kega76

Hi and thanks for responding! So, I see the New menu in the UI, I have a mission with DSMC-, but still I don't get the option to save in the radio menu. I 'm using OB 2.5.6, could that be the problem?

Hi, I've tried to follow all the instructions but as many others I don't have the F10 menu item. Does anyone have a clue on what to do to make this work?

Just want to state the obvious here...so, one thing is the vehicles and their technical state. Another thing is the soft skin humans that operate the vehicles. The blast effects from a bomb would greatly affect them even at distance (lungs/breathing, hearing, concussion etc). Even when sitting in an armored vehicle they wouldn’t be protected from this. Also, as stated earlier, the frag pattern would cause great damage. The frag pattern is even taken into consideration when dropping the bombs so as not to fly into your own frag. Metal pieces traveling in excess of 1500m/s would melt through steel like the armor penetrating darts of the main battle tanks. The last thing would be the moral or fighting spirit of the guys being bombed. That’s a common problem for AI behavior of most computer games, the AIs are super human and too keen to die. No humans is no active vehicles. Let’s just say that the damage modeling should get some attention.:)

I did a test with the 9Ms but can’t say they are acting normal. When uncaging the aim9 the seeker head should start a search pattern across its field of view. If it detects a heat source good enough it would lock unto that. Also the raw sound from the missile would indicate the status. As far as I can see it’s not possible to uncage the missile when it’s in slave mode. In bore it only follow your HMDS.

So, if you read the bok Viper Pilot you’ll Get stories from Iraq 2003. The guy is flying SEAD with the F-16 and have the towed decoy available. Also, at least the European F-16 MLUs are equipped with a MAWS and jammers installed in underwing pylons. I’m not sure if US planes have it though. However, information behind this link indicates that a number of such MAWS systems were approved for fiscal year 1997. https://books.google.no/books?id=wuJsAAAAMAAJ&pg=PA278&lpg=PA278&dq=F-16+EWMS&source=bl&ots=XKSlwNycHh&sig=ACfU3U1nRMkk55jmUTWsN5sywogm6GLGug&hl=no&sa=X&ved=2ahUKEwiypvTUvL_lAhUPwsQBHfvQBFkQ6AEwGXoECAoQAQ

It’s very easy. In the triggers menu in ME, make a new trigger Mission Start and in the last tab choose either sound to all or radio transmissions. The last one will enable you to turn down the sound on the radio or even switch to a different frq to turn it off. The .ogg or .wav files can be anywhere on your HD.

Hi, I’m using the Reverb. Got a new one today and sending back the “old” one. The new pair doesn’t even work. Get stuck with a 1-4 error in WMR connect your cable. Hav tried all the fixes I can find to no use so far... So at the moment, no VR the day the F-16 releases!

Been testing even more, reinstalled etc. Same issues and only in DCS. In a plane everything is fine. DCS is almost unplayable at the moment!

I have the same experience. It has been stirling until some weeks ago. Now even with 70-90fps it stutters and I and the sound goes on and off. Sometimes Steam gives up. This might be a Steam VR issue. I also tried to set priority through project lasso, no effect. I don’t have a antivirus installed. I don’t have the issues in non VR.

What you describe is exactly my situation as well. It went from good to very bad, and I’m not able to figure out why.

Same thing here, almost unplayable in VR.

Same story here. Have had O+ and are now sporting the Reverb. The performance have degraded lately to a level where I’m not able to complete a mission. The sound volume adjusts back and forth and also the Steam screen flickers in and out. This might be a steam issue? When flying 2D I didn’t have the issues. I have a high end system.

Hi, I did go from the O+ to the Reverb. It was worth it! The clarity makes up for some of the annoying problems I have. I’m on my second reverb now, just got a new one from HP. The screen problems seems to be gone, and I’m left with some sound issue (due to the faulty cable connection). I will wouldn’t dream of going back to the O+.

I also have the O+ with the adjustable IPD. My experience is that I spent a lot of time with that trying to find the sweet spot due to blurry edges. It really had to be dead center. Now on the Reverb I do not have these issues. I find the sweet spot to be pretty large, good enough.

