SPAS79

For that problem, the issue is you have to move the throttle pinky switch to the aft position first, and before that you need to have your inverter on (either on ext pwr or from a generator, APU or eng doesn't matter). About the IFFCC thing, IDK I always skip the BIT LOL. BUT IIRC when you are in the "middle" position you have to press the "ENT" key on your UFC to engage the BIT, otherwise it just sits there. Hope this helps.

And it turned out to be the issues with the Garmin 430 module. I've disabled it and it seems to work as it should now. I know the thing is listed in the "known issues" but I had the feeling that it wasn't really "in my face" enough... Sent from my SM-G930F using Tapatalk

I'm still getting the flashing menu error after I ran a clean/repair of my install. Tried resetting the install path in VAICOM's options: nothing Tried deleting export.lua: nothing. It just does not work. I'll put vaicom aside for a while I guess... although this seems an ongoing, unsolvable issue from what I see in the forums.

Sorry for necroing this but this takes an unhealthy amount of time to start DCS each time... both in VR and non-VR... is this normal?

Of all the italian singers, WHY Pupo?

So it seems I can't load campaigns or missions. DCS.log gives this message after a while 2020-03-08 08:18:05.960 DEBUG LuaGUI: GUI Error: [string "./MissionEditor/modules/me_autobriefing.lua"]:122: attempt to concatenate field 'dialogsDir' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_autobriefing.lua"]:122: in function 'create_' [string "./MissionEditor/modules/me_autobriefing.lua"]:355: in function 'show' [string "./MissionEditor/modules/me_campaign.lua"]:1013: in function 'func' [string "./MissionEditor/modules/me_wait_screen.lua"]:72: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>an then hangs at the loading screen. It seems like DCS does not know what "dialogsDir" is, so I have found out that changing this line (into my me_autobriefing.lua) window = DialogLoader.spawnDialogFromFile(base.dialogsDir .. "briefing_dialog.dlg", cdata) into this window = DialogLoader.spawnDialogFromFile("F:\\DCS World\\MissionEditor\\modules\\dialogs\\" .. "briefing_dialog.dlg", cdata) solves the problem. Obviously this is not a solution for everybody (DCS install dir will be different) but I think it still warrants a look. I must NOT be the only one with this issue. Peace out.

I'm having a similar issue... with a slightly different file but same structure. Did you manage to find a solution to this? 2020-02-29 19:15:06.722 ERROR_ONCE DX11BACKEND: render target 'mainDepthBuffer_copy' not found 2020-02-29 19:15:06.722 ERROR_ONCE DX11BACKEND: render target 'DummyShadowMap' not found 2020-02-29 19:15:07.660 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_autobriefing.lua"]:122: attempt to concatenate field 'dialogsDir' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_autobriefing.lua"]:122: in function 'create_' [string "./MissionEditor/modules/me_autobriefing.lua"]:354: in function 'show' [string "./MissionEditor/modules/me_openfile.lua"]:627: in function 'func' [string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>

Yeah, seen in the Ka-50. Rift S.

Can't this just be edited out with a skin?

Right. Just a case of me being a stupid ass. I normally export mfds on screen 4 and 5, under some thrustmaster cougars. Seems like my Shkval export decided to appear just around the HUD, thus why black when turned off and gray when on... :D reverting to one of the standard "screen" (1 Screen) .lua files fixed it. I can live with that for VR. The funny thing is this didn't happen before, nor it happens with any of the other modules. Case closed?

Bignewy, Yes I've done that, I have uninstalled all mods and run cleanup/repair (from Skatezilla's update utility, but it should be the same...). Then uninstalled the Ka50 module, deleted the whole mods/aircraft/Ka50 folder under DCS root and the same under Saved Games\DCS. No joy. I guess it's some .hlsl somewhere... even though clean/repair should have taken care of that... I guess I'm up for a full uninstall/reinstall...

Yeah, I did that as well, and made sure no leftover "Ka-50" files or folders were in either the main DCS folder and the DCS folder under my "Saved Games". No joy. I think a full reinstall of DCS is in order...

The issue comes up with both the Steam and the Oculus VR API. I'll try and paste a screenshot as soon as I can. I do not have any track files, as I shut it off every time (I haven't flown it with the square in place). To me, it looks like the "transparent" texture sitting behind the HUD (the yellowish/green baked in "halo" so to speak) is missing or broken with the VR shaders, thus the sim places a black square there. Might have to do with me trying those modded VR shaders (although I tried to remove them and ran a restore+clean a couple of times for good measure...) The other thing I'll try and do is save the log from the VR and non VR versions while loading, maybe that helps.

Done Also done Drivers are up-to-date as of current, v 442.19 on Geforce 2080ti Thank you for your answer, this is realy annoying though... ...

Hi, I was trying ouy the new cockpit in VR, and I get the issue as in the image attached, which is one big black (or gray, depending I think on the day/night mode of the hud). Please pay no attention to the fact the Ka50 is "off" in the attached the issue is present in all states, it seems to be tied to how the game renders the HUD in VR. Headset is Rift S. No Mods are applied. Also, I am not seeing the same in 2d mode... Anybody having this issue?

Same here. Then ended up in this thread as I was starting to think I had dreamt of the whole thing. Oh well, can wait another week.

Well I'm going to sorta kinda necro this, but I have them and I fixed them today. Still, can't figure out how to make them interact with DCS...

Yes, your "in cockpit" MFDs will virtually disappear... Sent from my SM-G930F using Tapatalk

Is this downloadable somewhere? also, does it pass IC?

...aaaaand that prayer has been answered in 2020 by Microsoft. Who would have known at the time, huh?

nope, still looks weird.

....aaaand it didn't work. Still getting the same error. EDIT: I missed deleting two files which were not in the ..\Saved Games\DCS\Scripts\Twitch2DCS\ folder, but lived in the ..\Saved Games\DCS\Scripts\ and ..\Saved Games\DCS\Scripts\Hooks\ folders (Twitch2DCS.lua and Twitch2DCS-boostrapper.lua, respectively). With those deleted we're back to normal.

I am pretty sure I didn't... and have run the repair/cleanup several times. Although one more time wouldn't hurt, I guess. Later with the results.

how to uninstall? I've tried deleting the folders, but then I get this message at the startup?

nobody dealing with this? :doh: