Persian Gulf will not run in VR

[Irk26]

Hi, all. Really wasn't sure whether to post in PG or VR as the problem is specific to both, so I just flipped a coin.

 

I cannot get Persian Gulf to run in standalone VR. It will run okay in Desktop, but not in the SteamVR app. All other DLC modules and terrain work fine.

 

In VR, the loading screen appears (clouds on black background) and nothing further ever happens. It's basically hung at that screen. The progress indicator never moves, music keeps playing, the game appears to still be alive as I can do things like VR recenter (numpad 5) but I'm otherwise stuck on that screen. I have to kill the game from task manager.

 

Sometimes it will say "error initialization terrain" but not always. That seems random.

 

Under 2.5.2.(version previous to 19682) Stable, I tried:

-"Repair" which did not work.

-Then tried removing and reinstalling the terrain which also did not work.

-Then tried @uprade to Open Beta in case that was still required to run PG. Didn't work.

 

-Completely uninstalled DCS World and started from scratch by downloading and installing it again (Stable 2.5.2.19682 Update 7).

With no other DLC modules or terrain installed, downloaded PG again. Still doesn't work. Just hangs at the loading screen.

 

NVidia driver is current (updated from 398.11 to 398.36)

 

The Windows installation is a clean install from a couple weeks ago, patched to current. All drivers are current. BIOS is current.

 

 

I'm out of ideas.

Log attached...

 

 

Edit: From the log, I presume this is the problem: ERROR WorldPlugIns: Failed to read serial number for 'PERSIANGULF_terrain'

Seems to be that it can't read the serial number when running from the SteamVR app. No idea why or what to do about it though.

Edit2: Serial num is not the problem.

dcs.txt

Edited August 10, 2018 by Irk26
additional info

[Irk26]

Update 2.5.2.20143 fixed the problem somehow :)

[Chopper A-10]

Irk26,

 

I had the same issue . . the PG map missions ran in non-VR only.

 

Solved my issue today by deleting the Persian Gulf map, re-installing it, rebooting and everything worked in VR.

 

REPAIR and CLEAN did not fix what ever issues I had . . glad you got yours working again!!

[Irk26]

Yeah, I saw your post, Chopper. I debated whether to jump in there or not. Yours was very similar but not exactly the same. Glad you got yours working too!

Weird problem,man. Even reinstalling my DCS and PG didn't work.

I've had a ticket in with ED for a while so I don't know if they actually found and fixed something or it's just incidental that .20143 fixed the problem. I haven't heard anything back yet.

Anyway, at least we're both back in business :D

[Irk26]

