Gryzor

In PG I have slower framerates too (0.4 ms more), maybe related to night-lightning improvement.

Me too. A10C II

Just to be honest, not quite good, they give me some general advices like put swapfile at 30GB (I have 60) even I reported this thread, it seems that don´t pay much attention. Fran Clavijo 11/08/2022 13:07:58 Quote Ok, but because the crash occours 30 minutes after start the plane, track doest reach that point (plane crash intro the ground, because track playing is bugged ... you know). Do you want the mission file? I find some other posts about A-10C II issues with the sames errors I have, please look the last post of this thread: https://forum.dcs.world/topic/311685-try-this-for-28-crashing/#comment-5085000 Thanks Mike 11/08/2022 15:01:49 Quote Hello, Please try to reduce the size of the Windows paging file to 30 GB. If the crash occurs again please send the latest dcs.log file and we will try to reproduce the crash on our test computer. Thanks. -- Best regards, Mike

I have the same logs and crashes with the A-10C II, but in other missions, in PG Map. I attach the latest one. I openned a ticket also. It seems to me that there is some 2.8 bug with the A-10C II. dcs.log-20221105-114401.zip dcs.log-20221106-013907.zip dcs.log-20221106-111012.zip

I´m having same logs in my four last crashes EDIT: @QuozL, did you have these crashes with the A-10C, like me?

I´m on VR, I have preload at 100K. Will try 150K thanks. PD. Do you tested with 2.8 version and not having any crashes?

Ok I create the ticket thanks Flappie. I attach all crashes related. dcs.log-20221030-163944.zip dcs.log-20221031-000847.zip dcs.log-20221105-030031.zip dcs.log-20221105-114401.zip

This mod is compatible with 2.8?

I have crashes in other missions (14), exact point, exact logs, @solid_84 look for my posts.

I have had another one, the same mission, the same location, the same sort of logs like before. @Chilling: I paid for the campaign just to pass every mission, please investigate or fix It, don´t mind if its ED, 2.8, A-10C II bug, or so... I wanna pass the campaign. I don´t have any issues with other campaigs. Thanks. dcs.log-20221105-030031.zip

I don´t know why I have to open a ticket, the problem is not my PC. I have another time the same error at the same exact point in the same mission (other missions plays perfect). Maybe its a A-10 module related, maybe the mission itself, maybe 2.8 version... i don´t know. I just want a fix because I pay for the campaign, not to be a betatester. Please @Ed fix it. Attached the new logs dcs.log-20221105-030031.zip

Exactly, some difference between to eyes is normal, but with these two shaders, rendering only occours in L eye. I prefer having smoke optimization switched on.

Hi Lefuneste, I noticed some glitches in FPS shaders about smoke bomb-cbu reduction, so I disabled from d3dx.ini: smoke is view in VR only in one eye. I copy them: ; track CBU OB ; GS shader of 1st serie, create smoke --> CAUSA DOBLE IMAGEN ;[ShaderOverrideCBU_GS1OB] ;hash=00000000e9c3df9f ;if $fixCraterBug > 1 && $BombSmoke > 100 ; handling = skip ;endif ;$BombSmoke = $BombSmoke + 1 ;CS of fitht group --> CAUSA DOBLE IMAGEN!!! ;[ShaderOverrideBomb_PS2OB] ;hash=00000000ec577c10 ;if $fixCraterBug > 1 && $BombSmoke > 100 ; handling = skip ;endif ;$BombSmoke = $BombSmoke + 1 In addition, I cleaned these effects, making only available for latest beta. With these lines I copy, I don´t have many issues, good balance between perfromance and quality, nor double rendering: ;------------------------------------------------------------------------ ; improve crater, gun and bomb smoke peformance by disabling effects ;------------------------------------------------------------------------ ; track CBU ; VS shader of 1st serie [ShaderOverrideCBU_VS1] hash=00000000564febe8 if $fixCraterBug >= 1 handling = skip endif ; track CBU OB ; GS shader of 1st serie, create smoke --> CAUSA DOBLE IMAGEN ;[ShaderOverrideCBU_GS1OB] ;hash=00000000e9c3df9f ;if $fixCraterBug > 1 && $BombSmoke > 100 ; handling = skip ;endif ;$BombSmoke = $BombSmoke + 1 ; CS shader of 1st serie [ShaderOverrideCBU_CS2OB] hash=00000000961bc6f5 if $fixCraterBug >= 1 handling = skip endif ; CS shader of 1st serie [ShaderOverrideCBU_CS3OB] hash=00000000ba2ef6b0 if $fixCraterBug >= 1 handling = skip endif ; CS shader lower fps after explosion [ShaderOverrideCBU_test5] hash=00000000e82a7e80 if $fixCraterBug >= 1 handling = skip endif ;------------------------ ;track bomb ;remove smoke but add fps ;DS of fitht group [ShaderOverrideBomb_DS1] hash=000000004b441fd9 if $fixCraterBug > 1 && $BombSmoke > 100 handling = skip endif $BombSmoke = $BombSmoke + 1 ;------------------------ ;track bombOB ;no visible impact ;CS of third group [ShaderOverrideBomb_CS1OB] hash=000000004a407f1d if $fixCraterBug >= 1 handling = skip endif ;CS of third group [ShaderOverrideBomb_CS2OB] hash=00000000897f524d if $fixCraterBug >= 1 handling = skip endif ;CS of third group [ShaderOverrideBomb_CS3OB] hash=00000000229e74e3 if $fixCraterBug >= 1 handling = skip endif ;CS of fitht group (after explosions) [ShaderOverrideBomb_CS5OB_F16_B49] hash=00000000675b556e if $fixCraterBug > 1 && $BombSmoke > 100 handling = skip endif $BombSmoke = $BombSmoke + 1 ;CS of fitht group (after explosions) [ShaderOverrideBomb_CS6OB] hash=00000000855b0e9d if $fixCraterBug >= 1 handling = skip endif ;remove smoke but add fps ;DS of fitht group [ShaderOverrideBomb_PS1OB] hash=000000006609d790 if $fixCraterBug > 1 && $BombSmoke > 100 handling = skip endif $BombSmoke = $BombSmoke + 1 ;CS of fitht group --> CAUSA DOBLE IMAGEN!!! ;[ShaderOverrideBomb_PS2OB] ;hash=00000000ec577c10 ;if $fixCraterBug > 1 && $BombSmoke > 100 ; handling = skip ;endif ;$BombSmoke = $BombSmoke + 1 ;CS of third group [ShaderOverrideBomb_CS4OB] hash=000000006a93daf7 if $fixCraterBug > 1 && $BombSmoke > 100 handling = skip endif $BombSmoke = $BombSmoke + 1

