Stubbies2003

Guessing this was the best place to put this one. I already owned The Channel and Normandy 1.0 and the system is pricing it correctly at 9.99 for owning those two but as soon as I go to complete the purchase I get a flashing warning that I already own a license for the Normandy 2.0 map. It is the only thing in the purchase so it cannot be mixing it up with anything else.

Yeah I don't think that issue is a MT specific one as I can see the same scenario develop on the non MT DCS.

Yeah the only other oddity was that when I launched the MT executable moving the headset around did move the view on the monitor just nothing in the headset itself. The other odd bit was the menu was way below my seated position for some reason as if it didn't know where it should have put the menu.

Well this is definitely not a headset specific thing as I am seeing the exact same as the OP but with the Varjo Aero. Monitor displays the game and menu absolutely nothing in the VR headset. Haven't upgraded my video drivers recently but when I do it is always via DDR and completely clean installs. DCS OB works fine sans the MT executable in VR. Also the same in that I am not forcing OpenXR and just using the WMR/SteamVR.

THIS. I get why they decide to not allow miles to be used in the purchase but at least let us accrue miles for the full pre order pricing. Not even allowing miles to accrue is a D punch.

For TrackIR style flying or flying with a middle to low end VR headset you have a point. However with the Varjo Aero there is no such thing as too much GPU atm.

I can also verify this one. Same as what Kang said. Not sure if it is weather related but it isn't anything about what I am doing in the pit as it is just flying at altitude. I've never seen it cause any issues. Almost like a glitch in the F/A-18 matrix so it is the boy who cried wolf for me and I just ignore it. Doesn't always happen.

Would be nice to get a fix for this as it makes trying to use the mouse to click buttons etc. a massive annoyance. You will see two crosses and the hot spot to actually click will be between AND BELOW the middle of the two. I haven't messed around with OpenNXR. Both OpenVR and OpenXR are enabled in my Base. Base and firmware are both current.

So this one was hella weird for me. I tried all of these at the same time. I can't say if the cross eyed worked on Open XR because the viewing angle was so borked in OpenXR that there was no possibility of flying. In OpenXR both the main screen and the select role/brief/etc screens were all down at my feet. I was hoping that jumping into the pit would fix this but nope I was floating well above and slightly ahead of the F-16 cockpit. I exited out and undid the two DLL files and the ini file and used the regular shortcut to nullify the OpenXR mod. Back into Varjo OpenVR the views returned to where they should be but the cross eyed mod hardly changed a thing. Still double crosses with the actual point somewhere in between which made cockpit clicking suck big time. So at least I know that the wonky view at my feet was specifically caused by the OpenXR method and not the others. So next I went and shut off OpenXR in Varjo Base and tested to see if that would use SteamVR since both OpenVR and OpenXR were shut off in Varjo Base. Nope still using Varjo's OpenVR with the 4 view. So I went and used the OpenXR force Steam VR shortcut. This got me off of the craptastic Varjo OpenVR and back to SteamVR which definitely behaved itself better. For some reason this also made the cross eyed fix work perfectly too. Each time I had changed how I was getting into DCS the cross eyed fix window came up and I did the double flip and save and close each time but it was only the last time using SteamVR that it actually worked. Not sure if I even want to mess with it now that it is in a functional state.

So this one was odd. My buddy has a map but he never assigned a home base waypoint. Annoying before hand but I was like don't care now I'll just mark point it and drive home that way. This was the only mark point I had at 26 and had been doing DEAD work via HARM/HTS pod for a few hours. On my last flight a SA-11 got targeted and for some reason I couldn't drop the lock. I tried to go back to Nav mode then to A-G again but that didn't change anything. Neither did going to the weapon page for a HAS shot. Still hard locked to the SA-11 and refused to let go. I started heading back South to home plate but I then noticed that this somehow had also overwritten the mark point at 26 which was now pointing towards the SA-11 and not home plate any more.

Bummer for you. Both the 18 and the 16 are great 4th gen fighters. Love flying both and employing weapons.