Well, crap, DCS crashed tonight (first time it's ever done that) and now PG DOES NOT work again. And I wasn't even in PG when the crash happened. I was in NTTR with the Hornet. After a reboot, I looked through the crash logs and saw mention of PG -which I wasn't even using at the time- but it prompted me to check it. Sure enough, not working in VR again. *sigh*

[MadDog-IC]

Hi, all. Really wasn't sure whether to post in PG or VR as the problem is specific to both, so I just flipped a coin.

 

I cannot get Persian Gulf to run in standalone VR. It will run okay in Desktop, but not in the SteamVR app. All other DLC modules and terrain work fine.

 

Edit: From the log, I presume this is the problem: ERROR WorldPlugIns: Failed to read serial number for 'PERSIANGULF_terrain'

 

Seems to be that it can't read the serial number when running from the SteamVR app. No idea why or what to do about it though.

Edit2: Serial num is not the problem.

 

Problem is most likely:

 

1. In your "C:\Users\HomerSimpson\Saved Games\DCS" directory, try renaming the "MissionEditor" folder temporarily and let it recreate a new one to test with, run dcs again and save a new log file.
   
2. or
   
3. In your "C:\Users\HomerSimpson\Saved Games" directory, try renaming the whole "DCS" folder temporarily and let it recreate a new one to test with, run dcs again and save a new log file. (If it works, you will have to move directories back one at a time and retest to see what may have broken it.
   
4. The Persian Gulf Map module isn't passing authorization, it doesn't use the key system so ignore that error message, but is directly linked to your account, so there is still something amiss there also. May need to be deleted and reinstalled again.
   
5. The VR system may be causing some interference to the security system, I suspect this as I see a failure of the DCS WebGui because of "no webserver running" in the log files.
   
6. Other thing that causes a module security to fail is the presence of livery, cockpit and other mods in your E:\DCS World\ install directories and not the "C:\Users\HomerSimpson\Saved Games\DCS" directory structure, but as you done fresh install this is unlikely.
   
7. My own system is similar to yours I am guessing, I have win8.1 with 32gb of ram, and I have a module security failure with the AV-8 Harrier module, it is linked to my account fine, but it fails every time, early on dcs would lockup and not run at all until I disabled the module completely, now dcs runs fine with it enabled, but I can't fly it when I go into a mission designed for it, it just shows an AI flying it.
   
8. Disable any virus scanner as maybe interfering with software installs ???
   
9. Repost new dcs.log file of current effort running DCS.
   

 

 

2018-07-30 17:21:07.689 ERROR DCS: WEbGui init failed: no webserver running

 

 

 

2018-07-28 00:46:12.104 ERROR SECURITYCONTROL: failed to load mods/terrains/persiangulf/terrain.cfg.lua.dll.crypt

2018-07-28 00:46:12.104 ERROR SECURITYCONTROL: Failed to load mods/terrains/persiangulf/terrain.cfg.lua.dll

2018-07-28 00:46:12.104 ERROR DCS: Can't load terrain from ./Mods/terrains/PersianGulf\terrain.cfg.lua

2018-07-28 00:46:12.123 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_weather.lua"]:1192: attempt to index local 'SW_bound' (a nil value)

GUI debug.traceback: stack traceback:

[C]: ?

[string "./MissionEditor/modules/me_weather.lua"]:1192: in function 'generateWinds'

[string "./MissionEditor/modules/me_weather.lua"]:389: in function 'loadPreset'

[string "./MissionEditor/modules/me_weather.lua"]:1239: in function 'loadDefaultWeather'

[string "./MissionEditor/modules/me_mission.lua"]:2487: in function 'create_new_mission'

[string "./MissionEditor/modules/me_mission.lua"]:1435: in function 'load'

[string "./MissionEditor/modules/me_quickstart.lua"]:260: in function 'func'

[string "./Scripts/UI/ProgressBarDialog.lua"]:138: in function 'updater'

[string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>

 

 

Regards, Ian.

Edited August 14, 2018 by MadDog-IC
Clarified some procedures better

[Irk26]

Hey thanks for the reply, Ian.

For sure antivirus is not the issue because when I had the original problem, I had no anti-virus installed at all.

 

I don't know if it makes any difference to what you're suggesting but I haven't flown a single mission so far. I've just been flying in Instant Action or Training. If what you're suggesting to try is still relevant however, I need a little more detail:

-What folder specifically do I rename in DCS World\MissionEditor? There are multiple folders with multiple sub-levels below them and I don't see any one that refers to Persian Gulf in any way.

-Or same question for Saved Games. I don't see anything in the MissionEditor folder there that looks like it applies. All I have in there is a few files and one folder named Weather.

 

I've posted the current log but it looks pretty much identical to the one I posted at the top.

According to tech support the problem is this:

2018-07-28 00:46:12.104 ERROR SECURITYCONTROL: failed to load mods/terrains/persiangulf/terrain.cfg.lua.dll.crypt

2018-07-28 00:46:12.104 ERROR SECURITYCONTROL: Failed to load mods/terrains/persiangulf/terrain.cfg.lua.dll

2018-07-28 00:46:12.104 ERROR DCS: Can't load terrain from ./Mods/terrains/PersianGulf\terrain.cfg.lua

 

They say something is interfering with crypt but if the problem was on my side, I'd would expect other DLC to have similar issues. The fact that this is confined to PG only in VR makes me think the issue is with PG. Anyway, I think tech support has given up because they can't reproduce it and they say no other users have the problem. I let them know about the similar issue Chopper A-10 was having but I still haven't heard anything from them unfortunately.

dcs.log.txt

[MadDog-IC]

Hey thanks for the reply, Ian.

 

I don't know if it makes any difference to what you're suggesting but I haven't flown a single mission so far. I've just been flying in Instant Action or Training.

 

If what you're suggesting to try is still relevant however, I need a little more detail:

 

It is a hard one for sure, what I am saying is still relevant, I updated my previous post to be more clear and added the VR failure message to the spoiler, so please re-read.

 

You appear to have at least 3 separate issues:

 

1. VR interface in DCS failing to run.
   
2. MissionEditor .lua file corruptions.
   
3. Persian Golf Map security failure and map not loading.
   

Could be that VR interface failure is causing a snowball effect and creating the other two problems, this would be logical, as you say you can run the same senario with a montor instead of VR and it doesn't have these issues (A dcs.log of the same missions run on a monitor setup would be helpful to compare against the VR based one)

 

-Or same question for Saved Games. I don't see anything in the MissionEditor folder there that looks like it applies. All I have in there is a few files and one folder named Weather.

Don't focus on PG map so much and look for relevancy:

 

1. I don't have VR I don't know what is normal for the dcs.log to have in it when working correctly, but I do see a failure to init the DCS WebGui which I have never seen in anyone else's logs.
   
2. I am trying to fix the two other issues (MissionEditor .lua config file failure) and (PG Map security failure), by ruling them out of the equation, so by taking the complete DCS configuration directory back to default, that is one thing less I know isn't causing the issue and so on.
   

 

In your "C:\Users\HomerSimpson\Saved Games" directory, try renaming the whole "DCS" folder temporarily to "_DCS" and let it recreate a new one to test with, run dcs again and save a new log file. (If it works, you will have to move directories back one at a time and retest to see what may have broken it.

 

They say something is interfering with crypt but if the problem was on my side, I'd would expect other DLC to have similar issues.

Not necessarily.

 

The fact that this is confined to PG only in VR makes me think the issue is with PG.

May be so, but if PG runs fine when not running VR, then the issue must be something to do with the VR setup or files associated with it (Is there any software or firmware updates for your VR setup available at the support sight).

 

Anyway, I think tech support has given up because they can't reproduce it and they say no other users have the problem. I let them know about the similar issue Chopper A-10 was having but I still haven't heard anything from them unfortunately.

Very difficult to fix if no one can't reproduce, but as I said in other post I have a security issue with the Harrier module that has no reason for failing but does, I am running it in a test version of DCS that is pretty much no mods or anything fancy such as VR.

 

 

Regards, Ian.

Edited August 14, 2018 by MadDog-IC

[Irk26]

FOUND IT!

If the pixel density is about 1.7 or greater, PG will not run in VR.

1.6 or below, works fine. 1.7 or above, stops working.

And I get those exact "SecurityControl" lines in the log.

 

In brief, I just did what you said, Ian, and followed it fully through: Renamed the DCS folder. The newly created one worked. Started transferring stuff from the old to the new. Narrowed the problem down to Config\options.lua. Then diff'd the working and non-working options files, swapping one line in at a time from bad to good until it broke. That turned out to be the "pixel_density" line which was set to 1.8 in the old config. Then I just dropped the value one notch at a time until it started working again. That turned out to be 1.6

 

It's actually a little wonky in that those numbers are not hard and fast. 1.6 or under seems to work every time. 1.7, it'll work most of the time. 1.8, will pretty much never work... just once in a blue moon.

 

Anyway, however the numbers work, the problem does appear to be tied to pixel density.

Edited August 15, 2018 by Irk26

[Irk26]

More update: since .20601 the issue has crept into NTTR as well now. Anything over 1.7 is pretty much guaranteed not to work... at least for me...

Edited August 29, 2018 by Irk26
additional info

[Mesenzio]

I have the same issue with Persian Gulf. I tried to lower the PD to 1.3 but the results are the same. Maybe it takes a bit longer to crash (not much though), but it crashes nevertheless. No problem (aside from some occasional crash) with Caucasus. I did a fresh install and also deleted and reinstalled the PG map.

 

I run a Lenovo Explorer with an i7 3770, 16GB and GTX 1080 with the latest release version, lately the open beta has been even worse.

dcs.zip

[MadDog-IC]

I have the same issue with Persian Gulf.

 

I tried to lower the PD to 1.3 but the results are the same. Maybe it takes a bit longer to crash (not much though), but it crashes nevertheless.

 

No problem (aside from some occasional crash) with Caucasus.

 

I did a fresh install and also deleted and reinstalled the PG map.

 

I run a Lenovo Explorer with an i7 3770, 16GB and GTX 1080 with the latest release version, lately the open beta has been even worse.

 

This problem doesn't look related to previous users issue as your not getting the same errors in the log he had, but your error log shows a lot of out of memory issues.

 

I take it your not running the latest OB 2.5.3.21444 as it appears more unstable (I suspect it may have a memory leak, which might exasibate your issue by raising the required RAM faster and higher, thus exhausting all of your physical and virtual RAM). Compared to the OB 2.5.2 version you are running, still causes the issue, but just takes longer

 

I would suggest trying:

 

1. Check your "Windows swap file" settings, and have it set to system managed, if not already so, with 16gb of physical RAM, I would want it to be at least 16 to 32gb of virtual ram.
   
2. Unlikely to be a video card driver issue, but you never know.
   

Error Log Exert showing Directx errors:

2018-09-16 21:20:11.850 ERROR   DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY
2018-09-16 21:20:11.850 ERROR   DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG
2018-09-16 21:20:11.854 ERROR   DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY

Regards, Ian.

[Mesenzio]

Hi Ian, thank you so much! It was indeed the page file. I had already set it to maximum 16GB but it wasn't enough, with a minimum of 16 now the game is stable.