investigating unplayable in VR

[SgtButsy]

The dysync with this module is unplayable in VR.  It's not my rig, I fly the huey  just fine.  is there some expectation of fixing the terrible VR experience with this module?  If not, can I get a refund on this?  

[BIGNEWY]

17 hours ago, SgtButsy said:

The dysync with this module is unplayable in VR.  It's not my rig, I fly the huey  just fine.  is there some expectation of fixing the terrible VR experience with this module?  If not, can I get a refund on this?  

Please be more specific with the issue you are having. A track replay example would be a good idea. Let us know your rig setup also, dcs log would be helpful.

Please don't forget the CH-47F is in early access and active development. 

[fjacobsen]

The cockpit texture sizes are insane.

This has been reported in the Bug section of the CH-47F by many.

Some has reduced the texture sizes themselves, since regardless if this has been reported from the very first day of EA release, nothing has been done by the developers.

[LuseKofte]

2 hours ago, fjacobsen said:

The cockpit texture sizes are insane.

nothing has been done by the developers.

That last bit is bollox, or you have no idea What you Are talking about. You got to give more time before issuing a statement like that. They might very well have done nothing, or plenty. Thing is nobody outside knows

[BIGNEWY]

folks keep it sensible the op has said its unplayable for them, lets see the data first, there may well be a reason for it that we can help with. I do get lower frames in the CH-47F than other aircraft and we have reported to the team, but I am flying it without a problem. 

so please don't derail this thread with pointless squabbles. 

thanks

[MAXsenna]

That last bit is bollox, or you have no idea What you Are talking about. You got to give more time before issuing a statement like that. They might very well have done nothing, or plenty. Thing is nobody outside knows

In what way is it bollox? I have reduced the texture size with the script. It did reduce the VRAM demand, and got me som FPS in the formar patch. This changed with the latest patch where ED did some optimisations.

Sent from my SM-A536B using Tapatalk

[SgtButsy]

10 hours ago, BIGNEWY said:

Please be more specific with the issue you are having. A track replay example would be a good idea. Let us know your rig setup also, dcs log would be helpful.

Please don't forget the CH-47F is in early access and active development. 

i5 12600K Intel, 4080 Super Nvidia, 64 GB RAM, Quest 3.   If I look down the cockpit visuals are smooth, if I look out of the windows, it goes to ..., FPS down into the 40's, usually pretty locked at 60 in the F-18 and other modules.  It seems to been when the rotors are in sight, it becomes extremely choppy and not very playable.  LastMissionTrack.trk

[LuseKofte]

2 hours ago, MAXsenna said:

what way is it bollox?

It been out too short time to be evaluated and judged by what’s been done. 

[BIGNEWY]

1 hour ago, SgtButsy said:

i5 12600K Intel, 4080 Super Nvidia, 64 GB RAM, Quest 3.   If I look down the cockpit visuals are smooth, if I look out of the windows, it goes to... , FPS down into the 40's, usually pretty locked at 60 in the F-18 and other modules.  It seems to been when the rotors are in sight, it becomes extremely choppy and not very playable.  LastMissionTrack.trk

 

Hi, can you post your dcs log, it will give us some more clues. 

thanks

[BIGNEWY]

Using your track with my pimax crystal at 72hz frames were not to bad. 

Hopefully with your dcs log we can look at ways to tweak your setup to help with your frames. 

[SgtButsy]

16 hours ago, BIGNEWY said:

Using your track with my pimax crystal at 72hz frames were not to bad. 

Hopefully with your dcs log we can look at ways to tweak your setup to help with your frames. 

Sorry Newy, which one?    null

[BIGNEWY]

Hi, yes the top one, just named dcs 

If possible test again and send that file it will be from your latest session then.

thank you 

[SgtButsy]

dcs.logThanks Newy

[BIGNEWY]

Thank you for the log. 

It maybe worth removing all unofficial mods and sorting out the errors below, then running a slow repair.
Deleting metashader2 and fxo folders in saved games dcs so dcs can create new ones the next time it starts.

Ensure windows and all drivers are up to date also. 

Custom Mods
,ECHO19_FA18,CJS SuperBug AI Tanker,SAMSitesAssetPack,FA-18C,High Digit Sams,Hercules ver 6.8.2,FRENCHPACK 491 CORE,A-4E-C,Civil Aircraft Mod,MH-60R,HH-60_Seahawk,UH-60L,VNAO_T45,USN Ships,SSSMA,Tacview

The Integrity Check failed

