SPAS79

I am divided between answering to you with the same sarcasm or just saying something sympathetic... Sent from my SM-G930F using Tapatalk

On a second thought, I'll attach a JSGME/OvGME ready archive as soon as I'm back home. EDIT: the issue is that when you go USE_LCD_MFD = false, the EHSI export becomes unrecoverably unreadable... I have yet to find a workaround to this.

I'm going to type up a quick answer, will articulate later. In short, you have to change the ONLY line in config.lua from "USE_LCD_MFD = true" to "USE_LCD_MFD = false". Then it's a case of editing the two right and left .lua files to make the lines appear normal and not a blurry mess. Seriously, have a look at my files, or just copy-pase them in your F16 directory (backup the originals first).

I'll attach my files. It is a combination of telling the system you're not using USE_LCD_MFD (with config.lua) and then setting stuff as I have in my MFCD_x files. MFD_left_init.lua MFD_right_init.lua config.lua

With USE_LCD_MFD set to False in the F-16C config.lua (which I need because MFCD readability), my EHSI looks like this

Same here... don't know why tho... this also seems to be random, or mission dependent... some missions simply generate the whole pages. Also, the beacons pages also do the same, they are either all blank (transparent) or tend to generate some blank pages. Weird.

To me, this is still happening with build .12

Does not work for me... all I get it fuzzy MPCDs and I'm not able to fix them.

And then again, it does not work. Same conditions, same pilot. DOES NOT WORK.

So... progress. For some reason it decided I should have worked, and it did. Until it crashed.

I'm pretty sure I'm within the limits. I'll try make a recording of the session, then abandon this piece of crap forever and fly what flies and behaves like a helicopter. Also, I flew robinsons IRL, not as twitchy as the gazelle... not even the R22...

Can't make it work for the life of me...

See, I didn't know that and constantly tried to stay within the limits... silly me.

Yes it is available with the rift, seems like some games do work if set in compatibility for Win7 (E:D used to work with it when OVRDrop was in beta) but I had no luck so far in DCS. Putting it in Windows7 mode makes VR non-usable for some reason...

And I thought I posted there and could not find my post anymore... Sorry for double posting.

consider 1 kn = 1Nm per hour. 60kn = 60Nm/hr -> 1Nm per minute 90kn = 90Nm/hr -> 1.5Nm/min 120kn = 120Nm/hr ->2Nm/min Ballpark figures but they help me estimate time/distance to do dead reckoning. That + map reading... Now that I'm considering this, I'm not sure if the miles we use in DCS are statute or nautical? Flying naturally calls for nautical, but...

Thanks. Now I know absolutely nothing about how DCS scripting works - but I just want to say this, maybe it will help, maybe not. Worst case, you take this post and throw it into the bin. But, let's assume that to pick up (hook) a cargo crate. You have to "tell" the system which one you want, that is: selecting it with F1-F12. This, I would expect, causes some information to get stored in some variable somewhere - if not you would not be able to hook THAT crate. Now, you could monitor when that variable gets populated (e.g. by the user making a choice, either with F1-F12 or with their mouse) which is an indirect way of knowing that a choice from the radio menu has been selected. Obviously this would need to happen ONLY after you are X meters away from the cargo, and again, IDK if DCS gives you any way for measuring that... Once that has happened and the user presses the hook cargo button, then the audio cue plays. ...or just leave it as it is and ignore the blabber. It is a minor issue anyway. You have a great day, thanks again for the hours of fun!

In fact I did check and notice there was no cable when on ground, and no load hanging from my heli when up... But I assumed it was a glitch, as I assumed that the message given by the AI copilot must have been triggered by an event that had taken place. Sorry I was trying to be funny, I realize we're trying to correct bugs here so here's the account, given as technically as I can: Looks to me the AI/script it does monitor the 'hook cargo' command, as the audio snippet was played just after I pressed the 'hook cargo' button... It would be useful if you could monitor the radio call (F6 -> All cargos etc...) for cargo AND the 'hook cargo command' and play the audio cue only if the two conditions are met. EDIT: and Greg: thanks for taking criticism so graciously! :D

SECONDED Also, mission 8, that scumbag of a copilot deceived me into thinking we were slinging a glitched cargo (i.e. it wasn't hooked, I heard him saying "ok now take off and go slow" and thought, "ok, we have it and it's not displaying for a glitch) and found out the hard truth when I landed on the carrier... - see here at minute 30:30) I know it was my fault as I didn't really do the F6-all cargo procedure but still, why do you tell me to take off and go carefully? Why? The thing could really do with some less reading the full backstory and a bit more details / scripting...

Ok here So I get there, spot the ginormous C-17, land, click the "hook cargo" command (without the radio works with F6-allcargo-etc...) and at minute 30:30 is where it got me. It literally tells you "Good job captain! Now get back to the ship. Gain some altitude to avoid damaging our cargo". So I thought, OK, it must have glitched and I have the cargo hooked and we're ready to go. So I lift up and I THINK I have it hooked but because of the glitch it is not showing. I trod all the way back to the ship in the shittiest weather god has ever conceived (I would like to see a pilot that wants to fly in that IRL, but hey, this is a game an that is where the fun is) I make it back to the "USS somewhat Something", land on the deck, breathe a sigh of relief and click the UNHOOK cargo... ... ... NOTHING HAPPENS! This means I have to re-fly this thing because the scumbag major/useless copilot/even more useless aircraft commander told me we were good to go at minute 30:30... Talk about annoying minor glitches.

Thanks. That was useful! Now if that information just was in the brief (and I understand why not) or in the spoken cues while you fly. Instead, your copilot and helicopter commander sits there like a black hole. Not even light can escape, let alone words (like 'that one over there at your 9 o clock...' or something like that). I'll try that again.

Mission 6: You are at FOB (Olympus?) and about to sling load cargo back and forth to the Argo when the FOB gets attacked. Fast forward a bit and you have to transport the wounded to kobuleti military hospital, ADF 490. 1) There's two ADF transmitting around 490, so picking the correct one is not the easiest thing. But you can do it with a little guesswork 2) When properly tuned, the ADF brings you to Kobuleti airport's ADF. I was about to land on the building thinking it was the hospital when I saw the antennaes... I have gone around the airport (probably making the controller swear in 12 different languages) but could not find a hospital. I've landed in a depot, in a fuel depot but no hospital in sight... Am I missing something? (the full video is on my twitch channel, I'll move it to youtube in the next few days).

Yeah, A risk you would not take... Although it's doable...

This is not working for me... I don't know why but it does not load anything, as it seems EDIT: not, it does, safe for a couple of textures missing (oilrig, AAA guns) STILL can't see the hospitals in THIS MISSION

My same conclusion... I am still searching a way to do that