uri_ba

Motion sickness is a bitch, but how to cope with it is individual. I remember that we had a DK2 at my workplace for a project. I've been put into a roller coaster demo. I usually suffer from motion sickness when I get disconnected from movement (I.e read a book on a bus for an extended period). The guy that was in charge of the DK2 had warned me that people get very disoriented during this demo. All I did was to ground myself, hold the table in front of me with to fingers to get a grip on reality. So maybe you should try that first, find a demo in pCars or dcs (and go for the ride. So you can take the head set off. Anyway, start with short "rides", 2-5 minutes initially. And once the "ride" is over take the headset off and stay seated. Wait for your body to regain speacial orientation.

Eye strain in VR (assuming proper lenses) is usually due to proper adjustments of the HMD (straps and IPD)

I don't think the steamVR implementation matters. openVR API (assuming ED use it for the vive) reads renderTargetMultiplier value using it's steamVR driver. However, the API should allow you to set runtime value when initializing the HMD. Which doesn't seem to be the case. -- Update -- Not a real coder, but I peeked in the OpenVR a little more... it seems that there is an option to override it (but it's not very well documented). seems like the vr::IVRSettings namespace has a "SetFloat" function that takes a key and a value. so in theory you can override the "k_pch_SteamVR_RenderTargetMultiplier_Float" value... I'll just leave it here for someone that actually knows what he is doing :)

I don't have "Normal" 1.5 installed, because I don't fly online, I don't really need it. performance is lower in 1.5.4 then it is in 2.0.2 (FPS is the same on similar areas, but 2.0 seems more stable - or maybe it's just the tracking jumping around?), but it's not a fair comparison, as NTTR has much less objects then Caucasus map. Flying in the Poti area yealds, ~35fps on the vive for me. choppy and annoying, but better then nothing, it's possible. (only tried P51 so far in 1.5.4 and P51 and M2K in 2.0) --- Update --- Managed to get 45 stable in low altitude in free flight poti in the P51. By low altitude I mean weaving and boring between the city buildings low. I've OC'd the 970 to its thermal limit using MSI afterburner (I have a second 750 blocking the airflow, so it's only a mild over clock +150mhz on the boost, pushing it to max 91 deg) Then I've tweaked some settings in DCS. Lowering MSAA to x4, shadows to "flat only" but pushed render distance to far with terraintex high and Tex on med. I'll give it a run on 2.0 as well and if everything would be the same I'll post my options.lua

I've changed something in the graphics tab only (not touching the VR settings) and they didn't stick (changed VIS range from High to Med)

+1 It's not just the VR option. it's any setting change (I even tried turning VR off - to verify it's not a generic issue, no luck on disabling that). and more info, settings are not saved. if you close the game at this point, when re-opening, settings are same as before the change.

Bluelight, try disableing HT from the BIOS. this will force your CPU down to using "only" 4 cores, but it might give you the little nudge of extra CPU power. I've disabled mine and it looks maginally better in 2.0. I've managed to install 1.5.4 in parallel, but I have another issue there. every time I change a setting there, and press OK, it returns to the hangar and shows me nothing there... :|

It's a mess, I only have space on my SSD for either 1.5 or 2.0 so switching back and forth isn't fun for me. In addition, I have 7 devices, all of them need to be reconfigured per plane per version. (Which is why I hardly play in DCS lately). So I guess I'll be waiting for 2.0.3 to be pushed out And start saving up for an 1080

I'm trying to figure out what is the problem on my rig. I've explicitly turned Vsync off on the nvidia panel. Only got 90fps looking straight up. The second something is I'm the frame, fps drops to 45 and stay there. When I look around I might get down to 42 frames before fps drops and locks on 30. So something triggers vsync and I can't figure it out. More on that, In the VR stream Matt had done two weeks ago, he had shown the "new VR settings" yet it's not in 2.0.2. is it something planned for 2.0.3 or I'm just missing an option?

For me it's even worst (vive w/970). When I move my head too fast, the left and right eyes are rendered on different positions giving a "cross eyed" nausea. I've started installing 2.0 (which seem to take forever). I'll give it a test later today and report back.

No need. Switch the TAD from L/L to UTM, then it will show you the cursor position in UTM.

Hiroshima was 20KT. Besides, Do you really want to encourage people nuking everything?

I say Blame FC3! :)

Install the latest (currently 1.2.4) it works just fine with DCSW1.2.3

try running TAC as administrator and run the export script installation, that might give him the permissions needed.

10x Headspace! :) Looking forward for it. Keep up all your good work! Uri

I'm aware of that. and I'm not talking about spectators/"dead"/"ejected" users. they all have TARS enabled and have certain permissions. I'm asking for the option to have a checkbox saying something like "hear non-tars users on <USER DEFINED FREQ>" so I can choose to monitor that frequency if I want to (and respond on that freq as well). Sometimes when you fly DCS on a TS server that supports a whole community, people might pop in from time to time just for fun. they can hear you speak - but you can't hear them. In addition, When the TARS plugin is disabled via TS, it will not reset the mute lists. it is possible to add a keybind to toggle TARS to STBY mode instead of needing to disable the TS plugin (to be able to communicate out of the game) And one last question, What are the TS permissions needed for TARS, I've seen a server where we kept getting "error" from the TS everytime we transmitted.

Is there any way for a player within the game to hear spectators or people just in the channel? if someone's game has crashed, how can he let anyone know? if people are flying togeather and someone is joining the channel, they can't hear him at all... is it possible to have an option from within the control panel to set a "frequency" for all "non TARS" users?

and what about all the "Forever Alone" folks, don't they get Valentine's gift? :)

I'm affraid you are probably right, and I'm probably stupid :P

I've flown the first Quick mission. on landing I was heading to Varazany. Opened up the CDU divert and it said tower FREQ of 138.00. I've called it up, but got no response. I've then checked the F10 map. there the FREQ was 140.00 and the tower has answered as expected. Could you please make sure the Airport data in the CDU is updated? Thanks, Uri

10x

Hi folks, I've been playing around in the DSMS screen and I was wondering. 1. Are the delay settings on the fuzing is in ms? couldn't find any thing in the manual. 2. Is fuzing effects of boms being taken into account in DCS? for example, If I set on a GBU-31 NOSE to NONE and put in a long delay on the TAIL fuze would it penetrate more then if I put a short delay N/T? 10x, Uri

I have TS3.0.1, TARS doesn't seem to recognize it. Am I missing something?