Error
attempt to index global 'AGM_84D' (a nil value)
Line
244
Script
C:\Users\S\Saved Games\DCS.openbeta\CoreMods/aircraft/FA-18C/FA-18E_Attachments.lua

Error
malformed number near '0.2S'
Line
12
Script
/sounds/37/sdef/aircrafts/fa-18/distant_flyby_s.sdef
Error
attempt to index local 't' (a nil value)
Line
449
Script
./Scripts/Database/db_mods.lua

 

[SgtButsy]

I'll give it a go, thanks for the looking Newy

 

[YoYo]

27 minutes ago, SgtButsy said:

I'll give it a go, thanks for the looking Newy

 

No any issues for me, Chinook is FPS friendly for me. Maybe its a mod or part of the map when you are. Check on Nevada for example.

[Dangerzone]

8 hours ago, BIGNEWY said:

Deleting metashader2 and fxo folders in saved games dcs so dcs can create new ones the next time it starts.

Hey BN,

Just a quick one... is this still a thing? I heard chatter that this was no longer required as the update does this anyway - but I'm guessing since you're recommending the above, that this isn't true, and deleting FXO & Metashader2 is still required for optimum performance? 

(Just looking for definitive clarification one way or the other).

Cheers

DZ

[BIGNEWY]

7 hours ago, Dangerzone said:

Hey BN,

Just a quick one... is this still a thing? I heard chatter that this was no longer required as the update does this anyway - but I'm guessing since you're recommending the above, that this isn't true, and deleting FXO & Metashader2 is still required for optimum performance? 

(Just looking for definitive clarification one way or the other).

Cheers

DZ

Yes, deleting metashader2 and fxo folders is still a good thing to do if you are having issues. Allow DCS to generate new ones. 

 

[Raven (Elysian Angel)]

15 hours ago, YoYo said:

Check on Nevada for example

Funny that you mention Nevada. During the IA Chinook take-off NTTR mission I get 2 (two! - definitely not a typo) fps unless I reduce cockpit texture size to medium, and I have a pretty beefy PC.

 

9 hours ago, Dangerzone said:

is this still a thing?

It's good practice to prevent issues. Personally I clear both folders every time a DCS patch goes live, AND every time I update my graphics drivers. I also clear the DirectX shader folder in Windows itself.

[LuseKofte]

2 hours ago, Raven (Elysian Angel) said:

also clear the DirectX shader folder in Windows itself.

Is the folders name DiretX shader ? Or is it a folder inside DireX folder? 
Many thanks for information

[Raven (Elysian Angel)]

10 minutes ago, LuseKofte said:

Is the folders name DiretX shader ? Or is it a folder inside DireX folder? 
Many thanks for information

It shows up when using the Disk Cleanup utility built into Windows itself:

null

[YoYo]

6 hours ago, Raven (Elysian Angel) said:

Funny that you mention Nevada. During the IA Chinook take-off NTTR mission I get 2 (two! - definitely not a typo) fps unless I reduce cockpit texture size to medium, and I have a pretty beefy PC.

I still think it's not the module's fault, but some performance issues with the computer. Make a Track where you had those 2 FPS and I'll check that mission and will back with info. You can also show your graphics settings.

Edited October 23, 2024 by YoYo

[Raven (Elysian Angel)]

40 minutes ago, YoYo said:

I still think it's not the module's fault, but some performance issues with the computer. Make a Track where you had those 2 FPS and I'll check that mission and will back with info. You can also show your graphics settings.

 

It is most definitely the module’s fault, there’s absolutely no doubt.

The frame rate is that bad because the VRAM buffer of my card gets hilariously overloaded: it’s drinking from a fire hose. Why some people are still debating this, is beyond me…

[buceador]

32 minutes ago, Raven (Elysian Angel) said:

It is most definitely the module’s fault, there’s absolutely no doubt.

I posted something about this module a couple of weeks ago basically saying that I had included it as AI in a mission and as soon as it spawned the mission became a slide show, I replaced it with the original DCS Chinook and it ran perfectly...

[YoYo]

39 minutes ago, Raven (Elysian Angel) said:

It is most definitely the module’s fault, there’s absolutely no doubt.

The frame rate is that bad because the VRAM buffer of my card gets hilariously overloaded: it’s drinking from a fire hose. Why some people are still debating this, is beyond me…

How is that possible, since you have 16GB VRAM, my DCS doesn't take more than 8-12. So you still have some free space but ok, maybe it's an individual case, I won't confirm this without a track.

Edited October 23, 2024 by YoYo