npole

The game is nowhere optimized for VR... neither if you own a 1080 and set everything to low. Of course this is not because of those devices, but because of DCS (in other games, with much more details, better gfx and such you can do four times those fps). In conclusion: it's DCS that is not ready for VR... I believ the developers are investing their time to fix other things, rather than dedicate their time to the VR. It's an unfortunate situation for us.. but I understand this decision, since most ppl doesn't own an HMD (yet).

Be aware that the game won't turn ON your device if it's OFF (set to turn OFF from the SteamVR options: turn off when quit...). So you have to have SteamVR running, or disable the option to turn it off when exiting SteamVR.

So the issue looks to be about the objects in view.. I enabled the detailed FPS screen and I have noticed that in a random situation (while sitting in hangar), while looking at right, the screen reported 1900 objects loaded and I were doing 18-20 fps, and when looking at my left the objects were 900 and I was doing 52 fps. There must be something really wrong with the ambient occlusion because both the views were similar (no visible objects...). My sets are also all to low (including the view distance)... and again I own a 980Ti .. i don't believe that I would do 18 fps in DCS with all the sets to LOW, while in every other games I do four times that FPS with mid-high settings in VR (in example in Project CARS).

I'm having so many stutters in multiplayer.. and I now lowered everything i can set to low/off. When moving my head in the cockpit, it's like having duplicate frames, making it a pain to fly. I tried with both VSYNCH OFF and ON (now it's OFF), by disabling SteamVR, reprojection is ON... does anyone has anything else to suggest? Again, i'm on a 980Ti and 4.3ghz 6cores. Does anyone here are experiencing similar issues with multiplayer?

I big player is gonna launch a hand tracking device... so I would hold my breath for some weeks...

One thing.. the screen resolution is ignored when running in VR mode right? Because i normally run in 1600p with the monitor...

Hi everyone, I own a 980Ti Hybrid (OC'ed) and a 6core 4.3Ghz... To get rid of the jitters, I have to set everything on OFF (textures.. etc.), is it normal or I'm doing something wrong? I have set the VSYNC already off.

Both the tech are here already (almost)... we will have some hand gesture and recognizing device "soon", from a big hardware player (it will be shown at the next E3), making the virtual cockpit clickable, much more easier. You can also have an hybrid tech (similar to the augmented reality, or the inverse of it): the VIVE has a webcam in front of it, it can be used to project the reality in the VR environment. The possibility are endless...

Any news about the dedicated server? I read about it in a previous newsletter that was being worked on... what's the state currently? We will have a proper dedicated server in the upcoming months ?

...any good server with 120C disabled? It's like playing the noob mode now, you see only "killed by 120C" on every single server out there! :D

Without discussing the fact that TWS is bugged atm so you're forced to go STT... eve if it's 15nm+ .. is there any explanation about it? I mean the specs says that if the target is further than 15 miles you can't STT it ... or it's just speculation? I'm trying to determine if it's a bug .. or if it's expected but not documented.

Only if the developer gives the possibility to apply those rules. If the scenario is: Mirage is ultra-realistic, but the Su27 and the F-15 are not, so they are overpowered.. a poor soul will have the only option of playing on a Mirage only server, or play PvE or on a Mirage only server. Knowing that this is the case will help to keep the decision: if this will be the case even in the final Mirage release, who is interested to play only PvP (like me), will have the only option to abandon the Mirage for something else.. or he will never have a chance. While, if we know that this is a bug.. then the story is different, we just have to wait for the fix.. whenever it will come. I love the competition... but the competition must be fair, I'm honest: i wouldn't join a motor bike race.. with a bicycle, maybe some persons will enjoy it too.. but I like to play having (almost) the same odds. So to resume: is the current radar and STT lock heavily bugged, or this is (almost) the effective potential of the Mirage 2000D? ...I think it's bettor to know today, than investing more time, hoping that it will get any better *in pvp* anytime in the future.

The distance can vary.. sometime it's 30nm .. some other times it's 20nm .. other times even less. A jammer will let you TWS but not STT? Same, for the distance: is there a distance where you can only soft lock but not hard lock? Knowing the limitations and the possible cause would help a lot...

Internal build.. he also already said that we won't have any change for the Mirage today (Friday DCS update), we must wait the next Friday (June 3rd).

In a bunch of occasions I cannot STT my targets... then after repeated tries, it finally locks it. I want to know what could be the cause of this behavior so I can understand how to counter act it. What happens is: I have a contact on the radar (I'm in HFR), I soft lock it (PID).. then if I try to hard lock it, it gets unlocked (it's like the lock button acts as a toggle), no other targets will be locked; I have to repeat the above steps several times, until it finally switches from PID to PIC (instead of unlocking the target...). Is this expected? And what could be the reason?

This is a naive statement: you cannot talk about "realism" for a single component in a multiplayer environment, if all the other elements aren't equally (realistically) represented. So if you make that aircraft 100% realistic, but leaving another couple only 50% realistic, then your 100% realistic aircraft will not be realistic anymore because it will be put in a unrealistic scenario. It will OK only when flying alone, or with other identical aircrafts (it's not the case of DCS). It's like putting a champion swimmer in a pool, but then changing his water with dense oil.. the performance will not be realistic anymore. This is (also) a PvP multiplayer game/sim, and the balance is an important factor. There's many way to balance a game without affecting the realism (in example by limiting certain weapons usage in certain scenarios.. and such).

I'm having the same issue, and no matter if the target is higher or lower than me. Ironically I'm able to see the target with my own eyes, but sometime it disappears from the radar or I lose a solid STT lock. The Mirage radar act randomly... it's like playing the lottery: the enemy is there, you are following him, but then it losses the lock, then you need to wait for the radar to find it again, you need to STT ... and repeat this multiple times over and over again, hoping to finally have a clean shot. I do not have any similar issue with any other aircraft (with a doppler radar) in DCS. I really love the Mirage, but I'm getting very frustrating of flying and being shot ten times while I lose the easiest targets because of the crazy radar. I know we're (much) in WIP, but I want to be sure that this bugs will be fixed, because if this is how it will work in the final version, I will consider to switch back to the the vanilla fighters and wait for a something better (the F18.. the F14.. or whatever it will be).

It doesn't work well: they can do the same, and much longer before you.. the current 530D is a (small) problem for the enemies only at sub-12nm .. at that point they would have shot at you already and they doesn't need any complex evading maneuver, and all this while their missile is a serious threat for you, while yours will be seriously effective only in the <8nm range. You gonna shot one at 14nm .. (the enemy will evade it easily.. even a U turn is enough to make your missile a paper clip), maybe another at 10nm (if you aren't already dead), and then hope to pursuit the bandit to go near enough to shot your Magics. All the above will only happen if your enemy is a noob... ..but again this is not a "bug", it's how the aircraft is underpowered online, with everyone else flying the Su27 or the F15. On same servers they disabled the AIM-120C ... but this is only a work-around, we really need something more to compete (but first the bugs must be fixed..).

Yes, I'm using DCS open beta. All the above bugs are there.. and it's not just about STT, it's all of them together which makes this aircraft (at the moment) unusable. The range of the missiles is another issue (which we know it is a problem atm.. but it's not a bug)... so I'm not sure how you would down enemies "quite well" at 5-8nm .. are they waiting for you at 5-8nm without shooting at you for first when you're more than 10nm away? lol ... while you wait to reach that range, you are already well dead.. unless you mean you're playing on a Mirage only server. ;) Tonight I'll record some MP flights to show...

More days and more I'm confused about the locking system on this aircraft... so far I have: - Targets lost for no reason in TWS (bug confirmed, so waiting for the fix); - Targets lost for no reason in STT (exactly like the above, but even in single tracking mode); - Radar locking in STT directly without first a soft lock, with the radar working in normal mode (no close combat); - As opposite, locking not switching to STT after a soft lock, despite the radar is in HFR mode; - Lock button that unlock the target when pressed (without locking anything else), like it is a toggle when it's just the "lock" button (unlock button uses a separate assignation); ...all the above normally happen in every flight, making the Mirage a flying coffin, since you're usually dead before trying to lock and shoot someone. So far I have been able only to kill bandits by using the Magic and by flying at 1.5ml behind their tail.. (basically only those who didn't even noticed you). I know we still alpha/beta .. but this is frustrating. :(

I'm confused with the terminology.. :D ..when say CCM (in English), you really mean the CAC modes (French) right? Another question: i'm having many issue with target (locked) lost for no apparent reasons (in front of me) in normal mode, so I have to lock them again... is it a recognized bug (to be fixed), or I'm doing something wrong?

Not sure... the warming up functionality is already working? I thought that you can switch the radar ON without any warming up at all... what's this bug about? (and how to avoid it)

That's only about the radar scan frequency: as I said I already have it mapped. If you look at the bug, when you exit the CAC Mode (close combat mode), the radar will return to ENT... I was looking for a way to have it automatically (notice the word "automatically") switch to HFR Mode back (the default mode) without force me to press an additional key. CAC/DEFAULT mode is a command (on the 2000C it's on joystick)... ...while HFR/ENT/INT is another command (left panel)...

I didn't found a way to switch back to HFR Mode automatically when exiting the CAC Mode. I mapped the key as well, but pressing that button every time (additionally to the Normal Mode button) is annoying.

Okie tnx.. I had to save the modified ones or I would have done the modifcation again and it would have been a pain. I wanted the original just to check if I missed anything. Solved anyway.