Krazee

This one has bugged me for years, since I like to fly Helos and you see it more often down low. It's probably such a simple fix too. Bring the powerlines forward in the rendering hierarchy?

Yes! Definitely an improvement in the mirrors. I can't even see the seat or tail of the aircraft in my mirrors no matter how I adjust my position.

Does anyone know if there are any adjustments for the mouse cursor restrictions in VR? I have it set to stay in the boundary of the screen so I don't lose focus but when in cockpit, the mouse cursor seems to be restricted to an invisble bounding box, which doesn't extend to everywhere I want the cursor to go. An example is for switches and knobs on the panels at the side of the seat. When I go to click switches, my chin is on my chest, I can see the switch clearly but the cursor can't reach it. I have to physically shift my whole body position to the side to reach it. Any ideas?

So I'm on 2.5.6.43931 and I'm having a few problems. I'm not able to bring up comms menu items so I'm unable to communicate with wing men or atc in game. When the mission loads in, you usually get a splash screen on which you press the fly button to start the mission. It no longer appears so I have to hit escape and then resume.

I don't know if this is just me (hence the query) but I noticed when flying in my Helo in the Caucasus the other day that as I flew under the power cables and looked up towards the clouds, the black cables disappeared behind the clouds. Now the only thing I can think of that would allow this to happen is some of the cloud layers are above the cable layer. Not sure how this could only be on my machine so if you guys could check and let me know, I would be grateful. If it is my machine, anyone know how to fix it? Krazee

The lines that are orange are showing that the 'joystick' default.lua and the 'keyboard' default.lua have entries referencing the same name i.e. 'Radar elevation down' but the line in the default.lua files are mismatched in some way. Often, I find it's due to different 'in-cockpit control' bindings in both default.lua files. I've seen this when a keyboard binding for a press on/press off action and a joystick binding for toggling the same action, uses different commands but the name is the same when referencing the action in game. I found this happened in the Tomcat on release. I also create my own bindings and apply them with OvGME. Sometimes the names I have used have then been used in updates so I have to make them completely original.

Struggling to get speed and altitude modes to engage. When looking at my commands, I notice several of them are duplicated and in orange. For example, 'magnetic brake on/off' start panel is duplicated twice and also 'magnetic brake on/off' main panel is duplicated twice. Seems the default.lua for the keyboard and joystick are using different values, which probably accounts for the duplicates in the command menu. Joystick - default.lua Keyboard - default.lua There are also single values being used for two commands that don't appear to be related. Joystick - default.lua Keyboard - default.lua Is this why things aren't working as should be or is this normal? Am I looking in the wrong place?

Once you zoom the view out to where it's useable, you need to click RAlt + Num0 to save it?

It was an instant start on the ramp. I taxied, took off, flew around a bit and came in to land. I threw the switch for radar but it stayed with a flashing B. Seems to work fine now with exactly the same settings. I'll keep an eye on it to see if it happens again. May be intermittent. Must admit, my controls were screwed from the update. I would flick a switch on my Warthog Hotas and it would jump to a line where nothing was assigned. I reassigned it to the correct keybind but it would still jump to the same line with nothing assigned. I had to clear the assignment I wanted, assign the one I didn't (that it was jumping to), clear it and then reassign the one I wanted again. What a faff! Still, I'm getting there. Onwards and upwards!

Don't know if it's a bug but when I select radar altimeter, it shows baro (flashing B) all the time, even at 500 ft. Was okay before the update, I'm sure. If it's not a bug then can someone tell me what I've done wrong.

