Wilcino

You may have already tried this but This DCS World DFR guide says its due to using the standard single-threaded game engine and switching to multi-threaded fixes it....

Hey rurounijones, Its probably a little early to call this a bug. I've not tested this in-depth myself but Zhukov is an experienced guy so I suspect the expected behaviour is that the active runway is determined by wind direction. It may be that its always set to the same direction, or there is a bug with that particular airfield. Can you try to replicate this issue with other wind directions and other airfields? If it seems widespread we can try and get the attention of the DCS team for their take on it.

Thanks ED for giving us a way to feel like we are contributing to the direction of travel and that constructive attempts are being made to gather feedback from the community. Its a long list of options, some of which I didn't even understand in general, or what such a 'feature' would entail once implemented. I appreciate going into more detail would give people more ammunition when things change in the future. This did lead me however to put a low priority on things I didn't understand. As for everyone, the exact thing they want probably wasn't listed explicitly. I certainly value the quality of life upgrades, primarily the ability to set a waypoint seqeunce in multiplayer. This appeared to be under "mark points", or mission data card, so hopefully I've picked the right categories.

In cockpit (where this is designed for) no, you do not need to hold your head. As you move your view in the game the mouse cursor is moved in the opposite direction to leave it in same place in the cockpit. On a menu screen you do need to keep your head still, as point CTRL is expecting things to move but they stay the same. However at this point it is expected you just pick up your normal mouse.

Yeah, no worries, it would be really useful for more fine grained access to certain new features without having to be on the Open Beta branch.

Unfortunately, adding features to 2 separate base versions vastly increases the development effort required. Looking at the F/A-18 updates, it can look on the surface like the updates don't directly relate to what a 'core' game engine is, but they almost certainly do. To ensure they didn't would take a lot of planning from the start, and essentially you'd have to get lucky that the assumptions you made at the start about what is 'core' and what is 'module' turned out to be right years down the line.In your example of the radar, you may at the start think 'I can make it work with these standard parameters', and then find that to simulate some edge case it requires more information, and then you need a core change. Even a trivial change to the core, e.g. to add a field to a 'global' data structure or make something that was global unit-specific, would suddenly touch a lot of different areas of the code. Even if there are changes that don't require updates, you still probably double the testing requirement, you need to test everything on both versions of the game, and also as a developer keep in your head all the knowledge of how things work under the hood for both versions as you develop. I'm a part time developer who supports 2 companies with nominally the same product, and every time I try to implement a feature for 1 company and not the other, and roll out other, common, updates, it turns into a nightmare very quickly. It's frustrating from the outside, and its easy to imagine it can be nice and clean under the hood, but in reality it isnt. Early Access and Beta just brings these compromises to the end user.

I'm not a senior member of these forums, mostly a lurker, so I might not understand the culture and expectations here, but your initial response came across in my reading as passive agressive. In his previous posts, outside of talking about the VR hand controllers, Hog mentions he owns a 5K+ and gives his view on it. In this thread he doesn't give any personal opinions or representations of Pimax products. He links to a youtube video and it is clear that the video's creator is a separate person (or maybe Hog is a ghost account for Sweviver). Even if he was a promoter for Pimax I don't see anything in his opening post that would required him to advertise that fact. The link posted is relevant to the forum. Good discussion is helped by people disclosing affliations to products/companies they reference, but being too suspicious will put off new people contributing. I'm not saying that Hog's response was overly constructive either...

As mentioned by lunaticfringe, a non-vr solution (though still requiring spending money) is Track IR. There are open alternatives (I switched to Track IR as I had issues with these). This will allow you to move your head around laterally to look around the cockpit frame. You still use your monitor, but do have to mount to a cap, or buy a separate clip for a headset.

Playing in VR with the F-18C, (Pimax Headset, GTX 2080Ti) I get a pure black cross as a mouse cursor when I'm not over a clickable control. When over a control it goes green and shows an icon (e.g. to rotate or move a switch up/down). However when not over a control in a dark cockpit it can be very hard to find the mouse and direct it onto a control. A video showing the mouse cursor, and a track file of that mission (just a short startup), is available at https://drive.google.com/open?id=1VBFCf9vwtgheNmzEhxYF6uPtwvZzaYzY Some mouse cursor issues have been related to scaling in windows desktop options. Although I have a 4K screen its massive so the scaling is at 100%. :helpsmilie: black mouse cursor.trk Black Mouse Cursor Issue.zip

Thanks for working out how to fix! If people need a copy of 'fixed' Hornet of PG files (date set to 2003 and USN deck crew removed) I've posted my updated versions https://drive.google.com/open?id=1uM79ebzuFBa50I9-un14RvkjwhBS7eMA

You can re-center the VR headset view whilst flying. From the main screen, go to settings (Gear icon) > Controls. In the top left select "UI Layer". In the list of controls is VR re-center (or similar name). Click on this under the keyboard column. Bind this to a key and click accept. Pressing this key whilst flying will move your "current head" position in the game back to the nominal head position. As in other games put your head in the "right" position for you then hit the button. You can use the hand controllers, but I don't, I use the cross hairs and mouse. I do find it hard to see the mouse sometimes, I had a rendering issue where it goes black, so very hard to spot! In the input/output forum user MilesD has developed a finger-mounted pointing system. I have signed up but haven't tried it yet, but this looks like it could be a good method for interaction. Be warned this is not a commercial product. Regarding FPS, I use a different headset (Pimax), but the fps counter works for me. For my headset there is a smoothing function that locks the frame rate to a certain level (e.g. 40hz) and interpolates to generate an 80hz update rate. I don't know if the Rift S works in the same way?

Hi Miles / FireCat. I would like to be added to the list if possible. Good luck with the launch, It sounds like you've done a great deal of development work to get to this point, I'm sure it will pay off.

You're in the mission editor discussion here. AFAIK you can't control basket deploy / stowing from the mission editor, this is done when a player or aircraft approaches the tanker to refuel and establishes communications using the F12 menu. If you're asking how to do it whilst flying a plane to a tanker, see below: The basket extends once you make the call "Ready Pre-contact", and are in a good enough position for the tanker to accept. Tanker communication is accessed by pressing F12 (comms menu) -> F5 (Tanker) -> (Might need to select which tanker here) When initially flying to the tanker, you make a first "Inbound" call. The tanker will respond with heading and altitude information, to help you line up behind it. Once you have made this call the comms menu will offer you "Ready Pre-contact". You need to be close in behind the tanker and below, only 20-30m or so from where the basket will end up being. If you are in an acceptable position the tanker will respond "Ready pre-contact" and extend the basket/boom. If you are not in a good enough position the tanker will respond "return pre-contact". Once you have made the "Ready pre-contact" call, the basket will extend and you don't need to make another comms call, unless you move out of the acceptable area, at which point the tanker will call "Return pre-contact". Get yourself lined up behind the carrier and then make another "Ready Pre-contact" comms call.

I believe (but can't link to a source) that they are hoping to offer key bindings for the jester commands, to provide some way to integrate with VoiceAttack. Presumably this API could be customised to work with Streamdeck and other IO controllers, but I don't know what would be required, or even if such functionality will be available at launch/ever.

What is active pause actually meant to do? I always thought it was "Pause the world, but allow me to interact with my aircraft systems"? But apparently it isn't that.