GGot my Reverb replacement from HP yesterday. I can’t see any physical difference between the two. I did see a YouTube video where it was stated that gen 2 would have a extra clip for the cable connection. I managed to test them for maybe 20 minutes without any issues, doesn’t mean they’re good though. Anyone here received a gen 2 from HP?

I hope they would stop introducing more half finished fancy weapons and rather fix the more major systems that most of you have already listed. TWS, TGP functionality, ground mapping radar, JHMCS and off board planning functionality.

So, first start the windows app (wmr), then start steam vr and make sure you see the steam cliff house in Vr. Then open dcs, go to settings, vr and apply vr. You’ll have to exit the game and restart for it to take effect. Had some of the same issues before I did understand VR.

Hi, yep. I don’t know the number of the error but today, for the first time, my reverb picture turned black after five minutes in the pit. That has never happened before. The hmd wasn’t even warm. Dcs continued on the monitor at 7fps for 30 sec before it also shut down. There has been a 1903 windows update lately and also, as far as I know, some steam VR updates.

Hi, just noticed that the JSOW A is missing textures after the latest update. It now sports the green camo ish splash pattern.

Does anyone know how to stop Jester from switching from Lantirn view to radar view once I jump up front? Doing the Lantirn stuff solo you have to shuffle between the front and back seat a lot. And it’s pretty anointing that every time I enter the back seat I have to select TV/Lantirn view...

Hi, so the delivery of the bomb could either be done through Auto or CCIP mode (or manual), the only thing is that you basically deliver the bombs as accurate as possible. The laser is for the terminal part of the flight and as stated above, about 10 to 15 seconds before impact. The reason for this is that the guidance of the bomb is full deflection only which means that it will sort of bounce down a laser corridor to the target. If the guidance starts to early the bomb might go out of energy to reach the target and fall short. So, drop’em as accurately as possible, do a left/right 45deg turn or so to make sure the view of the pod is clear, turn on the laser 10-15 sec prior to impact. The time to impact is in the hud TTI. Good luck!

Just an update after todays update. When I was about to change the Stereo.lua again today I came over a file under disk/user/savedgame/DCS.openbeta SAmsung Windows Mixed Reality 800ZBA.LUA This one contains the following: EYE_LEFT = { L_OUT =1.230279, L_IN =1.045660, L_TOP =1.437487, L_BTM =1.418807, } EYE_RGHT = { R_OUT =1.230279, R_IN =1.045660, R_TOP =1.437487, R_BTM =1.418807, } These numbers are more familiar with the ones we extract from your tool. I've added them now to the Stereo.lua but haven't had time to test it. I'll report back when that is done... Update: have tested now and I don’t really see any difference. Seems like I can put whatever in the Stereo.lua?

Hi, so now I've done several flights after a restart. It's hard to really say that something is improved, but it didn't degrade anything for sure. I don't have that eye strain for sure, but that could have been a steam or WMR software upgrade. I will definately stick With this now for a while and test it some more. With the Reverb it's just crisp, crystal clear now, I love it! I'm pasting my settings below just for reference to others. Thanks again for posting this! Left = { x = 0; y = 0; width = screen.width * 0.5; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; eye_shift = -0.032; --tans of side angles projection_bounds = { left = -47.38, right = 43.62, top = 45.42, bottom = -44.82, } }, Right = { x = screen.width * 0.5; y = 0; width = screen.width * 0.5; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; eye_shift = 0.032; --tans of side angles projection_bounds = { left = -43.60, right = 47.63, top = 45.24, bottom = -45.13,

Hi and thanks for helping. I did do the cmd and got the values. However I got several values that wasn’t even close to the ones in the LUA. Also there were several for left and then for right. However, I did write in what I thought was correct, so for left eye (left, right, to and bottom) and same for right. I had like left -43.xx right 43.xx etc. I fired up DCS and did a test run. Didn’t see a immediate difference but I didn’t test it for long. I have the Reverb and have had a sensation of eyes swimming a bit in DCS, not X-plane, and maybe this might fix it. Also it stated that the IPD was 65. Am I in the ballpark here?

Where exactly in the hmdq file did you pick these values (which values?)? I get a lot of different values, but they doesn't directly translate to this LUA file.