Jump to content

Cal.Iber

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by Cal.Iber

  1. I had this happen to me (1080ti, Index) but only when I had MSAA enabled - F-14 on the deck of the Supercarrier when I would turn my head towards any objects, primarily with the tower but also with smoke/steam trails of launching aircraft. I tried changing the new mask size parameter and no difference.

     

     

    I wasn't experiencing whole eye blackouts, but rather large black rectangles about the size of aircraft.

     

     

     

    I disabled MSAA and no longer had the problem.

     

     

    My buddy reported he was also getting black rectangles at one point briefly while using a Odyssey+. AFAIK it was only brief for him.

  2. Is there a workaround for AIRIO navigation points on multiplayer servers with map markers already placed?

     

     

    I created a map marker but was unable to get Jester to enter it. Hollywood mentioned a revamp in the most recent update but I'm not aware of what if anything has changed.

     

     

    Also, is there a way to et Jester to tune radio channels (presets) instead of static frequencies?

  3. SLAM-ER.

     

     

    i will conspire to get it banned, by getting a few people together and deleting bases from standoff distances online.

     

     

    but seriously, probably ATFLIR/DLINK/HARM. unfortunately we are going to have the BMS problem (henceforth known as the DCS/BMS problem) in that the SAMs are going to be too dumb and HARM is going to be rod from god effective in wasting everything, with a standoff distance that will be impossible to beat.

     

     

    without banning 1/2 of the weapons available on the future hornet, it's going to absolutely destroy multiplayer. hornet will be the most capable thing in the game by literal miles, at every role and in every situation.

     

    Multiplayer will evolve, like it has with every module that has come before it.

     

    The poll as it stands almost perfectly reflects my own personal Hornet priorities. HARM, ATFLIR, A2G Radar, AA Radar, JHMCS (in that order).

  4. Hi, I have e-mailed them for a price.. Thank you !. :)

     

    Are you happy with the Odyssey for DCS?. I'm using a DK2 and while it's a great experience it does tend to leave my eyes feeling a bit heavy after use - which I think may be more the low resolution than the actual headset.

     

    Ouch. I don't remember my experience with my DK2 and DCS but I do remember going from DK2 to CV1 in Elite Dangerous. There was a big difference in the ability to read text.

     

    I exclusively use my Odyssey with DCS now. The only thing I don't care for is that if there's some lag the visuals stop and drop to the SteamVR space temporarily. It's a bit jarring but seems like it hasn't happened much recently. I wish it behaved a bit more like the CV1 in that regard, but I agree with OP that the visuals are much better in the Odyssey.

  5. First off, I want to express my thanks for DCS and the incredible modules Eagle Dynamics and its partners have provided. This is a niche market of very demanding players and I'm super thrilled to have a sim of this quality with support for a constantly evolving list of new planes, new features, and a huge thanks for VR support.

     

    I've started playing Multiplayer more and more lately, largely due to the (somewhat) recent availability of both Hoggit's Georgia at War and Through The Inferno. My reasoning is simple: These are the types of missions that appeal to me, namely larger scale PvE. As someone who's primarily interested in A2G with friends, this is an excellent format.

     

    I get a 60ms ping to TTI and 170ms to GAW. I have roughly the same issues with either server ... I get disconnected (crash? not sure) back to the Main Menu, only to need to login and go through the process of starting up, reloading ordinance, taxiing, and flying to target. Last week while playing on TTI I had this happen 4 times in a row before takeoff.

     

    The experience can be quite disheartening.

     

    As best I can tell it often seems to be the MP server process itself crashing. Most(?) of the time the mission timer has reset for TTI which as far as I can tell means the server restarted. I've hung out in the Hoggit discord channels enough to know the server stability problems they've been having.

     

    I know first-hand that these problems are challenging to find and fix. I have a feeling many of us in the community would love to help if we only knew of a productive way to do so. If there is something we can do to gather data, provide access, or otherwise help, please let us know.

  6. The TrackIR system is only tracking Infrared light (and afaik has an IR filter) so general ambient lighting shouldn't be an issue. Its certainly possible that the projector potentially _could_ put out a bunch of infrared light but probably doesn't.

     

    If it becomes an issue, I'd pick up something like a TrackHat that will directly output IR tracking lights that should be brighter than any ambient noise.

  7. Okay Guys, jumping back in here. I solve my AI Suite problem and have overclocked CPU to 4.2 Ghz. I installed a Samsung 850 EVO SSD SATA 3 and moved entire DCS installation over to it. Honestly, it is not much better. GRRRRR!

     

    I have an Odyssey and its currently exhibiting major issues with DCS that I can recreate simply by starting up the NTTR Viggen Cold and Dark mission and proceeding through startup. About the time the radar comes up the system is almost unusable and then proceeds to hang / crash.

     

    I'm fortunate to also have a Rift which works fine with the same settings. After a couple attempts I managed to submit feedback in the Microsoft Feedback Hub with a capture that will hopefully lead to some improvements. If you're interested, feel free to upvote that post (titled "SteamVR Judder and poor performance in DCS World") so hopefully we get some developer attention looking at DCS.

  8. I use them in both the A10C and the Harrier.

     

    They're useable but not ideal. I usually grab the inside portion to give my fingers some sort of reference position and then fumble around for the buttons.

     

    That said, I think I often hit the wrong button about 35% of the time. It hasn't caused any real problems yet, but if I'm in a hurry I often grab the mouse to click in-game for the sake of accuracy.

  9. To be fair though the Odyssey is an ordinary VR headset as I understand it. Several reviewers have remarked that the ”mixed reality” label is kind of misleading in this case.

     

    Misleading because at launch it will be VR only; the difference however is that all the hardware components are there to be able to support mixed reality _eventually_ but most likely aren't ready.

     

    As the Tested video points out, AR becomes VR with a black screen, and VR can become AR with a camera in passthrough. Theoretically all the MR headsets should be able to support both if the software can selectively integrate objects in your environment (which it already is doing to be able to support its positional tracking).

     

    That said, ultimately in the VR/AR/MR arena software is king. This includes both the third party app catalog (most of us here want to at least play DCS and if a headset doesn't do that, isn't nearly as important to us) as well as the supporting features (Asynchronous Time/Space Warp). All the hardware specifications in the world are meaningless unless at the end of the day they have the capability to run software we want to run at a performance level that's acceptable without making us sick. Right now, only Rift and Vive are known quantities.

     

    There's a lot of potential here but the software side will have to be fleshed out before it becomes compelling. Microsoft has a track record of chasing after walled gardens and then abandoning its own efforts because consumers didn't find a reason to buy into their platform.

  10. That is a little odd, whilst my mouse when using the button assigned as mouse in UI layer would not have focus initially, I never had a problem with my joystick not being active in the cockpit.

     

    That's what I was saying regarding my deaths in campaign. If you click outside of the DCS window while in VR (I've got simshaker running, usually one or two other Windows) then I lose all HOTAS functionality. Not a good thing to happen when you're flying low through valleys.

     

    The VR view stays active, so you still get to panic while you realize you're not banking when you intend to. :joystick:

  11. Ok so, in VR mode, you most likely have a button setup on your hotas for the mouse button. That way you are completely hands-on all the time even when you need to manipulate cockpit switch and what not. You just have to point the little dot on the center of vision and activate switches with the joystick button mapped as left mouse click.

     

    So it works also in the main screen, to manipulate menus.

     

    My problem is that right after the briefing loads, this doesn't work anymore, I can't click the Fly button that way because it seems that the game "window" is out of input focus. I have click with the actual mouse button to bring it back in focus, then it works as expected.

     

    Same thing happens after the loading screen, I can't click resume with only my head and joystick button. I have to bring it back in focus, then it's working fine.

     

    I have the same problem in alt-tab mode.

     

    I also don't have this problem in 1.5 :(

     

    You guys don't experience the same problem ?

     

    I have the same problem. The button on my HOTAS for mouse doesn't work after mission load.

     

    Currently during mission start, the simulation window doesn't seem to have focus (be the active window in Windows) which means DCS isn't processing inputs for your HOTAS controller.

     

    There isn't really any solution other than using alt-enter as DBurne recommended. Its an annoyance that hopefully ED gets around to fixing at some point. Its been responsible for at least a couple deaths in Campaigns due to crashing into terrain while flying low and trying to keep terrain masked.

     

    On a side note, if any testers or people with ED's ear are looking over this thread ... perhaps consider requesting that the "Full Screen" checkbox in the settings menu still be respected for VR users?

  12. I went from a 980 to a 1080ti. being able to bump up the pd and some extra smoothness was nice. I would say that for DCS the cpu (particularly clock) is still the main factor. I think the age and evolution of DCS will always keep it a struggle though. That said, running native VR games I can run pd 2 and max out settings and that is sweet. Even some titles that have added VR after but done it well can be run max or near max, if the implementation was done well. Dirt Rally, PCars and BOS maxed are sweet. Since I only play games in VR now, the cost was worth it for me.

     

    I think this echoes my experience. I went from a 1070(FE) to a 1080ti (FE). While it was a bit smoother it wasn't lifechanging. This may be one of those situations where a CPU upgrade (focusing on high Turbo Boost; DCS is still mostly single-threaded) may have a bigger impact.

  13. Also as I understand Oculus does now support audio mirroring, for playing sound in both, but I have not checked it out to try it so not sure how to go about using it.

     

    Edit - did some searching sounds like you just at Oculus Home (desktop), go to Settings, Devices, click the Headset and select "Both (audio mirroring)" in Audio Output.

     

    Unfortunately Audio Mirroring with the Rift only works if you're launching apps using Oculus Home, and since DCS doesn't have a Native Oculus Store App, this isn't an option.

     

    I've used VoiceMeeter Banana to accomplish this in the past so that I could output sound to a Bass Shaker and it works ok.

  14. I ran some tests last night flying around Normandy with a couple different settings and I found that I could have acceptable framerates with MSAA on (4x) as long as pixel density was set to 1.0 (or vice-versa)

     

    My (arguably very simplified) understanding with regards to pixel density is that its essentially brute-force rendering at a higher resolution (1.5 x 2160x1200 == 3240x1800, essentially the same as FSAA/SSAA) and then downsampling on the device, so I imagine adding MSAA to that is probably more than most modern video cards can handle well.

     

    It seems strange in theory to try to run two separate anti-aliasing methods simultaneously (PD + MSAA). I only have a rudimentary understanding here though, so hopefully someone smarter than me can chime in and correct me if I'm misunderstanding.

×
×
  • Create New...