eaglecash867
-
Posts
1384 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by eaglecash867
-
-
That would be useful and appreciated
Send me a PM with your e-mail address in it and I'll get that over to you.
-
Greyman, maybe the best way to make sure we're on the same page is if I send you my SnapViews.lua file. That should put you in exactly the same position in the cockpit as where I have mine set. My PID is set at 70, but like you said, that doesn't really have much effect on how much of the HUD info you can see.
-
Yup. I can see the whole thing, top to bottom. The headrest appears to be about where it should be. The default view position actually seems to have the back of your head slightly buried in the headrest.
Its been quite a few years since I sat in an A-10A, but even as a 16 year old kid, I remember feeling like the cockpit was awfully cramped. I remember hoping I wouldn't get too much taller so I could eventually fly one.
Not that its the same jet, but I was recently in the cockpit of an L-39, and getting to some of the switches in the side consoles required a lot of twisting, and I would actually find myself reaching across with my opposite arm to operate some of them. The stick was pretty much right in your lap, with the instrument panel being really close to you as well.
-
That's weird. When I have my view position set to see the whole HUD, the VR stick is pretty much right where my actual stick is, about a foot from my chest. I just have to make a couple of adjustments to the shelf I have my throttle mounted to. Its a little too low and a little too far forward.
-
It feels about right to me, except for the side consoles like you mentioned. Not sure if that's because your position in the cockpit isn't right though. In the real thing, we'd be operating a lot of things mostly by touch. When we had to look at something, such as tuning a radio, we would be able to use our eye movement much more than what is possible in a VR HMD. I think if they made it so you could adjust the HUD glass, that would fix a lot of problems people are having.
-
+1 to the posts that say you're sitting too far back.
Check out my post in this thread to get your default view position adjusted and permanently saved.
-
And you felt the need to point that out, thereby adding to the thread. LOL :lol:
-
This has been a problem in Xplane 11 for ages, to fix it you need to open up the Oculus Debug Tool, launch DCS, then in the Oculus Debug Tool you need to force disable ASW, and then Force enable it, switch back to DCS and all should be well.
This was a problem with the last major update to the DCS Beta, and its been fixed already in DCS. No need to go tilting at windmills. ;)
-
To be fair, the search function on this forum software isn't exactly precise. That being said, its not like the search function was even needed, because there were no less than 2 topics about this on the VR board, and they were right at the top. People like us take the time to make sure we're giving accurate information, post our solutions, and then the thread ends without even so much as a "Thanks! That fixed it!". Now I know what Google would feel like if it were human. :)
-
Move View Left: Rshift+Rctrl+Num4
Move View Right: Rshift+Rctrl+Num6
Move View Up: Rshift+Rctrl+Num8
Move View Down: Rshift+Rctrl+Num2
Move View Backward Rshift+Rctrl+Num/
Move View Forward: Rshift+Rctrl+Num*
Save Position: Ralt+Num0
After you get your position set and saved, it should return to that position each time you start DCS. Just remember to pull your HMD over you eyes and sit where you will be flying when you start DCS. When you hit the Save Position keys, it will save a SnapView.lua file in the Saved Games/DCS/Config/View folder. You can save a copy of that some place safe and just paste it back into that same folder if something gets hosed with DCS and you have to reinstall it. Works like a champ. I'm finally sitting where I should be in the cockpit, with the HUD readable from top to bottom and it returns to that exact position every time I start DCS. :D
-
I have the CV1, which is going for about $400.00 these days, and the thing just works with no fuss. Not sure if its been mentioned yet, but the DK part of DK2 is Developer's Kit, which usually implies the need for a lot of extraordinary technical ability in order to get it working reliably. I definitely recommend the CV1 at this point, since true second generation VR is probably a year or two out. I've tried the Samsung Odyssey already and returned it. In my opinion, its too light and feels kinda cheap. Also, its interface was clunky for me. Can't go wrong with a CV1. :)
-
Just curious, can you jettison external fuel tanks, have it explode and lure an IR missile away?
Only if you're flying an F-18F and that missile has been chasing you for more than 3 minutes. :D
-
Depends on region. According to NOAA, Las Vegas declination changes +0°6' every year. Batumi -0°5' every year.
Pretty much what I said, just different terms. 6 minutes is roughly 0.1 degrees. Regardless of the direction of change, that's still an average of 0.1 degrees of change. ;)
-
Magnetic variation changes an average of roughly 0.1 degrees per year in real life, and in DCS its not really modeled correctly anyway.
-
Any fix for the peripheral black borders not being rendered when turning your head quickly? It's really annoying...
Another fix for this is to install the DCS "stable" version on your machine in parallel with the beta. It saves a lot of monkeying around with things as long as you have the drive space for it.
-
Frederf, I hadn’t thought of using an EGI derived height, that could be interesting. My memory is that pre-WAAS GPS did a poor job of determining height/altitude but I admittedly don’t have any idea how the A10 handled it or perhaps more importantly how DCS models it, but I think it is worth exploring.
Tom, I missed this post before. That's similar to what I do when I'm going to recertify an air data computer that can be calibrated in the field. Before I even connect any equipment to the aircraft, I use an altimeter app on my phone to get GPS altitude at that particular location, and then I call AWOS (which isn't available where I am anymore) or listen to ATIS to get my baro setting. If I dial that baro setting into the ADC and its more than 20 feet off from the GPS altitude, I usually just run through the calibration procedure prior to running everything in the aircraft. It takes out an extra step that ends up being just wasted time if the ADC is out of cal. To get to my point though, I still need current baro from ATIS to do the check. If they gave QFE like DCS does, it wouldn't do me much good. I'd definitely trust your rule of thumb method for figuring that out over just setting the ADC to match the GPS altitude. If you use rule of thumb and your instruments are way off of what they should be, you've got issues with your air data system. Heh, I'm sure DCS doesn't model things like an aircraft that got washed or rained on and got water in the static system, out of cal ADCs, or a bug in the pitot tube though.
I know you know all this stuff already, just wanted to throw out to the community the dangers of setting air data systems to make them match your EGI derived height, or based on the known field elevation of the airport. We both know that wouldn't be a valid method in real life. :D
Got the L-39ZA done today. I know more about that aircraft now than I ever wanted to know. Not particularly difficult to work on, its a really well-built aircraft. Just had to do a lot of exploratory surgery to get the new RG-142 cables run for the WAAS and transponder antennas.
-
Just write down all the weights from the loadout screen for the aircraft, and then do the math based on the ordnance/external stores and fuel remaining as you're flying. That should get you close enough. I'm not familiar with the mission, so I don't know why you end up landing on one engine, but that sounds like maybe an emergency situation (battle damage?) where it might be a good idea to punch off your external stores.
-
No OTT here either.
-
I didn't have the Core 2.0 Beta installed and had the drunk pilot problem with the latest DCS beta update. I enabled Core 2.0 Beta last night, and still have the drunk pilot problem. The current build of the release version of DCS works great both ways. Definitely the new beta causing problems for us Rift users.
-
Why have both? For times like now, when the beta is jacked up for certain users like us VR people. Can't fly multiplayer in VR on the beta right now.
I'm a VR Oculus Rift user and the beta is completely hosed for me as well. I was running the stable exclusively when it was released, but then I decided to install the beta as well. Definitely wanted to keep the stable, since we had the Great Building Vanishing of 2017 happen once. I guess us VR guys with the Rift can call this one the Drunk Pilot Simulator of 2018. Good thing I have the stable to fall back on. :D
-
Yeah kudos to the team for at least trying to get something out over the weekend.
I am grabbing it now - I have not had these issues so hopefully that will still be the case for me after this hotfix2. Will know soon.
Edit: Just checked the posted changelog, it really doesn't say anything about the VR issues in this hotfix2.
Don, should the latest hotfix be trying to download and install when I start DCS like usual? Mine doesn't seem to be doing that.
-
Yup, Zarma, did that too. While testing the latest beta to see if I had the same problems as everyone else, I even ended up screwing something up so badly that I had to completely remove the 2.5.3 beta and do a fresh install from the DCS download page. Even with a fresh install and clear fxo and metashader2 folders I still have the issue. I also noticed that the first time I tried running the updated beta, before the reinstall, SteamVR was somehow getting triggered to start up. I haven't used SteamVR in months because I currently don't run anything in it. But, for some reason, when I'd start DCS, it would try to load. I have since removed SteamVR altogether, and still have the feeling of being drunk in the cockpit. GUI and mission planners seem to be fine, its just when you enter the cockpit that things go screwy.
-
As I said, the shaders mod requires some extra steps to enable/disable. All described in the readme.
If you don’t disable the mod, you’ll have some redundant folders at best, e.g. your renamed folders during the mod install, and replacements for them during the DCS update.
What you said was we can’t be sure that ‘removing a mod is getting all of it’. I’m saying yes you can, and OvGME is a great tool that ensures that any files you changed are replaced with the originals when you disable the mods.
Just because you don’t see any problems by not disabling mods before an update, doesn’t necessarily mean it’s the right thing to do. By ensuring you disable all mods before any DCS update is good practice, and ensures you have a clean install to update.
So, semantics aside, are you having the same problems with blurriness in the Beta as most of us, or aren't you? :music_whistling:
-
OK, well, I guess that rules that out. Thanks Don.
[NO BUG-SEAT POSITION] HUD display too large after update
in DCS: A-10C Warthog
Posted
No problem, Greyman. The changes ED made did correct the problem of being way too close to the panel, but they ended up putting you too far back. If I sat down in an aircraft and the panel, stick, and rudder pedals were at the limits of my reach like they are in the default position in DCS, I wouldn't taxi the plane, let alone try to fly it. It really does come down to two camps though, just like you were saying earlier. If they made it so we could adjust the calibration on the HUD, I think that would make everybody happy. :)