Hippo

+1 Bump. Please can this be looked into.

Many thanks for replying. "Flights shall be established at their assigned port holding pattern altitude 10 nm prior to entering the pattern." I had interpreted this to mean that all aircraft come into the hold at their assigned altitude from 10 miles away, so 2,000 ft for lowest level, and then circle and drop to enter the pattern at 800 ft. If I understand you correctly would the default situation is aircraft coming in from 10 miles behind the ship at 800 ft straight into the pattern, without going into the hold at all? i.e what actually happens 10 nm from the ship?

From the CV NATOPS: A ceiling of 3,000 feet and 5 miles visibility within the carrier control zone is required. This approach may be utilized when it can be anticipated that flights will not encounter instrument conditions at any time during the descent, break, and final approach. The jet and turboprop port holding pattern is a left-hand pattern tangent to the BRC or expected BRC with the ship in the 3-o’clock position and a maximum diameter of 5 nm. Flights shall be established at their assigned port holding pattern altitude 10 nm prior to entering the pattern. Minimum altitude assignment shall be 2,000 feet MSL. A minimum of 1,000 feet vertical separation between holding altitudes shall be maintained. What happens wrt holding if there's an overcast at (say) 3,500 ft over the ship? Does this mean with Case 1 that no aircraft can hold above this level? If there were many aircraft inbound wouldn't it simply not be possible to stack them all up with Case 1?

Thank you. 1.5.8 and 2.5.0 are working for me again.

I think you could be onto something. For a while (around the time I was updated to 1809) I've been unable to start older versions of DCS (including 1.5) https://forums.eagle.ru/showthread.php?t=230874 Then again, I would've expected more reports regarding this issue.

This would be a perfectly reasonable question, which would add to the discussion. Unlike your own post. Perhaps you should take your own advice. And chill.

