eaglecash867
-
Posts
1384 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by eaglecash867
-
-
Its the same way in VR. I really love the amount of extra detail that has been added over the past few months in the Beta, but that whole "deferred shading" thing has taken the overall realism of the colors a few steps in the wrong direction. Also, in the middle of the day, I shouldn't be able to see flashing reflections of wingtip sttrobes on the ground or bouncing off every surface in the cockpit. These things are a couple of the main reasons I elected to not install the latest update to my release version that I have in parallel with the Beta, so I'm not stuck in cartoon land. The performance has gotten a lot better though, and so have the textures of ground objects and terrain. Hopefully they'll continue working on tweaking the colors and lighting as well.
-
Airport charts (not sure if all of them) include an annual rate of change. Those that I've seen are typically like 0.1° per year. AFAIK, sometimes runway designations do change due to magnetic variation, but at that rate that's not a common occurence obviously.
Yup, so a minimum 6 degree change since the runways were marked in DCS, in the amount of time DCS has been in existence, would be an unrealistic amount of change. We're also using a calibrated sighting compass when we do our calibrations, and if we ever saw more than a few degrees off of 350 on our taxi back from the compass rose, we'd know something is still not working the way it should be. :smilewink:
-
I think, basically we're both trying to say the same thing with different words. ;)
Heh...I think you're right. In almost 26 years of doing what I do, and asking pilots "Did you remember to -----?" when I can't duplicate a squawk, I don't think magnetic variation has ever been part of the question. "Did you remember to turn the thing on?", however, has probably been at the top of the list. The runway I mentioned has always been 35, at least for as long as I can remember. :D
-
Thanks for the info, Yurgon. When I take off from runway 31, my AHRS and compass show 299, so the runway designation should be 30. I understand that the magvar may be out of date for when the runways in the sim were marked, but is the magnetic variation in the sim in sync with current data, while the runways are static? Just curious.
Also, one of the ways we know we've done any good with an AHRS, magnetometer, or compass calibration is by using a known reference. We line up straight down the taxi-way, parallel to 35R, and check the cards to make sure they're showing 350 degrees more or less. Subtracting or adding a certain number of degrees from what is displayed has never been outlined in any procedure, and its never been necessary. Something appears to be out of sync on this. ;)
-
Hi bghvp,
I'm just getting into this part of the sim, so I'm not sure where to find the true heading in the mission editor. I'll look for that.
It may be different at Caucases airports, but runway designations, according to FAA regulations, should be within +/- 5 degrees of the magnetic azimuth. With the compass systems and AHRS systems that I work with on a daily basis, I don't think we've ever been concerned with magnetic variation, so having to manually compensate for that doesn't seem right to me for an AHRS. :)
-
Makes perfect sense to me. I've even noticed dramatic increases in VR performance just by shutting down seemingly insignificant items it the system tray, disabling indexing on my DCS drive, and regularly removing spyware.
-
Hi LeCuvier, I tried this again, paying more attention to my needles than the visual, and you're right, this thing is borked. I didn't even have the command bars in view this time, so I'm not sure if what I saw is the cause of what you're seeing, but the actual runway heading of runway 13 at Batumi appears to be 120 degrees (not 130 like it should be). Cross checked with the Whiskey compass. Velocity vector centered, so no cross-wind. So, if you have your HSI course needle set for 130 like you should, you're going to end up to the right of the runway by a long way, so maybe that's why the lateral deviation command bar is to the left when you're flying the heading the runway is supposed to be. Yup. This is a huge bug, and this would get someone dead in IFR conditions in the real world. So, either the runway is mis-marked, or my flux detector needs to be cranked about 10 degrees to the left. Does anybody know if they're working on a fix for this?
Edit: Just tried this in the NTTR map and the runway heading for Nellis appears to be good. Couldn't verify Creech though, didn't even get a backcourse indication on ILS, and I flew straight down 26, needles didn't so much as twitch.
-
It's pretty easy to convert the Beta back to the Stable by using the updater with the corresponding command, so there is not really a need to keep them both installed in parallel.
Thanks for the suggestion, Quigon, but I've got plenty of space on my program files SSD, so its just easier to keep both in parallel.
-
Do you have any MSAA turned on? I have a waviness when I move my head in VR when MSAA is turned on.
-
The Beta looks, runs, and feels great! But, I'm keeping my "Stable" right where it is so if I run across something that's broken in the Beta, I still have an earlier generation of the Release version. No point in locking myself out of my "safe space". :)
-
Yup. You don't want to use the command bars on the ADI to get on the ILS. Use the CDI needle on the HSI to get you onto the localizer. Make sure your course needle is set for the runway heading and keep the CDI needle centered, with the course needle and desired heading at the 12 o'clock position on the HSI. When you intercept the outer lobe of the glideslope, your VDI will appear on the ADI. When you get near the center of your glideslope, you'll see that lateral command bar snap to the center, and it will track with your movement inside the ILS cone. It is a little squirrely compared to the real thing when you're outside the capture parameters, but once you hit the capture point, it locks on and tracks, just like its supposed to.
-
MSAA and Pixel Density help with the readability of the gauges. I'm running both Open Beta and Stable and use the Stable most. In that, I have Pixel Density set at 2.0, and MSAA set for 8X. I also noticed a difference in the clarity of the gauges when I checked the "Force IPD" option and set it for my own IPD of 70mm. I was only able to turn things up that high recently though, and although I'm not sure where the greatest improvement came from, I turned off indexing on my SSD that has my programs like DCS on it, cleaned spyware from my machine, and I close anything in the system tray that gives me an "exit" option. All of that has dramatically boosted performance, with consistent results.
For VR, the video card is the biggest key to good performance, so what you've got in your machine is definitely going to help you squeeze every possible bit of performance and detail out of it. Also, setting shadows to low or off is good for performance. The high setting for shadows is borked anyway and looks terrible. Low shadows actually look fairly decent.
-
You should be able to pick up the localizer in a fairly wide cone from either end of the runway, but if you're approaching from the wrong end, you'll be on the backcourse, so you'll get localizer but no glideslope. I've mostly been practicing the startup procedures, becoming proficient with weapons employment, and then just doing visual landings. Haven't played around with the ILS to see if it works like it should. I'll have to give it a try. From what you're describing, it sounds like its broken.
-
An IPD of 70 looks about right for me, but I based that on the measurement I took between my pupils with my digital calipers. Now if we could just get them to fix your default position in the cockpit in the Beta to be a little more like it is in the Stable, it'll be just about perfect. Not sure if anyone else has seen it, but in the Beta your back and head are against the back of the seat like they should be, but the front of the seat and stick in both the A-10C and the F/A-18C are WAY too far out in front of you. The Stable is just about perfect, except for the fact that you seem to be sitting on the front edge of that incredibly deep seat cushion. The distance to the panel is about right though, you shouldn't have to lean forward and stretch to reach your switches and OSBs on the panel. Imagine having to do that when you're in the real thing, pulling Gs. Heh...fixing the caging knob on the standby AI so it operates like it does in the real world would be a good thing too. It says "pull to cage", not "turn to cage". :D OK...I've strayed off topic a little bit, but 70mm IPD works for me. :thumbup:
-
Hi,
Sometimes under high load I see a number flashing under the altitude digits. Last time it happen to '29.29'. What does it mean?
Cheers
What altitude are you flying at when you see that flashing? Is it at 18,000 feet and above? It could be an annunciation telling you to switch to standard baro of 29.92. Don't know though...just a theory. I'll have to fire up the bug and go test my theory. :pilotfly:
-
The Samsung Odyssey is cheaper and provides much better visuals than the Rift or the Vive Pro.
Microsoft store also offer student/military/educator discounts to drop the price even further. :thumbup:
After using the Rift and Vive...I'd never suggest someone buy one of them. The Odyssey is just hands down a much better HMD every day of the week and twice on Sunday!
The Rift is about $100.00 cheaper than the Odyssey right now, but the Odyssey having better visuals is a good reason for someone who doesn't currently have a VR HMD to consider spending a little more cash than they would for a Rift. For us current Rift users though, I think a lot of us agree that, at this point, we'd rather stay with the Rift and hold out for generation 2, rather than forking over another 500 bucks for generation 1.5. In the mean time, I'm very happy with my Rift CV1.
-
Hey there,
I´ve got a short question concerning Oculus Rift Connection to USB 3.1 only Mainboards just like the Asrock Z370 Extreme 4. This is the one that I purchased (not yet delivered) and now I wonder if the Rift/Sensors will even work on USB 3.1 ports as there are no USB 3.0 or even USB 2.0 Ports anymore. I also googled around a Little and stumbled about some Posts where Users told that it would work with 3.1 only, thus I would like to know if some of you guys have particular experiences with this may be with the Z370 Extreme Board as well.
Thanks
regards
Memphis
When I had a motherboard with built-in USB 3.0 ports, even with a self-powered USB hub, sometimes I had trouble with the HMD going dark, or my HOTAS being intermittent. So, I bought a dedicated USB 3.0 card with 5 ports on it made by Inateck, and those problems went away. I recently got an ASRock Z370 motherboard with 3.1 ports only and moved the Inateck card over to that. It still works perfectly with no dropouts. I know that doesn't quite address your question, but if the 3.1 ports on the mobo don't work, this is a good fallback option for you. The Rift pulls a lot of juice on the USB interface, so its usually best to have it on an independently powered USB port/hub/card anyway.
-
I've never had any success starting it from Oculus Home either. I just start it from the desk top and pull the HMD back down over my eyes. The icon is only there for about another half a second before the main loading screen for the game appears. Not a big deal.
-
Mine have so far, but my missions haven't been very complex up to this point. That may be different if your missions are more advanced than mine are.
-
Yup, I like having to lean, twist, and sometimes grab onto something to see where I need to see. You have to do all that in the real thing. The thing that I see that needs a little work is that its possible to put your head right through the canopy, but other than that VR is the most natural.
-
I wonder if it's because you're using a Rift instead of Vive. Do you get full range while in hangar view too, or is it just in the cockpit?
At least knowing that it works different for you tells me that maybe there is something I could change on my end. Maybe I'll have to try a complete fresh install, although I did one when I built this PC for VR.
Thanks for the feedback.
That might be it. In the hangar view, its the same way. If I can see it, I can click it.
-
Move the task bar to the right vertical and you will never have a mouse problem. You move the bar back for normal windows use.
Thanks for the tip, but Alt-Enter works just fine for me, and I don't have to change where my taskbar is. :)
-
The drawing definitely helped me to understand the problem you're seeing. I was thinking you were having the same kinds of issues I've had a couple of times. That is definitely a weird one. Unfortunately, I don't have any helpful input for that one, other than to say that if its in my field of view, I can click on it. There doesn't appear to be any invisible barrier in my setup. Manipulating that #2 VHF requires me to move the cursor almost to the edge of my field of view, so I'm not seeing the restrictions that you're seeing.
-
Anyone running both Stable and Open beta is 1TB enough for both? Will I have a decent amount of room to spare. This is a 1TB Dedicated DCS World SSD
I run both and I have A-10C, P-51D, AV-8B, F/A-18C, and Flaming Cliffs 3 installed (with F/A-18C only being installed for the Beta of course). The total space used up on my SSD is just under 170GB, so 1TB will be plenty of space for an SSD dedicated to only DCS.
ILS Vertical Bar Error
in Bugs and Problems
Posted
Nope. Not if your runway markings are 10 degrees off from the magnetic azimuth of the runway as they are in DCS. :smilewink:
Headed up to 11,000 feet for about a week in a few minutes...it'll be nice to get out of these triple digit temps for a little while. Have a good one everybody! :D