netizensmith

As title. Tried in 2D at 1440p and at 4K and in VR on an HP Reverb G1. Previously the MFDs were highly readable to me on both my 4K Flat display and in VR. Now all the symbology seems to have a black outline around it that renders it borderline unreadable in 2D and literally unreadable in VR. Discussion and evidence can be found in this thread:

It's not environments. It's this week's update vs the version prior. We can see that they are applying outlines in places they weren't before. I can't find a quick fix though. Hopefully they'll revert.

Thanks @imacken this shows that the colours have not in fact changed. There's more to it than that.

I'll try to fix the colours later. If anyone has a copy of the old MPCD_definitions.lua file that would help. The entire old " mods\aircraft\AV8BNA" folder hierarchy zipped up would be even better. EDIT: Ok, the colours are the same as before so it's something else... I don't know what. Could someone post the whole of the AV8NA folder?

Change mods\aircraft\AV8BNA\Cockpit\Displays\Display_StrokeDefs.lua to look like this: stroke_thickness = 0.5 stroke_fuzziness = 0.4 -- Currently is used for DMC generated fonts black outline --DMC_outline_thickness = stroke_thickness * 3 --DMC_outline_fuzziness = stroke_fuzziness * 1.1 DMC_outline_thickness = 0 DMC_outline_fuzziness = 0 DMC_stroke_thickness = 0.65 DMC_stroke_fuzziness = 0.42 Now all outlines are gone. That's not the end of the story though. They changed the default colour values to assume font outlines so these need to be made darker but I don't have time to do that right now. The colours are defined in MPCD_definitions.lua

I see complaints on here "How can Company X release the module with an error like this!?", well, they released a multi-million dollar actual aircraft with a moving map that can't actually be used so you can kinda see how that could happen.

I would say that the colour map display is, globally, worse in VR with yesterday's release than it was before. In 2D I think the colour map is more readable with the default green, or white text than it was before. All other colours are unreadable, particularly blue which was actually the best colour prior to this. Overall I'd much rather what we had before. Just tried the Hornet. Hard to tell with that because the colour map symbology was always unreadable, and continues to be, plus you can't change its colour.

You can "step" between the pods. I believe by default it will cycle through them as you fire, so you'd have to override this manually if you had two different varieties onboard.

Aha! Explains why 1688 is the only code that worked for me. Cheers. Again though, weird UI. Working here I'm afraid. Although I reckon the TDC slew X-Axis is ignoring my curves. It goes from not moving to super speedy despite curves of 40. I'm using the analog stick on a VKB Gladiator for reference; gave up on the warthog throttle analog thingy.

Thanks. I see 3 separate entries; 11X1, 111X and another one, with presumably the option to set a value for X. Does this mean that setting the TPOD laser code to any one of those 3 will work? Bizarre system.

So setup is literally select them in stores, fire a laser at something (doesn't matter what the laser code is seemingly), get to within 5 miles ish and launch. Is it really that simple?

Big update today, announced right here on the ED forum.

So have to start cold remove chocks before hitting auto start for now?

Update: Same mission last night. First lot of 2 65Fs released, all went well. Landed, loaded 4 more, took off, Master arm on, A/G, 65Fs selected, chose Mav View. nothing, no countdown timer. After 3 minutes the view came life, 65F released, next lined up and same issue, took another 3 minutes to warm up but no timer displayed. Rearming seems to be the issue. Not sure if it's supposed to do this but when I went to rearm the 65Fs were still showing on my loadout.

I think I just had similar: Took off with 2 x 65Fs. Didn't use them, landed, refuelled and replaced 2 x HARMs with two more 65Fs. Fired my first one. Second one would not show Mav View, no countdown timer, could not cage/uncage and the Mav inverted triangle was rendered above the velocity indicator. After a while it started working (i had switched to Air 2 Air, master arm off etc. in an attempt to get it to work). Reading the above I wonder if it was actually redoing the timer but not telling me.

Additionally loads of things (everything?) external to the forum that used to link to forum posts here no longer work. This is an absolute nightmare as tons of things point to this forum as explanations on how things work, where to find info, where to find mods etc. It's not an exaggeration to say that support for the DCS community has been massively compromised by whatever change to the forum has caused this. As an example everything in the Hoggit wiki on Reddit - https://wiki.hoggitworld.com/view/Hoggit_DCS_World_Wiki - is now broken.

To add confusion, on a Reverb G1 100% is pretty much the actual native res of the headset i.e. not a supersample. If I set my slider to 54% it shows a lower res than the G2 does at 54%. EDIT: I see Imacken already mentioned this so consider this as confirmation as I have a G1.

A friend and I have both had this recently too. Both times we had been flying for at least half an hour in a mission I'd say and the bomb fall line was about 30 degrees off the vertical. Did not change when turing around 180 and approaching from the opposite direction; always 30ish degrees left of vertical, similar to screenshot above. EDIT: Mission Date is 21st June 2016

Just adding my name to the list. Happens all the time, DESG or not, NAV or A/G.

Ok this looks promising. I went delving into the two tracks. In the options file for the 2D mode we have this: ["plugins"] = { ["Su-25T"] = { ["CPLocalList"] = "default", }, -- end of ["Su-25T"] ["AV8BNA"] = { ["CPLocalList"] = "default", ["INS_Alignment"] = 2, ["INS_GYROHasNAV"] = false, ["MPCD_EXPORT"] = false, }, -- end of ["AV8BNA"] whereas in the VR file we have this: ["plugins"] = { ["Su-25T"] = { ["CPLocalList"] = "default", }, -- end of ["Su-25T"] ["AV8BNA"] = { ["CPLocalList"] = "default", ["INS_Alignment"] = 0, ["INS_GYROHasNAV"] = false, ["MPCD_EXPORT"] = false, }, -- end of ["AV8BNA"] Are these options that I've set somehow? Indeed yes! So I use the DCS updater/Launcher by Skate Zilla and it seems that even though I choose my VR profile, as soon as I launch using the "VR/ON" launch button it quickly switches to its own VR Headset profile (no idea where it gets this from) and when I check in the special tab for the AV8B, shure enough INS is set to not aligned. Mystery solved. Not a bug (not for Razbam or ED anyway, possibly for Skate Zilla but I'll read the docs to see what's going on there)

Thanks. Have uploaded a VR track and a 2D track. 2D.trk vr.trk

Issue: From a cold start the automatic startup sequence usually takes the INS switch to the IFA postition but in VR mode it only goes to the GND position, leaving you without a working compass etc. Can be disconcerting for new players who have always played the game starting from hot. To reproduce: Launch DCS in VR mode Play the instant action, Cold and Dark Choose auto startup and allow it to complete Check the INS switch Workaround: After auto startup completes, turn the INS knob to NAV or IFA