fjacobsen

Please excuse me - Normally I´m very patient and have a great understanding, but this really starts to become ridiculous. This comes ontop of the Razbam dispute, CH-47 delay without a new date, missing Kola Map updates - a map that I find to be in too early acces. Note that I´m a long time user of DCS - all the way back to BS1. I have bought most modules as EA and never had a problem with what >I got, apart from the too early F-16 and the SC "incident" for acouple of years ago.

Regardless if its Early Access or not, what is shown in previews for the Early Access, should also be what we see in an Early Access release, otherwise I would call it false advertisement. Even for a Early Access module, we should clearly be shown and informed on what we will get the day of an Early Access release. Personally I have not a problem with Early Access. Most DCS modules have been bought this way, but some are simply too early, like the Kola Map. When shown screenshots like the one above, one would expect this to be what You will get when released.

Ensure that You don´t have a Pitch Breakout. Check this by opening the control indicator window (Ctrl+Enter). The small diamond must be within the bigger one. Your Joystick might need calibration.

So another postponement... I start to wonder if we will see anything this week. I was irritated about the CH-47 now delayed until further notice (no plan), but found it ok. But now also the main update, and this also so close to the anticipated release time.... Children an wife send to her sister - easy dinner (Sausages and fries) and now for nothing.

Because he did

Irritating, but better later than sorry. I think there is more than enough to do with the rest of the updates and the Afghanistan map, so let's be possitive. Also it seems that the F-15E radar will be fixed, so either ED has managed to patch it, or RB has reacted.

At least the Airbags work

Didn´t You notice that this release is Early Acces ? The module will be updated over time and most probably get a much better damage model.

Personally I want to wait claiming a refund for the F-15E, simply because it´s still not clear if the ED/Razbam issues will be resolved, so I try to keep a cool head and rather like to wait, simply to help not fueling the fire that is raging within the community right now. But to be sure..... @BIGNEWYJust to be sure - the day when it will be clear that the issues with Razbam cannot be fixed and support ultimately will be ended for Razbam modules - will I then still be possible to get a refund for the F-15E, and how will the situation for the M2000 and AV-8B be ? I think it´s fair for us customers to know where we stand, should Razbam definitly close down support for their DCS modules.

Setting the UDU to be in Left or Right Eye in VR does not work - it is present in both eyes regardless of setting.

I can grab the M4 from the Co-Pilot seat, but I cannot aim or shoot it.

Maybe we should simply come down to the fact that in single player - one person has to do two persons job. 'So while a slight "drift" would be nice, I can also accept the current way they have done it.

I would think it would be part of EMCON - being able to turn off an emitter.

Ok- but still the switch does nothing, as far as I can see.

The swicth for setting the HUD altimeter between radar altimeter and baro altimeter is still inop. Also the radar altimeter is able to display the altitude even at 40.000 ft, which I assume is incorrect - this is on the Kola map.

Yeah with a six week update frequency, next update was not sheduled before end of may, so there isn't anything to complain about. I (naivly) hoped for a surprice release of the F-4 Phantom and maybe fixes and additions that might have been ready to be added, but it´s unfair to be disappointed.

Performance on my system with a Quest 3 is Ok. I'm a bit underwhelmed by the number of Airbases and has yet to find any of the Swedish Road runways and I hope they can optimize it for better performance. Otherwise it looks like a good start with some beautifull scenery. I would say that performance is like on the Syria map. Edit*** Maybe fly around for a while, since the shader cache has to be properly "updated" in order to gauge performance. I think I got better performance on my last flight out of Bodø AB in a F-16

As such I have nothing against pre-ordering, but it is now exactly 7 month since I pre-ordered the Phantom. Maybe it´s me - but I find that it´s too long time from pre-ordering to release.

My preferred setting is DLAA without DLSS. MSAA causes too much shimmering using 2x, but 4x only helps a tiny bit with worse performance. DLAA is more blurred looking at the distance, but I prefer this over shimmering with MSAA. I tell myself that it is haze, since IRL this also causes a kind of blurriness. I have not tried DLSS with the new DLSS version, since I get good performance already with DLAA.

In 15-20 years maybe, when / if they can get hands on documents for it´s sensor and weapons systems on the present Block version. Note that for all the present "modern" combat Aircraft in DCS, the Mark / Block numbers simulated are all more than 15 years old.

It´s weird... I have both V63 on my Quest 3 and in the Oculus PC App and everything works as it always did. I´m not sure if I still use then openvr.api.dll from the Open Composite Github site and if it makes any difference to the issue. Here is the link: https://gitlab.com/znixian/OpenOVR (look under pre-game install and download the 64bit version)

As posted before - I have both my Quest 3 and the Oculus Link app updated to V63 and has no problems running DCS in OpenXR mode. Oculus Link app is set to use Oculus as OpenXR runtime. OpenXR Toolkit works with no issues.

Strange... I have V63 in both the Oculus app and my Quest 3 headset, running DCS in OpenXR with the OpenXR Toolkit and does not have or had any issues. Oculus is set as the OpenXR runtime.

I got my T-shirt with a Parcel service today (Denmark).