joca133

5 crashes on MP after updating to 2.7 and the clouds look blurry and even on super. Performance has not changed noticeably and it is still abysmal on a 3080. Not happy.

I had tons of fun with the M2000 when it came out. Baltic Dragon campaigns are the finest and most immersive ones I ever played. That being said after the latest upgrades it became unplayable for me. The controls changed and are incredibly clunky and unintuitive, rwr, radar and other systems became certainly more faithful to the real thing, but I never got around how they work. For me it lost the fun factor as it is quite maddening when I have to go through a sequence of buttons on an unreadable cockpit to try and release a bomb or use the guns. It is also very lacking compared to newer addons (f18, 16 and jf17). I would strongly advise against it, sadly.

My play sessions are 3 hrs avg and I always have some juice to spare, with some 1-2 more hours between menu, mission editor, windows etc. If you config your usb to deliver power when pc is off then you can always make sure it will be 100%, except when you forget it on or block the light sensor :megalol:

If you use an aftermarket with a separate ac adapter yes. If not, just usbc, then it slowly drains. how slow? I find if at 100 it will work for a whole day on dcs (+6hrs). The issue is only when the darn thing turns on by itself (light sensor triggered) and discharges. Several times I had to wait 15-20 min to give it some juice and then play for 1.5 hrs. Now I installed a magnetic adapter and use a sepparate usbc ac/dc cable to keep it 100% when my pc is off.

1) Improved UI with better copy/paste and selection of multiple units. 2) Mixed A/C groups. 3) More dynamic weather, ideally with options to change into a certain weather after X minutes or via trigger. 4) 3d viewer in editor. 5) Better “explosion” trigger (current 1000 limit doesn’t seem to do much damage if I want to cover an entire aerodrome).

Yeah, cockpit quality looks good for me, although sometimes the text next to some switches get blurry (unreadable) on VR. Im almost positive its something on my end though.p, and it doesn’t happen often. INS upgrade is welcomed. Thanks!

It may be my imagination, but going from 16GB to 32 I noticed significant improvements and zero crashes or freezes (finger crossed) on multiplayer during heavy missions. It’s about time to get some real performance optimizations, the last patches seems to have made things worse.

Hi. It takes some tweaking to get a decent performance. How decent? With a cou running at 2.6GHz like you seem to have and a 1070 I wouldnt be too optimistic. But try this guide and focus on reducing shadows (or even disabling them) and msaa, spend whatever is left on super sampling via OTT. Also try out the shadder mod and look in the forums how to disable xbox game bar stuff. Unfortunately the game is poorly optimized, it has been for half a decade and, even with high end systems it rarely gets a stable 90 fps on all conditions (with 1080ti and 3700x I aim for 45 fps). Good luck!

Can’t wait to play it!

Since the last small update (third after v19), motion on my link is way too sensitive. I mean, my view is shaking like crazy and using zoom gives me a headache. No, I don’t have Parkinsons before it is asked. I am using ASW and keep a constant 36fps. I am suspecting my usb port but don’t know how to test it besides the standard oculus test (result was 1.7 Gbps). Any tips on how to smooth head motion tracking on Quest?

That would explain why sometimes I end up doing my approaches 5 miles away from the runway lol.

Yes, you are correct. Took me a while to figure that out. Now my pilot is no longer getting hypoxic lol. Can’t wait to have a full manual for this thing, there’s a lot Im not sure Im doing correctly and stuff I have no idea hoe it works (e.g, css handle and how to eject just canopy).

I used them and found pretty useful if you can get them fixed like others mentioned. However, after having PointCtrl I sold both unites along eith my lilliput screens and never looked back. PointCtrl is amazing on VR, really the best “hand track” solution right now. Sadly I did not test mfd+PointCtrl, but if you have a setup like the one posted, I think it would be even better!

Another vote for PointCtrl, it works great! Also have 6 additional aux buttons attached to it and positioned on my Quest, use them to trigger nvg/nvg brightness, jettison etc.

After the last Oculus update my Quest is extremely twitchy, like the motion sensitivity has been crancked up and there is no smoothing whatsoever. Very noticeable when using zoom and giving me a headache when trying to read something on the panel. I don’t know what is causing or how to fix it. Sensors are clean.

After a thorough comparison between hot/cold start, maybe I am turning on the emergency o2 handle during preflight (yellow handle) when I arm the seat, thinking it was necessary to arm it.

There is a bug. Can you explain why with bottle on, hose connected my oxy blinker stops but the oxy qty is unchanged (always at -~2200)? Or why on some missions (bear campaign m10) I get hypoxia after 15-20 min while in other I can fly for 45 using the same startup procedure? I don’t think Im forgetting anything, there isn’t much to remember (hose, bottle, canopy pressure, temperature/ecs) and on the some missions this happens and not in others, plus I always double check everything with the checklist. With hypothermia its even worse, if I change temp 5°C my pilot passes out? Ridiculous. I hope there will be a n option to turn these poorly implemented features off, I am sick of having to abort missions over this.

We need a way to disable hypothermia and hypoxia, this bug is annoying.

Finished, it was very very good. Mission 10 was a bit too far if Im being picky. Then I got the hypoxia bug and had to restart 3X and eventually resigning to fly at 12000ft so I wouldn’t pass out. Annoying, but not your fault. My favorite I think was the convoy interdiction (M06), and the one following that M07 scramble. Lots of great times, thanks!!

A little late to the party, but I can confirm after playing three times the last mission (M10) on Bears’ amazing campaign that I am blacking out after 20-30 min in. It is not my cold start procedure, I have oxy bottle on, hoses connected, temp monitored and ecs norm. The blinker is not working, meaning no oxygen going through. My guess is I ran out of oxygen, but then the o2 qty indicator hasn't moved and is at 2000! I managed to recover every time by doing an emergency descent with ATT on and 15° nose down. Is there a solution to this BUG? Is there a way to disable hypothermia/hypoxia?

Copy-paste from 51-58 worked beautifully. I just did a “cat3” on kutaisi for the first time on this aircraft. This DST 59 is genius, I could even plot a 12nm faf the way I wanted.

Thanks for the detailed explanation, I got the basic of DST copy/paste already from programming the reporting points for a/g cruise missiles and you were very clear on what needs to be done. Ill go in the soup later on to try it. Very powerful and useful on PG I guess, since apparently with this method you can tune manually the ILS frequency through the code table on the kneeboard. Again, thanks!

Nice! Seems like there is a lot of hidden features in this system, although I am pretty happy so far with how simple it is overall. Thanks! :thumbup:

Interesting, I would prefer being able to cycle all runways. But it makes sense that an airport only has 1 active. The issue is with DCS vs JF17, I was told to land on rwy 22 but it defaulted to 04. Even if I was on the correct side it defaulted to the wrong runway according to winds and airport. A bug? Ill play with 059, if that is the only way to get the correct approach.

Awesome, I was looking for a way to manually tuning. Now on “autotune”, say airport #51... is there a way to select a reciprocal runway? On mfcd I only get the option to select 10R or 10L, which essentially just changes my PT inbound. How do I switch from runway 04 to 22 on Anapa, for instance?