Lace

I'm running it in VR on a laptop (i.e. diet) 3080 with 16GB. Perfectly acceptable performance for me, YMMV.

Having spent several hours this weekend over Fulda in the FC3 A-10A all I can say is, please please please consider a FF A-10A! The aircraft was literally made for this map.

As the title. In the ME or F10 it is not immediately obvious where the border is in any of the three chart/map styles. I know it's not a difficult task to cross-reference a contemporary chart, but it would be nice to see it in game.

I guess this is the de facto 'First Impressions' thread then? I'm not a hamburger, so can't comment on the geographical accuracy of anything. However, I love the map so far. I've tried out a few aircraft in a few locations but still only about an hour in. My biggest shock was the performance. I had fully braced for a terrible VR experience and was pleasantly surprised that it seems to run as well as pretty much all other maps, only slowing a bit over the built up areas. My test flights were in rain and fog, so I would expect CAVOK conditions to improve framerates a bit. When Syria launched it was unplayable for me until a few rounds of updates and optimisations, and I was prepared for the same here. I flew a Gazelle over Sennelager, which seemed a bit empty, but fine to build on. I took an OH-58 briefly around Fulda, and a F-15C out of Bitburg, under the clouds, through the valleys, and then up over the clouds for a quick look around until I had to shut down. The FC3 F-15C performance was very smooth, even over the detailed base area. The Kiowa (always a poor performer on my system) was a bit stuttery, and the Gazelle was fine, but flying in a low-detail area for the most part. Next flight I've a 'GR-5' lined up at Gutersloh for another test. Anyway, TLDR; Map looks great, and performs surprisingly well in VR.

Agreed. Airfields are generally very well tended.

Since everyone else is asking... Push the boundary north-west a bit and you can include Lakenheath for the F-15C & E, Bentwaters/Woodbridge for the A-10s (and back-filled F-16s), Honington and Marham for Tornado (eventually) etc etc. That whole part of the UK is flat and featureless anyway ( ), so a low detail coastline with some airfields is all it would take.

Today or not, it seems fairly certain to be in this next patch release.

My thoughts are rain. Lots of rain, and lots of hiding behind trees in my Gazelle.

ROLEX 1440

That's valid.

Kola is over 150 with far fewer built-up areas.

Push the boundary north-west a bit and you can include Lakenheath for the F-15C & E, Bentwaters/Woodbridge for the A-10s, Honington and Marham for Tornado (eventually) etc etc. The problem is, where does the expansion end? There will always be a compelling reason to make the map 'just a little bit bigger'.

I don't think Ugra developing a map has any bearing on the work ED carries out on their maps or the core game. More is better and there is no obligation to buy it. A central Europe map is long overdue IMHO.

Go Bratti go!

Guten Morgen meine Herren.

I finally have a valid use for the Chipmunk Yak-52 (Yakmunk?) skin*. Snooping over Berlin out of Gatow. * I know it's not the correct skin though. Ahem...

Chances are you are rotating early. Calculate your rotation speed prior to take-off, and start easing back at that point. I have a performance calculator spreadsheet, but for rough figures use this:

Thanks. I don't remember seeing the 'Developer' tab last time I looked - does that need to be enabled first somewhere? I'll look again later today.

How do you actually turn it off? I can't find it anywhere in settings. It's also the floor which is causing the issue, I can make the horizontal distance big enough, but looking down shows the circle. Maybe I need a bar stool

Does anyone know how to get rid of the blue circle when using the Quest 3? It never appeared with my old Rift S, but since upgrading I can't seem to switch it off anywhere. It is quite distracting when looking down into the cockpit and completely unnecessary when using a sitting (stationary) boundary.

Command: Modern Operations (and CMANO before it) allows a side to set their posture in relation to each other side, either friendly (blue), neutral (green), unfriendly (orange) or hostile (red), with yellow being an unknown/unidentified contact. This can be changed by triggers, so a side which is unfriendly might intercept another side, but change its posture to hostile if fire upon. It allows a lot more subtlety in scenario design and can create tense 'who blinks first' situations where each side is reluctant to make a move which escalates the conflict. It even allows a 'biologics' side, so whales and schools of fish can be included to complicate SONAR searches. In DCS some of this can be worked around by ROE settings, or engaging only a specific group on a trigger, but having it inherently incorporated into the ME would be a nice improvement.

I hope so. I mean, that's kind of the point, isn't it? Have pre-defined DTC files rather than setting everything up pre flight, whether in the cockpit or in the DTC UI.

A level turn does not mean no elevator input. A level turn with 30deg bank is approx 1.2g, and 60deg is 2g. That g is generated by stick back pressure, otherwise the turn wouldn't be level, it would be a descending spiral. When levelling the turn the stick back pressure needs to be reduced, otherwise you will get a pitching up action. The Viper FWB does some odd (not odd, perhaps unintuitive) things and there are posters here who are far more qualified than I am to comment on that, but learning to anticipate what the aircraft will do, and compensating before it happens will help you remain in level flight when entering or exiting a turn.

I do build nullthem into my own missions, but obviously they are cosmetic only.