AndyB

Yeah, I would imagine if enough people start having problems they'll address it(hopefully). It seems to be an issue in "tempMission" in the temp file or so it says.

It only seems to happen if the track is longer than a few minutes

I just turned it off, installed it, turned it back on. Haven't had any issues.

Just had this issue go to windows search bar, type in virus and open, "Virus & threat protection" then, "manage settings" turn off, "Real-time protection" run the updater and install the update. Turn real time protection back on after install. Worked like a charm for me

Found out you have to desginate the airport as blue on the afghanistan map. Either other maps dont require this or it happens automatically on other maps. Either way, put a blue tarp down, or go into the airport settings in mission editor and designate it blue and cc responds now

Found out you have to make the airport "blue" otherwise it doesn't respond. Works fine now

I thought I was doing something wrong at first but then came to find that I can't use the crew chief at all on the Afghanistan map, in any jet. Canopy open or closed, battery on. Any other map works just fine, I switched to the Iraq map, no issues. I'm not sure if this affects other radio items such as, atc, haven't tested that. Afghanistan Crew Chief Bug A-10.trk Afghanistan Crew Chief Bug F-18.trk Afghanistan Crew Chief Bug F-14.trk Afghanistan Crew Chief Bug F-16.trk Crew Chief Iraq.trk

It seems to be a bug on the Afghanistan map. Had no issues talking with crew chief on any other map. A-10 Afghanistan Wheel Chock Bug.trk A-10 Wheel Chock Working Correctly.trk

Well aware, either way, as I mentioned above, it didn't make a difference, canopy open or closed. Yes I will upload one soon