I cannot speak for the BDU-50 but you do realize that the BDU-33 is basically a 25 pound chunk of aluminum with a 12 gauge shotgun round not for damaging a target but for marking the hit so you can see where it landed? Any military vehicle with even basic armor isn't going to be bothered much by that even with a direct hit. Jeeps and other completely un-armored vehicles sure it will do some limited damage as a blunt weapon but that is about it.

Fair warning there is no permanent about those lua file changes. Every time DCS patches or you do a DCS repair those files will be overwritten to defaults and have to be modified again or use some of the programs out there to re modify the settings. This is only like for like installs. If you repair live side or live side patches live side will need to be re-modified but if you have beta installed as well it will be fine and vice versa.

It isn't useless in vis mode. I carry 6x 65D all the time. The target jumping was an issue prior to patch but they have been working pretty well since then.

If that was true he wouldn't have denied it. It was his stubborness on the issue. I know what it means and looked it up any ways. What he was doing WAS short hand and denying it doesn't make it less true. Just like you trying to start a flame doesn't prove anything but your bias.

If you are using the term "double ugly" to reference a specific load out instead of spelling out the exact config that would be short hand. Also you shouldn't be assuming that everyone is going to know the definition of Navy short hand in a channel like this. You aren't surrounded by a group of Navy people that you can assume would know these definitions. Short hand second definition: a simplified or makeshift manner or system of communication

Sounds more like common sense. Why would you want to be in autopilot if you are getting ready to AAR?

OK this is strange to me as I was on the 16 in the USAF till 2006 (also as avionics) on block 40s and the UHF/VHF radio had been the same setup for a long time and I hadn't heard of any talk of them changing out the VHF radio for one capable of both. It also seems odd that the USAF would have done this mod only to block 50+ and not to the older birds. Still I was off the 16 at the very beginning of 2006 so that is still the better part of two years that this could have happened without me knowing anything about it.

Well you might want to start by not using some short hand. I don't have a clue as to what a "double ugly" config is. I've never seen the fuel just go to zero on a whim in the hornet though.

I can get all of my stores off prior to needing to refuel so I don't. For me this happens just when climbing through altitude on the caucasus map only. No refuel probe out since I'm travelling to blow stuff up not to AAR.

Not correct for gear and low AoA. Yes for flaps. You don't need to hold the speedbrakes for gear down and low AoA only but they will retract automatically with flaps out of auto or if you have the gear down and you pull high AoA.. I do this all the time in the hornet.

Indeed. The worst one I've seen on the PG map by far is the Jiroft airfield. If you can keep a 16 on the runway at all or from flipping over on you landing there you are winning. I do believe this horrible drift tendency must be nose wheel related as I've started trying to rotate as soon as possible on take offs now as I've noticed as soon as the nose wheel leaves the runway I can drop all rudder input and she is just fine. Sadly on landings this isn't an option. The bases that are the worst like Jiroft I have to go full opposite rudder and sometimes also just the brake on that one side to try and keep it on the paved surface.

Throwing in my two cents as well since the F-16 is horrid compared to the 18 on take off and landings for this tendency to go four wheeling. The worst for me is on landings. I can control it (most of the time) with massive rudder inputs but then when it slows down to the point where the rudder doesn't have enough authority I have to quickly go to center pedals, turn on NWS and get it under control yet again. Even the 18 doesn't do that on landings. Take offs are no fun time either as I can have to put in quite substantial rudder inputs just to try and keep it centerline on take off. Sad to say but on the super rare times where she doesn't try to go four wheeling I feel like I hit the lottery or something.

Well for those who don't use TACAN on the 18 they are already safe there as the sim doesn't turn it on by default on hot starts. However I'm not sure if they model it to that level where they can work off of TACAN and other transmitting systems short of the FCR.

Definitely not the module as I flew the 18 just yesterday with no issues. As Gripes said you'd better triple check your setup. Possibly repair or have to re do the 18 setup file.