Jump to content

eaglecash867

Members
  • Posts

    1384
  • Joined

  • Last visited

Posts posted by eaglecash867

  1. I have indeed, and usually always run in fullscreen. Doesn't matter if I have the mouse confined to game window enable or not either.

     

    Let me describe in further detail. When you are on the hangar screen, the game cursor is confined to the gui window(mission, settings, modules, etc.). No matter how much you move the mouse, the game cursor is bound within that window, regardless of the above settings I mentioned. I always use the confined to game window setting, because otherwise it is possible to accidentally click on an icon on the taskbar.

     

    Now as well, when flying, the cursor(blue cross) is still confined to that same area, although it is invisible. You can see that area if you call up the pause screen. It is the same area as the gui window in the hangar.

     

    I don't know if there is a way to get the cursor to reach outside this "box" and go from screen edge to edge. Otherwise, in order to reach a control in the cockpit, it must be within the area of this box.

     

    Hope that makes sense.

     

    You definitely should have that "confine mouse cursor to game window" checked, but as I've found a couple of times, it still manages to jump outside the window and I end up inadvertently clicking on something in Windows. So, as you're moving your head in VR, and look down to say, arm the ejection seat, your pointer turns green, but when you click, nothing happens. Then you take the headset off to look at your screen and all is normal, except for when you say "Oh, oops, I forgot to use Alt-Enter to expand the VR window across the whole screen" and hit Alt-Enter, then some Windows settings menu keeps popping up. Its only after you click somewhere near center view in VR that mouse control returns to the game, and now you can hit Alt-Enter. For me, having the VR Window completely expanded makes it so its not possible for the cursor to click outside the game. Even with "confine to game window" enabled, it will still jump outside it sometimes just long enough to take the focus of the mouse click out of the game.

  2. I've gotten things even further optimized on my system, so now I'm at 2.0 PD and 8X MSAA on the Stable and it runs smooth as glass in VR. I can easily read every gauge, as well as the HUD. I ended up doing all the old stuff that I didn't think applied anymore. I shut off indexing on the SSD that I have DCS on, went back to regularly running spyware checks, and I closed every unneeded item sitting in the tray. Not sure what the biggest contributor was to the performance increase, but prior to doing all of that I was lucky to run 2X MSAA with 2.0 PD without getting visible stutters. The combination of all of those things has breathed new life into this sim. Now I can concentrate on the fight, instead of the graphics glitches.

  3. I've had a set of Saitek pedals for at least 8 years now. No problems here at all.

     

    I'll add my vote for the HOTAS Warthog for the stick and throttle. Solid construction, and the DCS A-10C manual is geared toward it, so its the easiest to integrate.

  4. Yeah, I never got the "if you see it, you can defeat it" until I tried to dodge a SAM launch in VR. Really cool.

     

    I knew that it worked, and I knew why, but hadn't been able to actually do it in a sim until VR came along. MUCH easier to keep it at right angles to you and force it to overshoot or run out of energy.

  5. Wow, are you using a Pimax 4K? That may explain it. The 1 to 1 tracking is such a departure from TrackIR. There's really no need to explain the difference.

     

    Yup, its that 1 to 1 tracking that makes it more natural to not only spot a missile launch, but to instantly know how to maneuver to have the best chance of defeating the missile.

  6.  

    I pretty much fly the A10-C exclusively and one of my biggest pet peeves is trying to get to controls on either side of the seat. Temporarily repositioning my head helps with startup, but for some reason when looking down to the left/right, I can see the switch I want to interact with, but the mouse cursor seems to hit an invisible edge, preventing me from reaching it. That edge is about a 1/3 of the way up from the bottom of the visible area. I'm guessing the cursor is hitting the bottom of the monitor window. Fullscreen or not, doesn't seem to make a difference. If the mouse cursor could reach the entire viewing area, then it wouldn't be a problem. I just can't physically tilt my head down enough to get the cursor on target. I have to physically move my chair.

     

     

    Have you tried Alt-Enter? That will stretch the VR view window across the whole monitor so your mouse cursor isn't getting trapped at the edges.

  7. After briefly running at 1.5 PD and 8X MSAA on the Stable version, I've gone back to 2.0 PD and no MSAA. Some things outside have little, barely noticeable jaggies on them, but at 2.0 PD, everything in the cockpit is crisp and clear. I have to agree with the posters above me. The only part of that video that shows how much "better" the Odyssey is than the Vive (similar resolution to the Rift CV1) is a side-by-side comparison with the Odyssey zoomed in MUCH further than the Vive. Of course that's going to give the illusion that one is vastly superior to the other! Aside from that, the rest of the video is pure blurriness from both headsets. My CV1 works just fine. I'll wait for a significant increase in resolution before I plunk down more cash.

  8. Yep, F-16 Flight Control System, F-18 Avionics, B-52 Guidance System.

     

     

     

    From the documentaries I have watched the major thing that was classified was the shape. Did you know one of the nicknames was the "Cockroach?" How bout that!!!!

     

    Yup. They also called it the "Stinkbug".

  9. No problem at all with naming your own install location. Just make sure to give the Beta a different location to install files than where you installed the Stable and you'll be fine. I have both installed on my D drive, which is my 2TB SSD for programs only. I have them installed in my D:\Games\Eagle Dynamics folder. I just kept the suggested folder name, but changed where I wanted it installed. Both versions run independently of each other, with no issues (other than the issues inherent to each version). :D

  10. Just install them both if you have the space on your machine. They run independently of each other, so you don't have to wait to try out some of the new stuff, and you won't have to worry about breaking what you're already happy with.

  11. Yeah that may be a little high on PD.

     

    I am running 1.5 currently.

     

    I have it set at 1.5 now with 2X MSAA which looks and runs great. 4X MSAA is much better, but still not perfectly smooth. 8X MSAA in the Stable version, with PD set at 1.5, on the other hand, looks and runs amazingly! Thanks for the tip, Dburne! It hadn't occurred to me that MSAA would make 1.5 PD look just as good, if not better than 2.0 PD with no MSAA.

     

    Thick8, I'll try a lower gamma and see what happens. Thanks! :D

  12. Hi folks,

     

    I still haven't downloaded the open beta, hence, I cannot enjoy the F/A 18 like most of you. How long does it normally take ED to release planes or maps on the stable/ normal DCS after they have been released on the early access? A week? A month? A year?

     

    Greetings to you all

     

    You can download and install the Open Beta just like you did with the Stable. The 2 of them run independently now, so you don't have to worry about the Open Beta messing with your Stable install. That way you can enjoy the F/A-18C without having to wait until they have the Beta far enough along to offer an update to the Stable. If you're fine with having both versions on your machine at the same time, you won't have to do any command line editing. You also don't have to worry about using an extra activation for your modules.

  13. That is odd I am running 2x MSAA without any issue, very smooth for me. I can even run 4x MSAA without a problem, I prefer 2x due to a little better performance. Your rig is certainly beefier than mine also.

     

    What pixel density are you running, Dburne? I'm running 2.0 on mine. Maybe that's why I'm having issues, or maybe I've got something else going on with my machine. Its a new build, so there's definitely a possibility I haven't squashed all the bugs yet. The jitters I'm seeing look like the image is separating between the left and right eye, so it jumps back and forth. Turning the MSAA off makes that go away.

  14. I've noticed an improvement in the appearance and frame rates with the latest incarnation of the beta. SSAA doesn't appear to do anything, which would be consistent with what others have said about it not being intended for VR. MSAA, on the other hand? Still broken. Even 2X makes everything a jitter-fest, like one eye is lagging the other. With that turned completely off though, things run pretty smoothly. Definitely don't like the affects of the deferred shading being locked on. I'm trying to get deeper into the more advance functions of the CDU in the A-10C, and now the keys are so washed out I can't read them. So, I'll be back on the stable with the A-10C and use the beta for the new modules.

  15. I've only gotten an occasional woozy feeling if I'm craning my neck to see around the windscreen frame and HUD on the A-10C. Other than that, no problems here. Heh, I go out and purposely stall aircraft while calibrating aftermarket AOA sensors on a fairly regular basis though, so knowing to look at a fixed point in space and avoid side-to-side craning of my neck while going into the stall to avoid getting sick is just something I've gotten accustomed to. The Rift has excellent head tracking, so where you look in the sim is where your brain thinks things should be, so spatial disorientation is pretty minimal. Definitely keep your head still while you have the loading screen up though. That doesn't move with head tracking, and it can definitely mess with you.

  16. Yup. Just download and install fresh versions of the Beta and the Stable and it'll all work, right out of the gate. You can get HOTAS configs from your Saved Games folder and load those back in after the installs are done. Just make sure you either use the default location for each version, or make sure you don't install both in the same base "DCSWorldxxx" folder. They can peacefully coexist without one messing with the other, and you only have to use one activation for each of your modules. :D

  17. I have mine set at 512 (not 512 every frame). I can't really visually see a significant difference between that and higher settings in VR. Higher settings, at one time, did affect frame rates pretty badly when the TGP is turned on in the A-10C. I think that has been fixed at this point, but I've never seen a reason to go back to a higher setting than 512.

  18. "Stable" versions of software have always been found to have bugs in them. Then updates/patches are released. Some of which fix the problem, and some which create more problems than they solve. The approach that ED is using here is to make their continued development of the sim available to everybody, instead of a select few on a testers team. That way, the sim is run on a more diverse array of hardware, by a more diverse selection of technical skills among users. Bugs get squashed quicker that way, and its a reasonable alternative to hosting multiple versions on their web-site so you can backload if a new beta does something you don't like. I haven't seen a sim yet that was perfect the day it was released to the public. Just run both versions alongside each other and you can decide which one works best for you at that particular time. They've made it much easier to do this than it has been in the past.

  19. You need to realize that not everyone wants two instances of a 100Gb program on their SSD...

     

    This is the only reason why people opt for the Command Prompt method.

     

    :lol: Kinda funny that you stated that with so much confidence, as if nobody here thought this through hahaha! :lol:

     

    (don't get me wrong, I'm not making fun of you, but laughing of the situation)

     

    Actually, I'm speaking from the standpoint of being one of the guys who thought it wasn't possible to run both versions on the same machine without them conflicting with each other. I got that way because that is how it used to be with this sim. I tried what I tried based on a "What the hell...you wanna live forever?", so I'm just sharing information. In my job in the aviation world, its not uncommon to see things being made more difficult than they have to be based on outdated information. If people are doing it for the reasons you say they are, then I'm sure they'll be able to figure that one out on their own, right? :smilewink:

  20. All of the references to editing with the command line stuff are completely unnecessary. Just install both versions and make sure they don't get installed in the same, base "DCSWorld***" folder and you're good to go. Compatible modules can then be easily installed and activated on both, without burning 2 activations. There's no need to make this more complicated than it is by messing with the command line editing. :D

×
×
  • Create New...