Yeah I've seen that, my problem is regardless with intercom on, canopy open or closed, crew still doesn't respond. Transmitting 251.000 on uhf/vhf if that matters (can't see why it would) I'll try pulling chocks before engine start with battery, intercom, and canopy open first and see if that works

I can't seem to get the ground crew to respond to any requests, specifically the wheel chocks. Selected Intercom, battery is on, engines running. No response, canopy open or closed. This was also on the Afghanistan map, maybe it's a bug, but I have a feeling I'm missing something.

Thank you, I'm glad you liked it!

This took a while to make and was quite a bit of work, but I had a lot of fun making it. I hope you guys enjoy.

So it's kind of a pain, but you can make this happen. It's livery specific so if you want all F-18's in the game to have their wings unfolded on the ground, you have to go into each livery folder and edit the Lua file. At the end, custom arguments [8] = 0, It also only works in single player or in multiplayer if everyone has the same livery, otherwise everyone else will see your wings folded.

That did it, Thank You!

Unfortunately that didn't work either. Still getting the same issue. I removed all mods from saved games. # -------------- 20240730-171130 -------------- DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631) C:\WINDOWS\SYSTEM32\VCRUNTIME140_1.dll # C0000005 ACCESS_VIOLATION at 00007ffd433811d1 00:00000000 SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew' OS-Version: 10.0.22631 () 0x300-0x1 0x00000000000011d1 (VCRUNTIME140_1): __NLG_Return2 + 0x81 0x0000000000004957 (VCRUNTIME140_1): __CxxFrameHandler4 + 0x877 0x000000000000f886 (VCRUNTIME140): __C_specific_handler + 0x1E6 0x00000000000a50cf (ntdll): __chkstk + 0x1AF 0x0000000000020154 (ntdll): RtlUnwindEx + 0x274 0x000000000008f6ae (ntdll): __C_specific_handler + 0xDE 0x00000000000a504f (ntdll): __chkstk + 0x12F 0x000000000001e866 (ntdll): RtlFindCharInUnicodeString + 0xA96 0x00000000000a403e (ntdll): KiUserExceptionDispatcher + 0x2E 0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE 0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0 0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5 0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6 0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C 0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77 0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87 0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6 0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461 0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B 0x000000000090bdd8 (DCS): SW + 0x422578 0x000000000090a886 (DCS): SW + 0x421026 0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9 0x0000000000cb85de (DCS): SW + 0x7CED7E 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D # -------------- 20240730-171119 -------------- DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631) X:\DCS World OpenBeta\bin-mt\Visualizer.dll # C0000005 ACCESS_VIOLATION at 00007ffcea13360e 00:00000000 SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew' OS-Version: 10.0.22631 () 0x300-0x1 0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE 0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0 0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5 0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6 0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C 0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77 0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87 0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6 0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461 0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B 0x000000000090bdd8 (DCS): SW + 0x422578 0x000000000090a886 (DCS): SW + 0x421026 0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9 0x0000000000cb85de (DCS): SW + 0x7CED7E 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D

DCS-MT crashes on the loading screen only in VR. It will load in 2D just fine. DCS-ST works just fine in both 2d and VR. I've repaired DCS, removed all user mods, cleared fxo and metashaders folders, uninstalled and reinstalled oculus app for Quest 3. I don't know what to do. I get 2 different crash logs. Somebody please help. # -------------- 20240730-163802 -------------- DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631) C:\WINDOWS\SYSTEM32\VCRUNTIME140_1.dll # C0000005 ACCESS_VIOLATION at 00007ff8c57911d1 00:00000000 SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew' OS-Version: 10.0.22631 () 0x300-0x1 0x00000000000011d1 (VCRUNTIME140_1): __NLG_Return2 + 0x81 0x0000000000004957 (VCRUNTIME140_1): __CxxFrameHandler4 + 0x877 0x000000000000f886 (VCRUNTIME140): __C_specific_handler + 0x1E6 0x00000000000a50cf (ntdll): __chkstk + 0x1AF 0x0000000000020154 (ntdll): RtlUnwindEx + 0x274 0x000000000008f6ae (ntdll): __C_specific_handler + 0xDE 0x00000000000a504f (ntdll): __chkstk + 0x12F 0x000000000001e866 (ntdll): RtlFindCharInUnicodeString + 0xA96 0x00000000000a403e (ntdll): KiUserExceptionDispatcher + 0x2E 0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE 0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0 0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5 0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6 0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C 0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77 0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87 0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6 0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461 0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B 0x000000000090bdd8 (DCS): SW + 0x422578 0x000000000090a886 (DCS): SW + 0x421026 0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9 0x0000000000cb85de (DCS): SW + 0x7CED7E 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D # -------------- 20240730-163741 -------------- DCS/2.9.6.58056 (x86_64; MT; Windows NT 10.0.22631) X:\DCS World OpenBeta\bin-mt\Visualizer.dll # C0000005 ACCESS_VIOLATION at 00007ff873d8360e 00:00000000 SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Andrew' OS-Version: 10.0.22631 () 0x300-0x1 0x00000000001f360e (Visualizer): TransformComponent::validatePositionsTree + 0x6E8BE 0x0000000000001080 (VCRUNTIME140_1): (function-name not available) + 0x0 0x0000000000002715 (VCRUNTIME140_1): __NLG_Return2 + 0x15C5 0x00000000000a4896 (ntdll): RtlCaptureContext2 + 0x4A6 0x00000000001b3fbc (Visualizer): TransformComponent::validatePositionsTree + 0x2F26C 0x0000000000195bc7 (Visualizer): TransformComponent::validatePositionsTree + 0x10E77 0x00000000001957d7 (Visualizer): TransformComponent::validatePositionsTree + 0x10A87 0x000000000011f136 (Visualizer): try_get_HMDcontroller_pos + 0x8DC6 0x0000000000109211 (Visualizer): TerrainRenderer::updateSharedParams + 0x2461 0x000000000010c3ab (Visualizer): HMD::initialize + 0x41B 0x000000000090bdd8 (DCS): SW + 0x422578 0x000000000090a886 (DCS): SW + 0x421026 0x00000000022358bd (DCS): AmdPowerXpressRequestHighPerformance + 0x11C18B9 0x0000000000cb85de (DCS): SW + 0x7CED7E 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D dcs.log-20240730-163802.zip dcs.log-20240730-163741.zip

Check out Hornet School. Amazing DCS Community designed to teach people the Hornet. https://sites.google.com/view/hornetschool/home https://discord.gg/thehornetschool

Update: what I thought was a clear image in the Rift S has been overwritten by the quality of the Quest 3. I now realize it was in fact not even close to being clear. I have no issues now.

I need some help. In VR in the F-18, for some reason I can't actually identify what I'm looking at in the atflir until I'm with in 3-4 or so miles and sometimes closer. The image is clear, not blurry, it just doesn't seem to fully render until I'm with in those ranges. Typically at 20,000ft asl in a 10 mile orbit. I'm in IR mode, I turn off alg, manipulate the gain, contrast, brightness, and the one above gain(sry forgot what it was called) and just cannot make out what I'm looking at. I can see big bombers from a little farther out but smaller targets like technicals, infantry, or even tanks, I have to be damn near on top of them to have any detail to see them. I'm thinking it's a setting issue of some kind somewhere. Or maybe I'm doing something wrong in the Hornet. Settings: Resolution: as small as possible for desktop Res of cockpit displays: 1024 every frame Anti-Aliasing: MSAA 4X Textures: High Terrain Textures: High Shadows: High Visible Range: Extreme Secondary Shadows, SSS, SSAO, SSLR: Off Scenery Details Factor: 1(max) Preload Radius: Max LOD Switch Factor: 2 Anisotropic Filtering 16X Terrain Object Shadows: Default Gamma: 2.2 Pixel Density: 1.5 MSAA Mask Size: 1.0(max) Enable hmd Mask: checked System Specs: Rift S Asus Rog Strix Z670E Motherboard Ryzen 9 7900x Asus TUF RTX 4080 64gb Trident Neo DDR5

The only way I know of, is by nws depress to switch L+S to that contact(assuming your radar sees it and it's not just a data link contact) Otherwise you'd have to drop the lock to get bullseye cursor information. I think that's built into the logic for a good reason.

I've also been experiencing this. Will upload a trk file soon

A little hobby of mine in recent years has been recreating US Tacital Demonstrations. This one being the Navy's Rhino Demo Team, flying the F/A-18F Super Hornet. This one was challenging given that the CJS Super Hornet uses the ED Hornet's FM, so we had to get creative with some of the maneuvers. I hope you enjoy!!

Just played this mission. It's still a bug. Ejected lol

Oh yeah I think you're right lol and haha yeah for sure.