Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: CP5670 on November 11, 2005, 11:38:25 pm
-
I have been getting a strange problem in FRED2 for the last few weeks that occurs in all builds since the 3.6.7 one as far as I can tell. Basically, the camera movement speed seems to be dependent on what's in the background. If there are lots of background graphics in view, it goes at a fairly normal speed, but if there are none visible, rotating and moving the camera goes about five times as fast as it should even though the speed settings are still the same.
Now I could be completely on the wrong track here, but I think it might have started happening at around the time that I updated my nvidia video card drivers. I went from XG 77.13 to the newer XG 81.85. Is anyone else getting these problems?
-
I'd guess that this is framerate dependent, since that's the only way I can see background images impacting the update of game state. Is this the case CP?
-
Are you using any time compression SEXPs? The camera is supposed to automatically scale so that it remains at a constant speed, even if you're screwing with the time.
It'll still speed up with just the in-game hotkeys though.
-
I'd guess that this is framerate dependent, since that's the only way I can see background images impacting the update of game state. Is this the case CP?
That probably has something to do with it, but I don't understand why it should cause this. I should mention that the retail FRED2 has no such problems, although that's probably because it uses a software renderer.
Are you using any time compression SEXPs? The camera is supposed to automatically scale so that it remains at a constant speed, even if you're screwing with the time.
It'll still speed up with just the in-game hotkeys though.
huh? This is in FRED2, not the game itself.
-
I'm guessing that FRED checks for input and updates on a per-frame basis, which would make it directly related. Retail FRED2 probably would have suffered a similar fate, but there's no way you'd ever load enough crap into the background to cause it with retail data and limits. On a related note, I've seen this too, on an ATI card, so it isn't just something unique to CP's PC.
-
Well...if you're somehow using the time-compression SEXPs to change the time compression in FRED, that could definitely be a problem. :p
Other than that, oops.
-
I didn't even know you could do that. What is it useful for, though?
-
You can't. That's why it'd be a problem.... :D
:nervous:
:sigh:
Nevermind.
-
Try the last mission of Trancend for an example of the SEXP in action in the game though :)
-
I mean, effecting time compression in FRED2 itself. Doesn't seem to be much point to that.
You can't. That's why it'd be a problem.... :D
:nervous:
:sigh:
Nevermind.
I looked over your posts again and still don't get the joke, if that's what it was... :p
Back to the topic, the thing is that I didn't have this problem until recently. Strat, did you always get this issue?
-
Yeah I've had it for ages, and it happens with both lots of Lightspeed nebulas and with really high-poly, texture-rich ships. It may not be the exact same thing, but I'd bet it's related.
-
I guess I'll just put this on mantis.