silverdevil

hello. are you trying a track that was created with the current revision of DCS? if you are trying a track from a previous revision, it is likely your issue. also if you want, post your DCS.LOG file for analysis.

well i learned something new today. i cannot even play the track unless i paid for the campaign. can you create a mission with the anomaly between the two waypoints with F-16? or coordinates?

i do not have that mission. but you can fly the mission to the point you start seeing the effect. quit the mission and save the track. then post it here. i can load it to see what i see.

if i am understanding, an hour long track has little chance of being free of "corruption". meaning the ending maybe does not happen the same as what really happened. the shorter they are, the more reliable. i have seen my own tracks do great all way to final for landing, and i crash into the trees. i am not sure how to fix. i personally think content creators film like a motion picture would do it. they would not do it in one take. they also have others in ac being sort of a chase plane somewhere on the map. but i do not do it myself. i could totally incorrect. before running DCS, unplug your controllers. run DCS. you start the track. being that you have no input devices, something will not "take control" of track. this is what i do anyway.

interesting. thanks for the update. what was the map in your earlier examples? i just thought of something. maybe do a short track of the anomaly and post it. i can try to see if i can see the effect.

i do not have many other ideas for you. how about a slow repair? turning off upscaling in DCS? maybe renaming CONFIG folder to CONFIG.bak as a test. when you rerun DCS the folder will be recreated. you can copy over the CONFIG.bak\INPUT folder to new CONFIG folder. where your controls are. unfortunately for testing sake, I do not have any of this banding.

i posted look into ReShade as a possible cause 3/22/2024. deleting contents of the shader folders is always a good tip.

oh lol sorry. i was looking at a log for someone else. if you have 128 then no need. i too have 128 but still have a 32 pagefile. can you share a log from when the mission gets stuck?

i helped on the post flappie linked but never got any feedback from the OP. see if anything there helps. essentially rename \Saved Games\DCS.openbeta\Scripts to \Saved Games\DCS.openbeta\Scripts.bak. retry dcs.

you have the latest version. so that is likely not the problem. i did notice that from your log, you have 32 GB RAM and a low pagefile. you should up your pagefile to 32 GB. https://www.thewindowsclub.com/increase-page-file-size-virtual-memory-windows

hello. it looks like you are using winwing exports 2024-03-24 16:09:53.188 INFO WWT (Main): Winwing export installed! 2024-03-24 16:09:53.192 INFO WWT (Main): Export start! these errors are last thing before your crash. post your EXPORT.lua OR try to rename your Saved Games\DCS and run DCS again. just as a test. if it works then there is likely an issue in those folders. you can then copy your CONFIG folder back over to the newly created Saved Games\DCS

i searched in google "dcs stripes banding on water"

@islapaisano i added TR and did not have any problems. went straight in with no delays.

glad to help. feel free to ask for help anytime.

hello and welcome to DCS. there have been other posts about this. your screenshots are worst i have seen. no fix that i could find. so looking at your settings compared to mine. try turning off SSLR. also turn off upscaling. FYI i do upscaling at the driver level outside DCS. and maybe disable reshade as a possible cause.

post your MIZ file as @Flappie asked. then we all can try it.

i was going to ask the same thing as a previous post i saw this was the corrective action. in all my years in IT (coming up to 35), i never heard this before. but not impossible i suppose. another reason to have a good UPS and not use a surge protector. UPS does a good job of conditioning power.

vielen Dank für deine Unterstützung!

log still does show a crash. there is lots of log stuff i have never seen. do you have any mods? you should remove them and run a repair. you may also want to check windows event logs for the BSOD message. you could have a hardware issue.

sorry. i do not have the huey. are you having these troubles in just the huey? any other aircraft having the issues?

hello. the key \ is for ground crew commo. those keys you mention and the HOTAS are in air commo. unless i am misunderstanding your question.

the log you provided does not show a crash though it does end abnormally. try to rename your DCS folder within Saved Games to .BAK. retry DCS and a new folder will be created. you will need to copy over your controls. look in \Saved Games\DCS\config\ it may be named openbeta and copy INPUT folder over into the new DCS\CONFIG folder. let us know.

i am not seeing a problem with your screenshots. from my perspective, the dark spots on the water are shadows. forgive me if i am missing something.

hello. please attach the latest ZIP and dcs.log for further analysis. they can be found in folder \Saved Games\DCS(.openbeta)\Logs