| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004986 | The Dark Mod | GUI | public | 05.02.2019 10:29 | 03.01.2024 15:27 |
| Reporter | wesp5 | Assigned To | stgatilov | ||
| Priority | normal | Severity | normal | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Platform | PC | OS | Windows | OS Version | 7 |
| Product Version | TDM 2.06 | ||||
| Fixed in Version | TDM 2.07 | ||||
| Summary | 0004986: Compass turns white when using stencil shadows | ||||
| Description | The summary says it all. Activating stencil shadows turns the compass white or whitish, depending on the brightness settings. Using shadow maps turns it back to normal. Newer report: http://forums.thedarkmod.com/topic/19973-compass-model-all-whiteuntextured/#entry437234 | ||||
| Tags | No tags attached. | ||||
 |
On a faster PC the compass stayed white unless Soft Shadows were disabled completely, but after enabling them it continued to look normal! |
 |
This looks like a driver bug. Are you able to replicate on other graphics hardware? |
 |
Can you still reproduce this or was it a one time thing, maybe cured by a config reset? |
|
|
This happened to me on two different PCs both with two different NVIDIA GPUs (Geforce 1050 and Geforce 7600). It's reproduceable too, like when I start TDM and load a mission with soft shadows on, it will always be white. After I turn it off, it will become normal and stay even if I turn soft shadows on again afterwards. |
 |
Can't repeat on AMD - screenshot attached A quicksave/viewpos and a .cfg would be great |
|
|
I uploaded a save and my cfg file. |
|
|
Where do I download that map from? |
|
|
Sound Alert Map: http://www.thedarkmod.com/missiondetails/?id=19 |
|
|
What was this save version? I can't seem to load it with neither 2.07 nor trunk Was it 2.06? Does this still happen in 2.07? |
|
|
It was 2.07... |
|
|
Can anyone else load the save game attached here? Or reproduce the problem elsehow? |
|
|
I have some more issues that might be connected. In Lords and Legacy some other inventory items turned completely white, including the backdrop. Again just disabling soft shadows and then enabling it again got rid of all these problems! |
|
|
And another one: In Fiasco at Fauchard Street the map icon was translucent and didn't show the map. This was not corrected by turning soft shadows off and on so it might be something different, maybe Melan just forgot to add a icon version? |
 |
@wesp5 the bug report says it's for version 2.06 TDM. We've had no issues with these maps, I played Fiasco a few weeks ago and it worked fine, Nvidia 980ti latest driver. |
|
|
The bug report had only the option 2.06 when I reported this as it hadn't been updated to 2.07! I never had any of these issues in 2.06, only in 2.07... |
 |
Desktop Nvidia GTX 1060, laptop with integrated Intel Card, both 2.07 no hotfix - cannot reproduce the issue. |
 |
Cannot reproduce it on my GeForce. Next time when someone has this problem, please record everything you can: 1) darkmod.cfg at some moment 2) condump at the moment when you see white compass 3) record all actions you did since TDM start to most precision: did you start new mission of loaded save? what settings did you change and how they relate to saved config file? Attach everything (add prefix to filenames) here and mention which files you have attached. UPDATE: Ok, I managed to reproduce it from the save in .rar. I'll post more info later. |
|
|
I have reuploaded the savegames.rar as savegames.zip, with condump included. The core reason for the problem is, most likely, "r_useFBO 0". I think we dropped support for it in TDM 2.07 =) Everyone who have had the "white compass problem" at least once, please set "r_useFBO 1" immediately and forever =) This cause also explains why compass does not return back to white if you toggle soft shadows or related stuff on and off: you can get into non-FBO mode only if you start TDM afresh with "r_useFBO 0" set in config file. Unless someone has the white compass issue with "r_useFBO 1", I think we can close this issue. P.S. wesp5, your controls scheme is crazy =) |
|
|
Could anyone confirm that r_useFBO 1 fixed it for them? One other thing might be image_preload 1. |
|
|
One player confirmed it: http://forums.thedarkmod.com/topic/19973-compass-model-all-whiteuntextured/#entry437395 |
|
|
This bug can be fixed by setting r_useFBO 1 which should be default in future TDM versions! |
|
|
I resolve it as "won't fix" because it happens on non-default non-FBO mode, which we don't support starting from 2.07. |
|
|
Delete the r_useFBO CVAR_ARCHIVE flag? It's possible for this cvar to auto-switch to 0 if an FBO has failed to initialize. |
|
|
The suggestion about removing "archive" flag is a genius idea! As far as I see, if we remove it, then: 1) r_useFBO will silently revert to default for everyone, starting from the second TDM launch. 2) If someone really wants to use non-FBO mode, he can do it a) for single launch in order to test, and b) permanently via autoexec.cfg hack. We can do it, in case there is still some player with r_useFBO 0 by 2.08 =) |