I can't select radar altimeter, seems to be stuck in baro. Is it something I'm not doing or is it a bug from today's update? Also noticed they've added all the joysticks and throttles for each module in the main input folders. Not seen that before (pretty sure it was just default.lua in there so if it was done previously then I didn't know). Probably why people are seeing changes in their keybindings? I found some of the Virpil joystick had been pre-programmed with keybindings I don't use so had to remove them. Same with Warthog throttle settings. Had to adjust some analogue settings too.

I have never achieved a zero knot hover. I would love to know how that is possible. My harrier often jumps from 4 knots forward flight to 4 knots reverse. It's even worse with wind. Wind seems to blow the harrier around like it's nothing but a paper tissue plane. Yes rudder pedals control the little air jets that allow the aircraft to rotate on a vertical axis at hover speeds.

Something I found out while flying around in the Hornet. Not sure if it's a characteristic or a fault but either way, it's good to know how to handle it if it happens to you (and I thought it would be an interesting topic). Now, we know that the Hornet (as well as other aircraft) retract the flaps above a certain speed as a kind of fail safe, which is all well and good. However, what if you inadvertently leave the flaps in full and you merge with a bandit, going below around 250 knts will see the flaps start to kick in, right? Now I'm not so knowledgable about basic combat manouevres or energy management so I don't know if this is a useful thing. However, I do know flaps bring some stability at lower speeds, which is useful in landing. But what if you are in the middle of a dog fight and you're at the top of a loop, is it helping to stabilise or is it messing with your energy management? This particular time, I went inverted at the top of a loop and my speed dropped from around 130 knts to around 60knts instantly, a strange behaviour in it's own right. However, the Hornet then behaved like a turtle on it's back, unable to right itself and dropped out of the sky, like a stone. I had no response from the controls so I couldn't roll it or drop the nose to gain speed and even with the engines in full afterburner, the Hornet didn't gain any forward momentum, which again I thought strange. I plummeted to the ground, totally helpless and wondering what had gone wrong. I tried again and found that this action was repeatable. I tested this with flaps retracted and found that I could recover every time, in fact it was impossible to get the Hornet to stay on it's back as it always wanted to go nose down. This is the behaviour I expected. So I tried with the flaps in full until the Hornet behaved like the proverbial 'turtle on it's back' and then when I retracted the flaps, with full afterburner, the speed slowly crept up to about 80 knts then suddenly jumped up to about 160knts and I could recover. I've heard of the falling leaf but this is not that. So, is it a fault or one of those negative characteristic that only appears when you mistakenly leave flaps in full? Be nice to know if you guys can replicate it and what you think.

All was not lost. I did a search for logbook.lua on all my drives and I found my old Mission Editor folder with my logbook still intact... on my desktop. I look at the desktop everyday when the computer starts so how I missed it and further more, how it got there... I have no clue. Still, it made me think about backup so all is good with the DCS World.

I have recently visited my logbook and it appears to have been reset...months of flight logging and data is no longer there. 1000's of hours logged in various aircraft, medals all gone. Even noticed my campaigns have been restarted, set to the beginning. The campaigns I'm not so bothered about. I thought the point of a saved games folder is to save information. I didn't think updates touched that information. When 2.5 was released, everyone was warned that the logbook would be reset and so we were advised to backup the files. But that was because it was a major change. We haven't had a major change like that, since...have we? Oh well. It doesn't bother me too much but it would be nice to know why it was necessary to replace my files. In a recent update, it mentions the logbook will now work with the Yak-52. Was this the update that killed my data? I've also noticed there are a lot more squadrons listed in the logbook, far more than I remember seeing. Mostly under USA but I haven't checked anywhere else. I guess I need to start backing up the saved games folder. Anyone else lost their data or is it something else I've done wrong?

On my HUD, if I set autopilot to BALT and adjust the throttle, the 10 degree line comes into view at 265 knots (266 and it's gone). Being as the S-3 tanker in the 'Instant AAR Mission' is flying at around 350 knts, there is no chance the 10 deg marker can be used. At that speed, I'm sure even the 5 deg marker is only just visible when in a turn. I find using a physical entity, such as the top of the inner or outer HUD glass or even the corner of said glass being a more stable reference. I don't know if IRL there is a set minimum/maximum 'refueling speed' for each aircraft but it is evident you need to be able to refuel at various speeds and HUD symbology might change as a consequence so using the ladder as a reference is not the best idea (maybe as a beginners guide to refueling it would work, start them off with a slow 250 knts KC-130 or something) but a different reference that doesn't change, will be needed for faster tankers.

I am all for serious flying. I'm all for, "If it's gonna get you killed in RL, then don't do it in sim!'. I like to bring my planes home...