Thanks. I had tried that (should've said). Also tried a repair. No joy. Are you running 2.5.0?

I'm afraid I find communications from ED sadly lacking at times. What you're saying, in effect, is: We are attempting improvements to VR, but at the moment we don't know if they will work. We don't want to give any specific details because if some items don't work, some people will be upset. Can you not see a bit of a contradiction in your own argument? People are understandably interested in details, why not just state: We are attempting A, B, C. Nothing is guaranteed. Thanks, good to know.

I keep 2.5.0.15365 on my hard disk, as it was the last version with forward rendering available. But now it crashes on startup. Was wondering if anyone who is still running this version is experiencing the same issue. Thanks for any replies. === Log opened UTC 2019-01-27 10:43:59 2019-01-27 10:43:59.279 INFO VFS: Using 'Saved Games': "D:\Users\<USER_NAME>\Saved Games" 2019-01-27 10:43:59.393 INFO DCS: DCS/2.5.0.15365 (x86_64; Windows NT 10.0.17763) 2019-01-27 10:43:59.393 INFO DCS: DCS revision: 135364 2019-01-27 10:43:59.393 INFO DCS: Renderer revision: 15903 2019-01-27 10:43:59.393 INFO DCS: Terrain revision: 16184 2019-01-27 10:43:59.393 INFO DCS: CPU cores: 6, threads: 12, System RAM: 16319 MB 2019-01-27 10:43:59.402 INFO EDCORE: (dDispatcher)enterToState_:0 2019-01-27 10:43:59.406 INFO Dispatcher: 2019/1/27 10:43 V1704040900 2019-01-27 10:43:59.427 INFO INPUT: Device [Keyboard] created deviceId = 1 2019-01-27 10:43:59.447 INFO INPUT: Device [X52 Professional H.O.T.A.S. {B2136E80-FE31-11e7-8005-444553540000}] created deviceId = 2 2019-01-27 10:43:59.448 INFO INPUT: Joystick created[X52 Professional H.O.T.A.S. {B2136E80-FE31-11e7-8005-444553540000}], ForceFeedBack: no 2019-01-27 10:43:59.462 INFO INPUT: Device [Mouse] created deviceId = 3 2019-01-27 10:43:59.548 INFO SOUND: loaded 1261 sdefs from "sounds\sdef" 2019-01-27 10:43:59.566 INFO SOUND: Using driver: xaudio29 2019-01-27 10:43:59.593 INFO SOUND: XAudio2: channel layout: FrontLeft FrontRight FrontCenter LowFrequency BackLeft BackRight SideLeft SideRight 2019-01-27 10:43:59.610 INFO SOUND: Found 5 available audio device(s): 2019-01-27 10:43:59.610 INFO SOUND: 0: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{4716516e-a960-4b4e-91f3-1678bd572f28}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "U3477 (NVIDIA High Definition Audio)" 2019-01-27 10:43:59.610 INFO SOUND: 1: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{f5ad6543-f48a-4f35-9b4c-a80599f48041}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Headset Earphone (Corsair Gaming H2100 Headset)" 2019-01-27 10:43:59.610 INFO SOUND: 2: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{42d6adb4-46ad-4da3-8417-423b0d89e8d4}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Headphones (Rift Audio)" 2019-01-27 10:43:59.610 INFO SOUND: 3: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{fae8e0d0-311e-43a2-a4b5-70caf657be69}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Digital Audio (S/PDIF) (High Definition Audio Device)" 2019-01-27 10:43:59.610 INFO SOUND: 4: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{14e8b4e4-33b9-4590-b72f-7f3d4ab2cd45}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Speakers (High Definition Audio Device)" 2019-01-27 10:43:59.611 INFO SOUND: Using SSE FTZ/DAZ mode. 2019-01-27 10:44:01.484 INFO NET: Login success. 2019-01-27 10:44:02.120 WARNING LOG: 1 duplicate message(s) skipped. 2019-01-27 10:44:02.120 INFO DCS: Successfully got authorization data. 2019-01-27 10:44:03.140 INFO SECURITYCONTROL: Loaded mods/tech/wwii units/dcs_module.dll 2019-01-27 10:44:04.264 INFO Scripting: OBSOLETE mount_vfs_sound_path() used in ./CoreMods/aircraft/AJS37/entry.lua 2019-01-27 10:44:06.953 INFO Scripting: PLUGINS START------------------------------------------------- 2019-01-27 10:44:06.953 INFO EDCORE: try to write dump information 2019-01-27 10:44:06.955 INFO EDCORE: # -------------- 20190127-104407 -------------- 2019-01-27 10:44:06.956 INFO EDCORE: C:\WINDOWS\SYSTEM32\ntdll.dll 2019-01-27 10:44:06.957 INFO EDCORE: # C0000005 ACCESS_VIOLATION at F4CA9A9D 00:00000000 2019-01-27 10:44:06.959 INFO EDCORE: 00000000 00000000 0000:00000000 2019-01-27 10:44:06.962 INFO EDCORE: F4CA9A9D 009EE450 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlEnterCriticalSection()+D 2019-01-27 10:44:06.964 INFO EDCORE: CFB44670 009EE480 0000:00000000 D:\DCS World\bin\physfs.dll PHYSFS_setWriteDir()+E0 2019-01-27 10:44:06.965 INFO EDCORE: C7B9F202 009EE550 0000:00000000 D:\DCS World\bin\edCore.dll luaopen_i_18n()+612 2019-01-27 10:44:06.967 INFO EDCORE: C7B9F48F 009EE590 0000:00000000 D:\DCS World\bin\edCore.dll luaopen_i_18n()+89F 2019-01-27 10:44:06.968 INFO EDCORE: C7B9F6DA 009EE6F0 0000:00000000 D:\DCS World\bin\edCore.dll luaopen_i_18n()+AEA 2019-01-27 10:44:06.970 INFO EDCORE: C7B9FFB7 009EE730 0000:00000000 D:\DCS World\bin\edCore.dll ?vfs_mount@@YAIPEBD0H0@Z()+17 2019-01-27 10:44:06.970 INFO EDCORE: DB1F13FA 009EE860 0000:00000000 D:\DCS World\bin\World.dll 2019-01-27 10:44:06.970 INFO EDCORE: ED19A247 009EE8B0 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.971 INFO EDCORE: ED196245 009EE930 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.971 INFO EDCORE: ED196854 009EEAC0 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.971 INFO EDCORE: DB0C7294 009EEB00 0000:00000000 D:\DCS World\bin\lua.dll luaD_growstack()+7A4 2019-01-27 10:44:06.972 INFO EDCORE: DB0D727B 009EED10 0000:00000000 D:\DCS World\bin\lua.dll luaS_newlstr()+4E5B 2019-01-27 10:44:06.972 INFO EDCORE: DB0C7581 009EED40 0000:00000000 D:\DCS World\bin\lua.dll luaD_growstack()+A91 2019-01-27 10:44:06.972 INFO EDCORE: DB0C23B6 009EED70 0000:00000000 D:\DCS World\bin\lua.dll lua_call()+26 2019-01-27 10:44:06.972 INFO EDCORE: C7BBE8C7 009EEDA0 0000:00000000 D:\DCS World\bin\edCore.dll ED_lua_loadfile()+307 2019-01-27 10:44:06.973 INFO EDCORE: DB0C7294 009EEDE0 0000:00000000 D:\DCS World\bin\lua.dll luaD_growstack()+7A4 2019-01-27 10:44:06.973 INFO EDCORE: DB0D727B 009EEFF0 0000:00000000 D:\DCS World\bin\lua.dll luaS_newlstr()+4E5B 2019-01-27 10:44:06.973 INFO EDCORE: DB0C7581 009EF020 0000:00000000 D:\DCS World\bin\lua.dll luaD_growstack()+A91 2019-01-27 10:44:06.973 INFO EDCORE: DB0C23B6 009EF050 0000:00000000 D:\DCS World\bin\lua.dll lua_call()+26 2019-01-27 10:44:06.973 INFO EDCORE: C7BBE8C7 009EF080 0000:00000000 D:\DCS World\bin\edCore.dll ED_lua_loadfile()+307 2019-01-27 10:44:06.974 INFO EDCORE: DB0C7294 009EF0C0 0000:00000000 D:\DCS World\bin\lua.dll luaD_growstack()+7A4 2019-01-27 10:44:06.974 INFO EDCORE: DB0D727B 009EF2D0 0000:00000000 D:\DCS World\bin\lua.dll luaS_newlstr()+4E5B 2019-01-27 10:44:06.974 INFO EDCORE: DB0C7581 009EF300 0000:00000000 D:\DCS World\bin\lua.dll luaD_growstack()+A91 2019-01-27 10:44:06.974 INFO EDCORE: DB0C688F 009EF480 0000:00000000 D:\DCS World\bin\lua.dll lua_getinfo()+11CF 2019-01-27 10:44:06.974 INFO EDCORE: DB0C789E 009EF4C0 0000:00000000 D:\DCS World\bin\lua.dll lua_yield()+9E 2019-01-27 10:44:06.974 INFO EDCORE: DB0C2450 009EF510 0000:00000000 D:\DCS World\bin\lua.dll lua_pcall()+60 2019-01-27 10:44:06.975 INFO EDCORE: C7BBD42A 009EF550 0000:00000000 D:\DCS World\bin\edCore.dll ED_lua_pcall()+5A 2019-01-27 10:44:06.975 INFO EDCORE: ED195AA4 009EF580 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.975 INFO EDCORE: ED1976EE 009EF680 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.975 INFO EDCORE: ED195BF9 009EF700 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.975 INFO EDCORE: ECE0D295 009EFE50 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.977 INFO EDCORE: ED3209E3 009EFE90 0000:00000000 D:\DCS World\bin\DCS.exe 2019-01-27 10:44:06.977 INFO EDCORE: F4B27E94 009EFEC0 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14 2019-01-27 10:44:06.977 INFO EDCORE: F4D0A251 009EFF40 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 2019-01-27 10:44:07.085 INFO EDCORE: Minidump created. 2019-01-27 10:44:07.089 INFO DCS: try to write track file 2019-01-27 10:44:07.090 INFO DCS: 'D:\Users\<USER_NAME>\Saved Games\DCS\Logs\dcs.20190127-104407.crash' deleted successfully 2019-01-27 10:44:07.156 INFO DCS: 'D:\Users\<USER_NAME>\Saved Games\DCS\Logs\dcs.20190127-104407.dmp' deleted successfully 2019-01-27 10:44:07.156 INFO DCS: failed to open '' for reading === Log closed.

Please could you consider keeping the same keystroke for the same phrase across different submenus, for those of us who are using voice recognition software. e.g. if "Check out" is assigned to F3 in one menu, then please could it also be assigned to F3 in all other menus? Or is there any way this could be configured by the user in a config file?

Not just you. https://forums.eagle.ru/showthread.php?t=226369

Thanks for replying, and congratulations on your first post. I feel honoured. :thumbup:. Another descriptor that comes up often in the NATOPS is e.g. After AFC 327. Any ideas what that's about? It would be nice to know which "versions" ED have settled on implementing. Although, it's possible to guess through a process of elimination:

Entirely agree. Personally I would be quite happy to pay for this type of upgrade. They could just call it the A-10C v2.5. (like they did with BS2). I don't see why people expect it to be upgraded for free indefinitely. It's tricky though, as this has resulted from their engine upgrade. This means you are paying for something you DO want by buying something that you (possibly) DON'T. I would argue that that distorts the market, and ends up with a range of aircraft being produced that few are actually interested in.

Don't do what?

Just skimmed this thread so sorry if I'm repeating what's already been said. In a similar situation, I feel something's off. I was trying to do touch and goes on the runway. I touch down, set flap to half, full military power, if I don't hold the stick far forward the f18 will pitch up into the vertical. It feels very wrong. Maybe I'm doing something wrong?

"TBH and it's a personal preference however for me PD @ 1.2 or even 1.1 and MSAA @4 looks and flows better in VR. I also run the settings mostly on high except shadows low/flat and attempt to keep either CPU and or GPU from hitting 100%. " Yeah same here, except I try to go for 90 fps with not much going on, and find I need to put almost everything on low. Kegetys's mod gets me another bump up. Sayin' nothing about missions with lots of objects doing their thing... that's an issue for another day. (e.g. Ka-50 "Battle" mission - not really playable).

Nope.

Exactly my thoughts - at first. However, having used the Touch controllers for Dash whilst running games, I found that in practice, it's not as terrible as it sounds (place Touch controller on thigh, muscle memory, etc). I'd say wait and see. If done well it could be very useful.

Reading through the NATOPS I find many references to different mission computer OFPs, which I assume is something like a version number. If so which MC OFP does a LOT20 F/A-18C have, and is this being simulated in the DCS version? If anyone can explain in simple terms what on OFP is, that would be great too. Thx (The only F18 thread I could find with OFP in the title was over 400 pages long. Just... no).

I was testing* the other day and noticed that turning (cockpit) shadows on made little difference in the A-10C, but in the F-18 caused a considerable fps drop. Have you tried turning shadows off? I'm guessing all those extra details in the F-18 cockpit -> a lot of work for shadows / lighting. Generally I do get lower fps in the F-18, but as stated, it's more complex graphically, and remains in early access. And don't get too excited just yet, but there was some good VR news today. *it was a very quick test, so sorry if I've got this wrong. And it was in Caucasus as I don't own PG.

"Optimized VR performance". I'm starting to get excited. Let's have some more details please ED! Thank you ED. Great to get some official good news on this, following the severe performance drops incurred, especially in VR, when the switch was made to deferred rendering. The Touch stuff sounds intriguing, it'll be very interesting to see what sort of implementation can be achieved. Although personally, I'll be hanging on to my HOTAS, it's great to see this sort of VR innovation. I think Oculus prefer to call it the "grip button". For some reason middle-finger button sounds slightly rude to me ;)

Everything you ever wanted to know but were afraid to ask... Is very well explained here

After deciding that personally I prefer to have SPUD turned on (for the reasons I mentioned above), I had a look around on the internet and tried the following: Stop Oculus service (net stop ovrservice) Delete the files in %localappdata%\Oculus\Spud (Always back up just in case). Start Oculus service (net start ovrservice) The files are downloaded again, and one was slightly different. It could very well be a placebo and wishful thinking, but I'd swear that the Mura is not as bad as it was. A reboot might be necessary before the change kicks in.

Has something been changed in the last (ED beta) update? Flying the same mission I based my comments (above) on, I find the terrain textures are now black. Much, much improved from last week. I've been making quite a few changes on my PC and testing recently, so it could well be something I've done. Possibly shaders not recompiling?