lwalter

I going through the startup procedure of the Huey and I noticed some of the buttons in the cockpit had very blurry text, even when zooming in. Note that I'm in VR but I would say about 80% of the texts were readable and even more so when getting my head close to them. Here are a few examples of blurry button texts: radios power button of the IFF master switch. Moreover, seems like the first time I notice that.

Looks like the culprit wasn't Normandy 2.0 update but F/A 18 update that created FPS issues in general. I did a new test with other planes and I had same performance as when I first got Normandy 2.0.

same problem here

For me (Quest 2 at max resolution and NVIDIA 3070), this is one of the smoothest map, whether on desert or large cities. On the other hand, Normandy 2.0 is now the worst of all, I mean really worse than Mariannas, which works decent for me. I read that for other players, it's completely the opposite. I guess there must be a few settings with big influence on the fps depending on the map.

VR performance is excellent for me, as mentioned in my initial post. And this is true including over Cairo city. I'm using Quest 2 at max resolution and I have a 3070 graphics card.

For an early release, it looks absolutely great, the scale of the map is huge and still, lots of attention to details.... and it's even smooth from desert to large Cairo city and in VR!!! Thank you so much for making this map!

Was smooth for me, including over Paris, with first release of Normandy 2.0. Now, it's almost unplayable. Don't know what happened. FYI, in the same session, I tried other maps in case it could be DCS overall, but Syria and Sinai over large cities was smooth.

With the new release of Normandy 2.0, the "huge" churches scaling issue disappeared. Factories are much better too.

Thanks! At least if it's not going to be added to the map, Ugra Media should remove the houses that are scattered in the palace park.

thank you @NineLine For me it's not a problem at all if the church buildings are generic and repeating. The problem is that they do stand out from very far away from low altitude (I was flying UH-1H low to look at the scenery), which is normally not possible, especially in urban areas, unless we're talking about very large cathedrals (like in Paris, Chartres, etc...). Here in every village, there's a church, which is realistic, but it's way too large and high. For the chimneys, I agree as well that the factories are well placed. Not a problem with that or their number, but again, I feel the chimneys are way too high. As somebody else mentioned in another, maybe this scale issue is made worse because the villages look pretty flat and empty.

