|
2006-06-27 17:10
|
White blinking 1.jpg (255,652 bytes) |
|
2006-06-27 17:10
|
White blinking 2.jpg (193,759 bytes) |
|
|
Sorry, I use all adv_effects but animated glowmaps and high quality SHOCKWAVES. I do use beams, HQ backgrounds and effects. edited on: 06-27-06 13:21 |
|
|
Why are you using -alpha_env but not -env? Does it make a difference if you don't use -spec? |
|
|
I'm not using -env because I forgot it. I disabled -env because of 961 (the performance drop) to see if I could get more fps (I did that before I realized RC2 ran smoother than RC3). I'm going to enable it and check if the blink stays. EDITED: Using -env is the same, sometimes a lot of ships blink in white. I have also disabled -mipmap (I don't know why it was selected ...) EDITED (and two): I've played just once without -spec and the white blinking hasn't shown up. I'm leaving now but I'll do more test without this flag. EDITED (and three): Well, I've played 4 times in a row WITH -spec and I haven't got the error. (I'm getting mad) ???? EDITED (and four): I've played another 3 times in a row WITH -spec and I'VE GOT the blinking in all of them. It seems it happens when there are a lot of light sources (but I'm just guessing). From now on I will test without -spec edited on: 06-29-06 13:46 |
|
|
Well a double post but there were too many edits. I've played that mission for about 3 million times and: + I think blinking tends to happen when there are a lot of light sources (beams, explosions, and so on) BUT I'm not sure. + Without spec you get a greyish effect rather than a white one. (I upload two more screenshots). + (Edited). I nearly forgot. I've noticed that somtimes there are extremely increased brights within the SD Nyar... (I upload another two files). These lights are caused by damage electric discharges in the rear Ganimede Ring. But the effect is too intense. (I don't know if it can have some kind of link with the main bug, if it is just another bug, or if it is done in that way by design). edited on: 06-30-06 14:27 |
|
2006-06-30 18:03
|
|
|
2006-06-30 18:03
|
Blink without spec 2.jpg (259,366 bytes) |
|
2006-06-30 18:27
|
|
|
2006-06-30 18:28
|
|
|
|
See how it is with this build (note: 3.6MB)... http://icculus.org/~taylor/fso/testing/light_test.rar |
|
|
Tomorrow I will try downloading from work. I hope icculus.org is not forbiden (Mantis or HLP are ...) |
|
|
Sorry, icculus.org is also filtered out in my job internet access. Please copy the exe inside somewhere http://fs2source.warpcore.org/exes/. This place still works from there. |
|
|
http://fs2source.warpcore.org/exes/light_test.rar |
|
|
No luck, the blinking is still there. OTOH, now I sometimes get the white texturing just over a few ships. (I think I never got that with previous versions). I attach two screenshots. |
|
2006-07-25 18:17
|
Partial Blink 1.jpg (87,076 bytes) |
|
2006-07-25 18:18
|
Partial Blink 2.jpg (76,887 bytes) |
|
|
As expected, RC7 does suffer this bug. (Just posting this to make me sure I remember the last RC I've actually tested with it. Don't worry too much about this bug, I haven't seen it in any other mission). |
|
|
No one else has reported similar issues, and I can neither replicate this or find any code bugs related to it. I'm starting to wonder if it's not system specific. If there is a video driver upgrade available then try that and see if it makes a difference. If that doesn't help any then we just have to close this since I doubt we are going to be able to do anything about this unless someone else can reproduce it. |
|
|
OpenGL lighting problems are known for NVIDIA old or PCI card drivers |
|
|
He's using a very new card though (7800GS). There have been numerous strange driver issues with the 7800 series though, so I'm hoping this is just one of those. |
|
|
I haven't tested that mission for a time, but close the bug if you prefer as it isn't serious at all. While testing it I've used several versions of forceware so I think it's something within the game. Nevertheless, even if closed, I will continue updating the bug info if I find more facts (or if I get it in another mission ...). But unless you get a clear hint of what's happening don't waste your time in it. |
|
|
I've played once with RC7.8: The bug is present. I've played four times with VidTest: The bug hasn't appeared. Secondary issues about VidTest that I suppose you know/expect: + FPS are really low. + As it is a debug build it shows "Warning: Couldn't fix up turret indices in spline path" in Capital02.pof (The Lucy), Cruiser01x (A Levy), Science01 (A GTSC Faustus) and Corvette2s-01 (A SCv Moloch) |
|
|
I'm sad to say RC7.9u suffers the bug. And this build seems to be about 5 FPS slower than RC7.8 when I'm facing all the action arround the Lucifer SD (from 45-50 to 40-45) (I didn't see the white brights with your vidtest build so I just can think about three options: + It was just luck. + If vidtest has some more changes than RC7.9u, they could fix it. + Release optimizations cause the bug. I'm going to test with debug RC7.9u. EDITED: Discard the last one I've seen it with the debug RC7.9u) |
|
|
Strange. The vidtest build had some extra features, but only one bug fix that isn't in 7dot9u, and that had nothing to do with textures or graphics stuff. The extra features were some minor 3D sound code work (not going into 3.6.9), better particle handling (for 3.7), and the Theora movie player. The vidtest and 7dot9u-debug builds did have slightly different optimization settings though. The vidtest build was set for Pentium/blend optimization, the 7dot9u builds (both release and debug) were set for only Pentium Pro optimization. I find it strange that it could have caused a problem though. I'll PM you later today with a rebuild of 7dot9u with the exact optimizations as the vidtest build, just in case. If it works fine then we'll know for sure that it's the optimizations causing this particular problem. |
|
|
Taylor, I haven't recieved anything. Feel free to PM/email/add to icculus/or whatever when you get it. |
|
|
Haha, I totally forgot! ;) I'm working on several things at the moment (mainly for finally testing the new FS2NetD code) so I'll have builds going all night. I'll add your build to the queue and PM you that when it's available at some point late tonight. |
|
|
Try: http://icculus.org/~taylor/fso/testing/rc7dot9x.rar |
|
|
I've got problems... RC7.9x release doesn't work. When you start the mission you go to Pause and you cannot leave it (Tolwyn has the same problem in 0001151). Debug builds are pretty unstable because of ingame "Warning: Couldn't fix up turret indices in spline path". When the Moloch arrives, (its pof has one of these warnings), you get the warning while switching to Windows desktop. Then, most of the times, the game crashes with the typical "The program has performed an illegal action and will be closed" Windows error. I suffered it with the VidTest build (I don't know how I was able to run the mission four times in a row). I've been able to fully run the debug build only once and the issue hasn't appeared. (But it isn't enough testing). @Offtopic: One suggestion about the turret warning. Would it be possible to show it at mission loading for ALL the ships despite if they are present or not at mission begining? |
|
|
I can't replicate the Pause problem, works fine for me, both debug and release builds. The only thing that I can think of is that a window is popping up (either a warning or something), the game goes into pause mode (it's suppose to), but you can't switch out of the game since it lost focus and has trouble getting it back. That's just a wild theory though, and something that you should be able to figure out relatively easily, if a warning popup is on the screen when you switch back to Windows to kill the process. As far as the warnings go, there should be a fixed model pack which fixes most of the problem models. I use it (as part of my own VP set) and haven't had those warnings since. But, if that doesn't help you any then you should just be able to use the -no_warn cmdline option. Technically it's "For FRED", but it works just the same whether you are using FRED or the normal game. It should prevent both warnings and Assert()'s, but it will still hit on otherwise fatal errors. The crash when it switches to Windows and then back, is largely a driver bug, and there is already a Mantus bug (closed as "not fixable") about that. The only real choice is to be sure and not get those warnings (ie, with -no_warn) or to always run debug builds in a window (the preferred "fix"). |
|
|
I will test with -no_warn ASAP, (very handy flag against this known pof issue). OTOH I have never tested in window mode (neither release nor debug). I suppose the issue also happens but I will also test it, just in case. About the pause issue: I will test with other missions/MODs, but it really seems other new bug (although I don't know why you cannot replicate it). |
|
|
it does not matter what kind of build you are using. It does not matter whenever you start the game in window or full screen mode. And no warnings pop up (I tested the game with 3.6.9 RCdot9debug). Then again, the new EXE works fine on a Geforce 6800. So it might be as difficult to reproduce as bug 1115 |
|
|
I have opened a new bug report (0001159) for the Pause issue. |
|
|
RC7.9u release build suffers the bug. I have also tested Windowed/Full Screen and it doesn't matter. The bug appears in both. Now I'm going to do more tests with Debug builds using -no_warn flag. EDITED: -no_warn flag isn't usefull because even with it the game swaps to desktop when the Moloch arrives (althogh I suppose no message window is displayed). As the bug also happens in Windowed mode, now I'm going to test it with -no_warn and windowed. REEDITED: Forget about VidTest not suffering the bug. It does suffer it so my previous tests were just luck. Sorry. |
|
|
As posted in the other bug... Give http://icculus.org/~taylor/fso/willrobinson/hoopla.rar a try. I found and fixed a couple of OpenGL texture/lighting bugs. |
|
|
I'll try to test it ASAP. But I'm going on travel outside town, so maybe it won't be possible till next week. EDITED. No fix. The second time I played the mission the bug appeared. |
|
|
Try with http://icculus.org/~taylor/fso/willrobinson/cousinarnold.rar |
|
|
I've played the mission 4 times and it hasn't appeared ... EDITED I've played another 3 more times and it still hasn't shown up. I don't know what you have tweaked from hoppla, but it REALLY seems fixed. |
|
|
I've played the mission 3 times with official 3.6.9. and the bug hasn't appeared. It seems really fixed now. |
|
|
Ok, I'll mark it as fixed then. It must have been that freaky secondary color stuff that I removed. That had been causing problems since it was originally added anyway, so not loss there. :) |
|
|
Fixered. |
- Anonymous
