|
|
Screenshots would help |
|
2004-04-05 00:14
|
shrinkingbefore.jpg (14,997 bytes) |
|
2004-04-05 00:14
|
shrinkingafter.jpg (13,954 bytes) |
|
|
the after picture is as soon as i could press Print Screen when i saw it... is it almost immediately after the second picture that it starts shrinking normally... I don't know if this is in other builds, since Taylor's is the first to run on my system... |
|
|
Is this still an issue? |
|
|
I think so. It only happens with the player's warp effect - none of the other ships do it. Mebbe I could grab a digital video of it. |
|
|
If this is still an issue, is anybody working on it? |
|
|
It's still an issue. I'd like to see it fixed, but I don't know how to fix it. :( |
|
|
I've never been able to recreate this otherwise I'd have a go at fixing it. Only really tried under Linux but never noticed with my few tests under Win2k either. |
|
|
If I could take in-game footage at more than 5 FPS I'd post a video. It behaves normally except for a split-second when the hole skips from fully open to 2/3rds open. It's as if you "microsleep" for an instant. |
|
|
You can't do "dump_frames" in a debug build and get it? "dump_frames" is only capturing at 15 FPS but "dump_frames30" may get it if the other doesn't. Should be able to make an AVI out of the individual frames in VirtualDub after that. |
|
|
Wait... FS2 has a built-in capture-to-video function? Since when? This is very good news. :) Does it work in both debug and release? It should... assuming the framerate is good, this should greatly help with producing trailers and such. If it works, I'll grab a video when I get back to school. |
|
|
Yep, always been there, though I just recently filled in the OpenGL functions. Should have already worked in D3D but I never tested it there. On works in debug builds but that can be worked around so it can work in release builds too. For debug builds just bring up the debug console and type "dump_frames" (or "dump_frames30" for 30fps) and it will start recording (dumps frames in game directory with frm%.4 filenames). Do it again to stop recording. The 15fps version isn't very playable but it works. Typing "help" in the console will give the full list of commands or just search the code for those DCF() things to get the commands and options they provide. |
|
|
i can get an avi of it if it still exists... |
|
|
http://woodentoyandgift.com/files/rob/shrinking.rar captured at about 30fps, though there is a massive fps hit right when it shrinks... |
|
|
What cmdline options are you using Hippo? Have you tried Lightspeed's new warpmap (the EFF one with DDS frames)? I've got to wonder if this is somehow memory related. I couldn't make out the numbers but the memory count in the top left was moving pretty good when the problem happend. I'll play with this and try to recreate it on my end. |
|
|
that was with: -spec -glow -pcx32 -jpgtga -d3dmipmap -nomotiondebris -2d_poof -cell -d3d_no_vsync -dualscanlines -ship_choice_3d -targetinfo -orbradar -ballistic_gauge -snd_preload -dnoshowvid -env -decals -fps -window -stats -show_mem_usage -ALLSLEV -FOV 0.39 I can get a higher res of it if you'd like... And i haven't tried the new warps either... edited on: 03-13-05 15:57 |
|
|
Yeah, there is a lot of memory hungry stuff there. Last question before I go into all out bug-hunt mode, D3D or OpenGL? |
|
|
I first noticed it in D3D, thouch that was filmed in OGL, so it is both... |
|
|
See, I just have to recreate the problem and all is good. ;) WARPHOLE_GROW_TIME was changed from 1.5 to 3.5 back in 2002. This should have been evident since that change was made but it may not have been an issue until other warp changes were made in 2004. The problem stems from lifetime and radius. At 1.5 it quickly grows to it's full radius and stays there until the lifetime says to start shrinking. At 3.5 though is where the problem shows itself. It grows more slowly and stays fullsize a bit shorter ammount of time. This is where the lifetime comes into play since it needs to shrink at the proper speed but it's open too large at this point. There is a sudden drop in size to compensate. Setting WARPHOLE_GROW_TIME to 2.5 seems to be enough to fix this so that's what I'm going to do. I'm updating my just released build so please give it a try Hippo and let me know if this is enough. If not then I'll lower it down more and commit it to CVS. http://icculus.org/~taylor/fso/willrobinson/20050313-win32r.zip No idea why I never noticed this before. |
|
|
Bingo, looks fine... And somehow it's bumped my framerate as well :) BUT... There's something up with that build, since as i run it windowed, the FS mouse AND the windows mouse move, and whenever i clicked, the windows mouse always took precidence... But thats an entirely different bug alltogether... edited on: 03-13-05 21:41 |
|
|
Fixered. I noticed that mouse problem too. Going to have a look at it before the night is over. |
- Anonymous
