Alpha blend smoke over alpha test has sorting issues - Call of Duty 2 about dxvk-remix HOT 13 CLOSED

Thanks for filing the issue. To get the cutouts enable Opacity Micromaps and disable Dev Settings \ Developer Options \ Enable and make sure to remove all but the necessary overrides from your rtx.conf. You have a lot of overrides in there set some of which cause unwanted behavior and serve no purpose for your use case (i.e. rtx.enableDeveloperOptions = True or rtx.opacityMicromap.enableResetEveryFrame = True, and others). Never set any advanced rtx conf overrides that you don't know what they do and don't need to make progress.

Note, Opacity Micromaps are a performance optimization feature and shouldn't be required to get the cutouts, but in your case there's an issue with how the foliage is resolved without them. For now, force enable Opacity Micromaps. Note, Opacity Micromaps need some time (generally a few seconds) to get generated.

from dxvk-remix.

oh thank you kristof that's sorted it, looks loads better. I've reset everything and added back my lights and texture settings.

unfortunately a crash will happen within about 2 minutes with "Opacity Micromaps" on but I understand its a work around. thank you again. Would you like me to mark this as closed?

from dxvk-remix.

No, let's keep the ticket open until the foliage cutouts are properly resolved without Opacity Micromaps being enabled.

Please provide repro steps + rtx.conf for when you see a crash due to Opacity Micromaps being enabled in the game.

from dxvk-remix.

Yea ok good idea. I've recorded a video until the crash.

https://www.youtube.com/watch?v=KPA7fAUKyaM

looked pretty cool until the crash then, you can see the trees look loads better, particles still have the clipping effect during the explosion sequence. This is my updated to default rtx.cfg
CODIssues_01.zip
I've included the config files again and changed the autoconfig file to have fog. to "r_fog 1".

to get to this level open single player, on the main menu type "spdevmap duhoc_assault"

from dxvk-remix.

I have been unable to reproduce the crash on 536.23 driver. What GPU are you using? Does it repro on the latest public driver (536.23+) for you?

Opacity Micromaps may introduce incorrect cutouts due to unstable hashes. I see you have stabilized the hashes for grass and tree foliage in this game, which is a great find, but hashes for other objects (i.e. windows) where the Opacity Micromaps are applied will need to be stabilized as well. If that's not possible, you could specify such textures to be ignored in rtx.opacityMicromapIgnoreTextures list, though that's a less preferred approach since it requires manual tagging. It's better to fix the hash instability issue on the game side.

from dxvk-remix.

I'm using a 4070 with driver 531.79. since updating to this build I'm not been able to make it crash either. however switching back to this build and holding the camera looking at trees through smoke causes a crash. takes around 10 minutes maximum (maybe move the camera a little bit). to get here open multiplayer, open console, type in "devmap mp_carentan" enter spectate mode and zoom around, its the burning house right in front of you as you enter the level

As a side note to completely stabilize all mesh hashes (in current view) enter /r_lockpvs 1 into console command, it stops the culling which is why everything keeps updating. the game is using a portal based PVS system explained here https://www.youtube.com/watch?v=IfCRHSIg6zo
you can see in the usd captures every object with a material gets bundled together into a group and as the camera moves models cull and this updates model hash...super frustrating. any help here would be appreciated but I understand is unique to COD2 and quake engine.

pro tip spawn as a solider, enter "noclip" into the command, fly up VERY high outside the sky box and look down so you can see the whole map

then enter /r_lockpvs 1 to lock everything in the scene, just press escape and change team to the other team to run aroound as a solider and have stable hashes for the whole level. I've attached lights and models to meshes in create with this process, it's reproducible meaning you can close the game, go through this process again and my rtx changes remain which is exciting for future remix work.

from dxvk-remix.

Thanks for checking. Are there any special steps that need to be done for multiplayer to work/launch properly?

from dxvk-remix.

oh yea that old chestnut. you need to copy your steam.dll found here D:\SteamLibrary to the main folder for cod 2 like this

next plug something into your microphone input on your pc (I know, i just use a pair of headphones :P) and lastly when you launch the screen will be black for about 30 seconds but it will eventually load. you can see the black screen issue here.
https://www.youtube.com/watch?v=hEIvaWR2oMQ

from dxvk-remix.

Even with the workaround the multiplayer doesn't launch. Can you confirm if you are still seeing crashes after enabling Opacity Micromaps in multiplayer with the build or newer? You said you could hit it with a build that's older than that.

from dxvk-remix.

If you still hit a crash, please attach the logs (i.e. CoD2MP_s_d3d9.log) and any dumps from that run (i.e. .nv-gpudmp for a GPU side crash and/or .dmp for a CPU side crash) . To get a gpu dump on a GPU crash, make sure your dxvk.conf sets following: dxvk.enableAftermath = True

If you are getting a .dmp on the crash it'll have to be from a build I linked above or newer.

from dxvk-remix.

Oh no that's no good. try following the instructions in this one.
https://steamcommunity.com/sharedfiles/filedetails/?id=492109413
For me it's the steam.dll in my root call of duty folder then I plugged in a pair of headphones in the recording slot and turned them on with sound --> Recording Devices. Just make sure it's enabled. Should be all set 🙂

from dxvk-remix.

I appreciate you providing the workarounds, but It ran once and never since, it's just not an actionable repro and way too time consuming for us to investigate. If you run into issue with Opacity Micromap in another more easily reproducible scenario, please file another issue.

from dxvk-remix.

Ok thank you for looking into this , I'll close the bug

from dxvk-remix.