fragglescript cameras

[Neo]

is there any way to make FS camera unaffected by gravity? every time I spawn one it falls to the ground

[Rellik_jmd]

Not as far as I know. You have to make it using a hanging object.

------------------
DOOM Legacy Website Guy (http://legacy.newdoom.com/)
Webmaster The Legacy Editing Resource (http://legacy.newdoom.com/der/).
Webmaster Discharge! DeathMatch Level Reviews (http://www.telusplanet.net/public/daewoo/server/).

[Neo]

thanks..

and thanks for the awesome legacy editing site. it was extremely helpful http://forums.newdoom.com/UBB/biggrin.gif

[Agent Spork]

I don't know why you should even have to have a camera come from a thing... It would be alot better (in my opinion at least) if you could supply an X/Y/Z co-ordinate that you want the camera to be spawned from.

[Neo]

yeah, I agree..I don't see the point in relating it to a thing

[Exl]

You can use the objflag function to set options on a thing. Just spawn a camera object (const CAMERA = 144;) and immediately after that use objflag(cameraobj, MF_NOGRAVITY, 1

The MF* flags are in things.h, and the numeral '1' can be replaced by 0 to remove that flag instead of set it.

------------------
WhackEd, the only Windows DehackEd clone!

WhackEd 1.23.199 (http://home.wanadoo.nl/dennis.meuwissen/whacked)

[Ebola]

Sorry to bump a thread. but I've always used the camera thing supplied by SoM (I think or I just added an invalid thing, whatever it was so long ago I don't remember.) wich is thing number 5004

I'm fiddling some with old FS and it's alot to regain. I mean I've forgotten alot of it.

[Planky]

Thats odd, I don't remember editting exl's post...

Ebola, is it any different from thing 146? thats the one I've always used...

[Hurdler]

Planky: maybe it's related to the forum hacking (wasn't it around that date?)

[PumpkinSmasher]

no it say said was edited in february, the hacking was in january. and anyway, all threads from the hacking were deleted.

[Planky]

Planky: maybe it's related to the forum hacking (wasn't it around that date?)

I wasn't a mod then anyway.

[iori]

I've always inputted 5004 as well, never had any problems.

[Exl]

Just the CAMERA map object when spawning. Works fine.

[ToXiCFLUFF]

5004 and 5003 (MT_NODE and MT_CAMERA respectively) both have the correct gravity settings etc, for a camera, it's just that things.h was very inaccurate and so the CAMERA const had the wrong values.

The actual numbers should be:
const CAMERA = 146;
const NODE = 147;

[Exl]

We need a new updated things.h as well. TODO

[ToXiCFLUFF]

I've done a fully accurate one, but how can it be added to Legacy?

[Exl]

We might need to attract Hurlder's attention to see if they can be added to the CVS somehow.

[Hurdler]

I've already suggested that somone would centralize all the things you would like to see in a new things.h and then I can add it to the legacy.dat/wad for next release

[ToXiCFLUFF]

Ok, Hurdler. I'll send. PM me an email address to send it to (because IIRC the one listed gets full of spam).

[Hurdler]

yes, even more now. I delete every mail above 20ko because there is now nearly more virus on doomlegacy a newdoom.com than on legacy or hurdler a newoom.com (but less commercial spam though, interretings statistics you know).

can't you just put the file on a web server ?
Otherwise, just send it to doomlegacy a newdoom.com with a title like AAAAAAAAAA (I should recognize it ;))

[smite-meister]

Hurdler, when you get the updated THINGS.H, please import a copy of it to the doomlegacy_c++/resources/ directory as well...

[Hurdler]

ok. do not hesitate to ask me again if I forget ;)

[ToXiCFLUFF]

Exl and I have nearly finished updating the FS docs (Exl has made them much better, with a more intuitive listing method and proper CSS html stuff). Once he's done with the fsbasics.html, one of us will send them along with the accurate things.h.

[jnsg]

When/where will these updated docs be available to the public?

[jnsg]

5004 and 5003 (MT_NODE and MT_CAMERA respectively) both have the correct gravity settings etc, for a camera, it's just that things.h was very inaccurate and so the CAMERA const had the wrong values.

The actual numbers should be:
const CAMERA = 146;
const NODE = 147;
What are those things? I assume CAMERA is just a specialized thing for use with setcamera(), but what is NODE? And what are MT_NODE and MT_CAMERA?

[ToXiCFLUFF]

5004 and 5003 (MT_NODE and MT_CAMERA respectively) both have the correct gravity settings etc, for a camera, it's just that things.h was very inaccurate and so the CAMERA const had the wrong values.

The actual numbers should be:
const CAMERA = 146;
const NODE = 147;
What are those things? I assume CAMERA is just a specialized thing for use with setcamera(), but what is NODE? And what are MT_NODE and MT_CAMERA? Well, you can actually use any object as a camera (even an enemy) and MT_NODE and MT_CAMERA both have the same properties (except for radius, IIRC. I would imagine MT_NODE was implemented as a precursor to some kind of enemy path following system.

As an aside, if you set the shootable flag to an object and stick it where an enemy cannot reach it, enemies will still travel towards it. You can then do distance checks to determine whether to send them to the next point in the path. Useful for creating enemy patrols.