First of all, it's definitely a very nice map with lots of efforts put into it and as of now, it's the largest normandy map and definitely one of the best from any flying combat simulator. It also run smooth in VR for me, including over Paris or London, which is amazing. For this first discovery of the Normandy 2.0 map, I was flying around low-level with a Huey. After all these Normandy maps I've flown over, and after all the hype I read about this one, I was maybe putting the bar too high. Please note that I live in the Paris region, in a place near Versailles on the map, and I've been many times to the Normandy region, especially visiting the D-Day landing beaches. So flying over these places, I knew what I was expecting, and yes, I know this is supposed to represent a WWII map. The one issue that annoyed me a lot right away is the scaling issue (I think it's an issue) of the churches and the factory chimneys. They're way too large. In an urban area like Paris region, It's impossible to see churches so far away, because they surrounded by other building. I'm not talking about the few cathedrals in this region, but regular churches. Same for factory chimney. They look way to high. I posted a bug on this one. The urban area around Paris doesn't look very dense. Of course, it wasn't as dense as today, but at least we should see more villages all around Paris. It feels really empty to me. The famous monuments in Paris (Eiffel Tower, Louvres palace, Notre Dame) are all gorgeous, but I'm missing for example the very visible Sacré Coeur Basilic on top of Montmartre hill. The landing beaches and "Atlantic wall" fortifications look really nice and the beaches look fine, but there are too many of these weird big round rocks everywhere on the beaches. I don't know if the map is supposed to be before the D-Day landing or not and I haven't checked if you could change the date, but I like the idea of some other WWII sims where you can see the map before and after landing (e.g Mulberry harbor in Arromanches). Again, the Normandy countryside seem a bit too empty: where are all the villages? Where are the German fortifications on the island next to St Vaast la Hougue? This is just my first impression and I hope I'll enjoy it more after more flights other this map. Once again, it's a very nice map, but in mind, I was expecting at least the same wow effect as Syria map and it wasn't the case so far.

The Versaille palace garden is only recognizable by its long cross-shaped canals. However, the palace and rest of the gardens are "invaded" by town buildings.

Churches and factory chimneys appear way too large or high. They stand out from very far away I don't know if this is the case everywhere on the map, but in the Paris region, this is very disturbing. You can see these buildings (churches and factories) from very far away but the cities in which they are look completely flat, making the effect even worse. All churches look like they are as large as cathedrals, even as high as Notre Dame cathedral in Paris! Factory chimneys are all too high.

At least, does anybody know if it's possible or not?

When launching DCS from Steam, I can choose something like "Launch with Oculus", "Launch with multi-threading", but not "Launch with Oculus and Multi-threading". How can I try the latter?

Thanks! But Oculus Quest 2 already supports in-built hand tracking and you can activate it for standalone games in the headset. How can you force hand tracking with Oculus Quest 2 rather than controller tracking in DCS?

Normally, I launch DCS from Steam and check the VR with Oculus option and it works fine. I noticed that I never ever checked the "Enable Virtual Reality Headset" setting DCS. Am I missing something? Looks like everything is working fine though, including the pointing to buttons and switches with the Quest 2 controllers.

WIth Quest 2, you can use your hands as the controllers and it works pretty well in existing VR titles. In DCS, I can use the default controllers with no problem, but I can't seem to be able to use my hands as controllers. That's a pity, because it would be so great to (virtually) push the buttons and switch with your fingers. Did anybody manage to make it work?

If I don't activate the "precise" mode, then enter the grid coordinates work fine and what I entered is reflected in the waypoint screen. If I toggle on "precise", then select grid square and then enter coordinates on UFC, neither my grid square, neither my coordinates are kept. I would think it's exactly the same procedure between non-precise and precise grid coordinates, but correct me if I'm missing something.

@dleffler I picked the VR preset from DCS graphics settings and everything ran super smooth (I tried A-10C, F-16, F/A-18, UH-1H, F-86, F-5 and the FC3 planes on Caucasus, Nevada and Normandy so far). Actually, everything ran fine for about 2 hours.... until I ran into random "PC disconnects" from the Oculus Quest 2.... (It's not DCS, because I got the same issue on other apps). I read that I should "deny access to files" to avoid this issue. So, I'll try that next time. Don't know if it's really the solution, because I saw many people complaining about these PC disconnections in the forums.

@Paul_Exotic That's what I was afraid to read. I really would like to avoid tweaking many internal and low-level settings just for DCS and then realize that it messed up with all the other VR simulators I have, which all work great now. Nevertheless, I'll try at least to tweak the DCS settings themselves. @dleffler Indeed, I have just left my settings as they were for 4K on flat screen. I'll try the VR preset. For the screen resolution, will DCS automatically choose the resolution that fits the Quest 2 or should I enter it manually? I use the Steam version and the Oculus link (USB cable). I also connect my Quest 2 to the PC via the PC Oculus App. @Ramsteinsure, I'll try that when I create new settings for VR, as suggested by @dleffler What about the Quest 2 controllers? Are there of any use when flying? Can I ask the Quest 2 to track my hands? I think I saw one game that was doing that (I think it's Elixir).

Just got an Oculus Quest 2 as a present. On my other flight simulators, I didn't have to tweak anything or change any single setting (until now, for my flat screen, I had 4K ultra or very high settings). Everything just worked smoothly in VR and everything is readable (not super sharp, but better than good enough) On DCS, I noticed: - texts are close to unreadable and overall image is not great - FPS in Huey were acceptable, in F-16 it was unflyable. Some controls were interfering with my stick. Could DCS associate the Quest 2 controllers with axes by default? I really like how you can zoom in an interact with the switches with the Quest 2 controllers, but how do you practically do to have these controllers in your hands and use the stick and throttle at the same time? Overall, VR is such a game changer. As I read many times in these forums, you really feel inside the planes and you really get a real sense of distance. Several times I just wanted to touch the cockpit panels or switches, as they felt so real. My main issue now is to find the right DCS graphics settings I guess. If possible, I'd like to avoid tweaking too many places (oculus app, debug, NVIDIA planes, etc...) because it just worked fine with the other apps.

After many years, I'm still not able to do A2A refueling. The best I could get was the endless "return pre-contact".... until yesterday, when I finally got a "cleared for contact". Getting closer and probably too excited about this new milestone, I managed to get my A-10 nose plugged into something for refueling.... but not the right place I guess Maybe someday, I'll get it right. null

Wrong Alert. My bad: I thought the flaps lever was animated in the A10A or the F15C, like in the Mig29. In external view, flaps bindings work properly.

Neither my throttle buttons nor the keyboard keys like "F" have any effect on the flaps anymore for the A10A and the F15C. I double-checked the bindings and both keys and buttons are recognized in the bindings screen. Checked on other FC3 planes and have no problem. No clue what's going on.