Milopapa

Here you go. I did two flights: one with minigun only (last line) and one with minigun + doorgunner. The first one (minigun only) worked, the second resulted in an unarmed heli. Syria OH6.zip

Minigun, or minigun + gunner. Neither works (I'll try the rest later). Tried cold start, hot start... I'll include the mission when I have a chance but it's the same for a clean map with a freshly added OH-6 or when I change an existing heli in a download mission (Black Hawk Down Part 1) to an OH-6 and adjust the loadout. Again, the funny thing is, my selection shows up correctly both visually and then on the briefing screen but when the mission loads, it's a plain, vanilla loadout (skin is correct though).

Hey guys! For the life of me I cannot get the weapons to show up in game. They are there all right in the mission editor (both visually and in the list), they show up on the briefing screen configuration, but when the mission loads, the aircraft is weapon less (both visually and functionally). I have everything correctly installed (including \tech\OH-6A_Weaponpack), but no joy. Any ideas?

I have a similar issue: tree canopies and some shadows look different in each eye. I have a canted lens headset, the Pimax 8kx, not sure if it's related.

Let me add, that I've upgraded to a 3090 just recently and set up a dedicated server in my home just so I can offload as much AI from my VR PC as I can... and all is quite smooth even at 3000px vertical resolution in VR, EXCEPT when there is smoke on the screen. Not just engine exhaust, but bullet hits on the ground, smoke from damaged and destroyed vehicles... It basically kills the frametime completely. When the smoke is gone, framerate is back to smooth.

I used to run 75fps in VR (Pimax 8K-X) so I wouldn't call 60fps on a monitor great by any measure. Now it's running at ~45-50.

Just came here to report that in the latest open beta (aug 19, Syria releas), I'm getting horrible fps with the Tomcat in VR, roughly 2/3 of what it used to be. Both CPU and GPU frametimes are through the roof, while other aircraft (Mustang, Huey) perform like before on the same maps. Anything I can upload to help with the investigation?

I have one, just posted my initial impressions here: https://community.openmr.ai/t/backer-441-initial-8k-x-impressions-milopapa/29758

Mike, while we're on the subject. In VR one of the only issues with a pilot body is that it will sometime block certain instruments or controls and you can't "reach" them with your virtual cursor. I thought it about how this is not a problem IRL and I've come up with a solution: when you move the virtual cursor over a body part that's obstructing instrument, the virtual pilot should move said body part out of the way, as if trying to avoid being hit by the cursor. I'm not sure if it's possible to do in the engine (I expect the pilot body is more or less static), but now you mentioned animations, so I thought I'd throw this in.

Do you dirty up completely (speed brakes, flaps, DLC)? What's your AoA, you seem to be fast most of the time.

Has this been posted already? Pretty bad quality but interesting regardless. Also , the last Tomcat seems to perform AAR with wings swept forward.

I never heard him saying anything during Case I recoveries - is he supposed to comment them?

Turns out when you're not confirmed to be in the clear by the tanker, the basket logic is turned off (even though Jester will keep commenting your line-up just as normal) and you're not able to refuel. You need to make sure you have the clear from the tanker crew, otherwise the basket will not do anything and the probe will pass right through it.

Ok, so after forcing the clear contact (tanker guys are pretty stubborn), I was finally able to refuel last night. It's pretty confusing that Jester would actually comment on my refueling attempts like normal even if I'm not cleared for it - but the basket will not do anything.

Whaaat? So all this while I've been chasing a dead model with no refueling logic active? No wonder then... f*ck. I just assumed since the basket looked extended, I'm good to go. I'll need to try this again.

I just spent a very frustrating hour trying to nail the basket of an S3 without any success. I've had quite a few occasions when I swear it should have gone in - not dead center, but in my previous attempts these counted as good enough and the system would suck it in. Not anymore! Feels like the basket had collision detection completely switched off. Could this be a bug in the latest version?

Coming from a newbie, these were the biggest learnings for me while practicing Case I recoveries: Use the fuel flow indicator to hit the right throttle setting Trim the pitch when dirtied up then control your AoA and descent rate using only the throttle (mostly) Don't be afraid to make big changes on the throttle momentarily - simply nudging it will make it very slow to react Watch your final turn rate using the VDI - needs to be a lot shallower than you'd use instinctively Drop the throttle a LOT when you come level for the start otherwise you'll go high in a blink The wires are a lot more forward on the deck than they seem, trust the ball I have to say, both Maverick's video and Victory's guide helped me a ton, as well as watching some IRL videos (encouraging me to make more aggressive corrections on both throttle and stick). :joystick: I'd also recommend the NATOPS manual for general understanding of what everything does in the cockpit - it's great we can use real life manuals!

I believe that is what they said is coming next.

Agree, even the 'basic' implementation is amazing! Buffetting, jet wash, stalls... wow.

Is this a joke?! I just flew the Tomcat and with zero FFB, it felt totally dead. This has been my dream DCS module and it's completely ruined as it is: the stick doesn't even have a centering force! At least implement a centering force! You go all the way with implementing the buffeting of the plane in the cockpit and all and entirely miss the FFB opportunity?:badmood: :wallbash:

Well, I just flew the Tomcat and there was zero force feedback present. The stick felt dead in my hand and my immersion bottomed out as a result :(

Brilliant work, very useful!

QFT. Multi-threading would immensely boost the performance. I simply cannot hit 90fps over Las Vegas in VR (with a top-end PC), but just the other day, after crashing the helo, when the view switches to an external camera looking down, my GPU usage went up to 90+% and my performance stabilized at 90fps. My theory is the cockpit + flight calculations simply starve the GPU and no matter what hardware you throw at it, it won't hit the required 11ms.

First of all, they are not cheap :) Second, monitors contribute to short-sightedness more than anything else in the world, due to the fact that you're staring at the same focus distance (which is pretty short, for that matter) for hours and hours without flexing any of your eye muscles. In VR, you're actually changing the focus distance all the time as you shift from instruments to horizon to landscape to wingman. Third, even though they are a few cms from your eyes, their focus distance is set farther away due to the lenses. VR is a LOT healthier than a monitor. Please stop trolling, you seem to be alone with your opinion here. (Not to mention it's completely off topic.)

This is exactly why I didn't buy Normandy. Burned me once with NTTR, never again. ED simply cannot be trusted with any promises or expectations. They'll need to win me back by delivering at least 2 products on schedule (alpha doesn't count!) and in decent quality (performance included). Until then, I'll stay away and save myself the frustration.