fab.13

Salut Tigrou, You should post your 'VR Recovery' in the Bug/Peformance thread Moi aussi je vois du mieux dans cette OB ( à force... ) Au plaisir.

:thumbup: +1

+1 Look at total memory usage in task manager...

I made other tests. I can see a memory leak or bad memory managment with task manager. Selecting role many time in MP cause memory usage to increase, until crash when limit is reached... Using a greater SwapFile ( Virtual Memory ) make the problem to appear later. Here is a print screen of total memory usage ( physical + virtual ) near my 28GB limit (16GB physical + 12GB virtual )

Anyway, the "how to report a bug" thread in this forum says : "one thread per suspected bug". This is a rule. Now that "shadows performance" problem is existing and isolated in this OpenBeta. We should have to provide a good method to show this performance problem ( FPS counter, track, ...) And we'll see the status that ED will put on in. Let's be constructive...

I was thinking about getting the "REPORTED" status of such a thread...

Hello, We should create a separate thread about shadows Imacken has a powerful machine , but shadows performance problem ever exist on his machine

Another thread give numbers about the fps improvment ( f16 mission )

Hello AAlex, 0x00000000 seems a null pointer exception ( memory allocation failure and so on.. ) Did you have you monitored the memory usages of your machine while playing ( Task Manager ) ?

Hello, I encounter some crash with OpenBeta in MP ( last update ) Windows is stuck too after crash So I suspect that memory need has increased with OB, Or some memory leaks as we can see in Patch Notes. Example of memory leaks : - connect to a server - select a F14 Role and get into cockpit - see memory need in task manager - reselect a F14 role and get into cockpit - see memory need in task manager : it has increase a lot for dcs.exe ( 400 mo ) - and so reselect many times... until crash : system memory is full. WorkAround : disconnect from server if your system is near memory limit ( Physical Limit ) Other WorkAround : don't die ;-) I have not yet tested with other modules, i'll do it. My memory is 16GB, i'm going to add 16GB more in few days

+1 2.5.6 provided on March 20 feel in progress in VR mode We encourage ED to continue this work on Open Beta. I think we shoud have to redo performance tests we made, and give them again to ED team if tests results are not good enough.

@Mastiff : 2.5.6 have a significant impact in VR Performances, but your powerful machine allow you to keep 45 fps target for CV1 This not the case for lower machine. If you could do the test, you can mesure this impact. RTX seem to be better than any GTX, even a powerful GTX 1080ti...

Occulus is not fps limited in some case : see first post and the first answer The test procedure is in first post too

Hello CaptYosi Thank you for sharing New light system is very beautiful yes We are now interested about how it cost Beauty is not free ;-) Low power machine are very much impacted for now PS: Stutters are out of the scope, it is not the same problem Power can do nothing about stutters i think

Hello Terry, Open beta and stable version cannot share files But download is accelerated by coping from your drive In order to test the main menu, you do not need all modules and all terrains you own

Hello eaglecash867, Please could you do the VR main menu test with your CV1 as described at the beginning of the post ? I suspect current 2.5.6 need much more GPU power in VR than 2.5.5 It's as simple as that. And the main menu can show that. You need 2.5.6 and 2.5.5 and same graphics settings. Thanks

Hello, We should have to rebuild all VR settings starting from minimum ( nvidia control panel included ), did you take time to rebuild them ? After an acceptable balance settings choosen in 2.5.6 ( not as good as in 2.5.5 as we know ) , i tried a flight at night, the new light system is amazing !! and very much smoother than in day light...

Hello For now i reduced VR graphic settings drastically in OB 2.5.6 compared to Stable 2.5.5, so the experience is no longer as good as in 2.5.5 Did you take time to rebuild all graphics your VR settings starting from minimum ( nvidia control panel too... ), perhaps you could find a good balance ?

About the main menu, reducing the PD from 1.2 to 1.0 is the only way to get same fps between 2.5.6 and 2.5.5 on my machine I have now to test that in cockpit Perhaps the new ligth system allow us to reduce PD ?

True ! Main menu looks very nice now indeed. New light system is nice in VR But it seems to need much more GPU calculation at this time in 2.5.6 So i decided to redo DCS graphics settings from scratch and all well known combination with nvidia control panel In order to retrieve a good VR experience in 2.5.6, I lowered 'quality filter textures' in nvidia control panel to 'High Performances' So It is not as good as in Stable 2.5.5 about textures, but it is playable. Wait and see about ED team about tuning, i thrust them. If 2.5.6 goes to stable in this way, i should have to buy a more powerful graphic card ( planned for me in anyway ) PS: I found a fps killer : Terrain Shadow ( Flat ) If you look at shadow itself when on ground : fps are divided by 2 That's a proof that light has been rebuild ;-)

Same difference between stable 2.5.5 and the 2.5.6 released today. What could make the main menu downgrade about VR performances ? The current 2.5.6 rendering has performances downgrade for some VR people. Even in the main menu itself on my machine And it is a very simple gauge, no need to fly. And we can feel this differences when flying too. Please Occulus CV1 owners coud do the test ? Thanks

Hello, Here is the way i have been using to tune my VR Settings since 2 years : - Start Windows - Start Oculus Home - Plug Occulus Headset only ( hand controlers not needed ) - BUT don't put it on your head, leave it on your desk ... - Check Oculus Home detect your headset - Start DCS World in VR Mode - Stay on Main Menu, don't play ;-) - Display FPS counter ( CTRL + ALT + Pause ) Results : - Open Beta 2.5.6 : 127 fps - Stable 2.5.5 : 175 fps Graphics settings are the same Every well known tips have been done as usual ( "saved folder" deleted and graphics settings redone ) We shouldn't care about fps and so on We need smooth, playable, and nice VR experience. Stable 2.5.5 is very good in VR now in my point of view. Open Beta 2.5.6 is not so good for now, but everybody is working hard to get it better ;-) What are your results ? Thanks.

Hello, Here is the way i have been using to tune my VR Settings since 2 years : - Start Windows - Start Oculus Home - Plug Occulus Headset only ( hand controlers not needed ) - BUT don't put it on your head, leave it on your desk ... - Check Oculus Home detect your headset - Start DCS World in VR Mode - Stay on Main Menu, don't play ;-) - Display FPS counter ( CTRL + ALT + Pause ) Results : - Open Beta 2.5.6 : 127 fps - Stable 2.5.5 : 175 fps Graphics settings are the same Every well known tips have been done as usual ( "saved folder" deleted and graphics settings redone ) We shouldn't care about fps and so on We need smooth, playable, and nice VR experience. Stable 2.5.5 is very good in VR now in my point of view. Open Beta 2.5.6 is not so good for now, but everybody is working hard to get it better ;-) What are your results ? Thanks.

Hello, We meet a nearly problem with Open Beta 2.5 During our second multicrew flight on same server, auto-hover was not able to engage ( required parameters about speed and vario was ok as usual ). There was no problem in the first coop flight where role were inverted We'll try to reproduce on next time and provide 'step to reproduce'...

Hello, During our second multicrew flight, the commander was not able to see the Wite Rectangle in right corner of camera, whereas the pilot was able to see it. So the pilot should have to inform the commander for firing the HOT missile wich was lauched as usal. There was no problem in the first coop flight where role were inverted. We'll try to reproduce in next time...