Jump to content

Stubbies2003

Members
  • Posts

    386
  • Joined

  • Last visited

1 Follower

About Stubbies2003

  • Birthday February 16

Personal Information

  • Flight Simulators
    Falcon BMS 4.34, DCS World with all modules, FSX, XPlane11
  • Interests
    Computer gaming and simulations
  • Occupation
    Retired

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Bummer for you. Both the 18 and the 16 are great 4th gen fighters. Love flying both and employing weapons.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
×
×
  • Create New...