Skeletons on carrier!!

I report a crash that happens just after destroying the strela coming with other two bmps at the road. The same crash happened flying two times the mission, same logs, I attach. I believe its the mission bugged or some bug introduced in 2.8. Please review and fix it, the mission cannot be completed. Thanks. dcs.log-20221031-000847.zip dcs.log-20221030-163944.zip

After flying again the same mission, I have the same crash, at the exact time (just after destroying a strela SAM). The same exact log. So my conclussion, is not my config, I believe it is the mission or some bug introduced in 2.8 version. dcs.log-20221031-000847.zip

Thanks Flappie I´m sorry for the confussion. I repaired it following your advice, previous deleting Persian Gulf folder, I will test tonight the same mission. However, I´m quite opposite to updae W10 if it is not aboluteley mandatory, all my games & other program work without issues, so I don´t believe that W10 version is the cause. If some works, better not touch in!

Thanks BN. What W10 updates do you refer?

I find PS for flat shadows (all maps), also AH-64 rotor disable. If I can help... I copy for you: ;------------------------------------------------------------------------ ; Flat shadow skip OB ;------------------------------------------------------------------------ [ShaderOverrideBUILDINGS_PG_NEVADA_CAUCAUSUSOB] Hash=000000005abf504c handling=skip [ShaderOverrideBUILDINGS_CAUCAUSUS2OB] Hash=000000009883c095 handling=skip [ShaderOverrideFShadowTREES_PG_NEVADA_CAUCAUSUSOB] Hash=00000000b7325274 handling=skip [ShaderOverrideFShadowBUILDINGS_PGOOB] Hash=00000000a6e389cf handling=skip [ShaderOverrideFShadowBUILDINGS2_PGOOB] Hash=00000000f4404f1c handling=skip [ShaderOverrideFShadowTREES_SYRIA_NORMANDY_MARIANAS_CHANNELOB] Hash=00000000f1d3d17c handling=skip [ShaderOverrideFShadowBUILDINGS_SYRIA_MARIANAS_CHANNELOB] Hash=00000000eb6503ef handling=skip [ShaderOverrideFShadowTREES_NEVADAOB] Hash=00000000c9b4c413 handling=skip [ShaderOverrideFlagFShadowOBJ_AH641OB] Hash=0000000044ff43b0 handling=skip

Crash doing nothing. I attach log. dcs.log-20221030-163944.zip

I have had a similar freeze. Had to stop DCS. My logs ending is very similar to yours dcs.log.old.txt

Nearly one year has been passed since any news about multicore, vulkan or other updates... officially news. Come on ED... VR peformance is worse and worse after each patch iteration, making most modulues, specilly those recent ones, literally unusable in VR.

Thanks for your feedback. What I see is me flying relatively slow, and my enemy refuses to engage me. This is not correct, specially considering that he has the objective to intercept me. In addition, head to head shots must happen, and with modern fighters the AI never engage. With 2WW fighters, some times they shot on head to head, but not modern.

Hi NineLine, I attached 2 tracks in my first post. As you can see, every time the Mig-29 disengages everytime (I fly straight at mach 0.7 all the time). In one of them, Mig-29 have all fuel. Moreover, moder fighter never use guns in head to head BFM. Nevere. So its very easy to shoot down... The same situation happens with other fighters like SU-27

No. But looking at vrcompositor.txt (Steam VR log) everytime I get the stutter, I encounter these lines: Sun Aug 14 2022 15:32:19.139 - Error! EventWriteString Severe: [NvAPI] Invalid frameIndex: 39087 last=39087