lwalter

New version 1.8 was just submitted to Apple. Hopefully it won't take long until they accept this version and make it available in their AppStore. A few notes: The F-15E UFC display logic is quite convoluted (more complex than F/A 18C). Since I don't know the F-15E well enough to test any possible kind of info that is displayed in its UFC, please expect some bugs. This will be like a beta and I'll be glad to fix display errors I didn't catch.

As you are several getting excited for the F-15E UFC, here's a short preview of its current state: All buttons of F-15E UFC and of AH-64 Keyboard Unit (not displayed in the video) are now working. The last step is to add the displays. It shouldn't take too long now. Expect 1 to 2 weeks max before it appears in the Apple AppStore.

If you know where the source code is, that's already a good start. Current version of XCode can only support back to iOS 11. You would have to find/install an older version of XCode that still support iOS 9. With older version of Xcode, you may have trouble opening all the UI / graphics resources. They make a big part of the app (the representation of the UFC and the button interactions). Then, as explained by @idowza, you may have trouble with classes and APIs that didn't exist in iOS 9 (for the networking part, also for the AppKit framework itself, which changed a lot since iOS 9). I can support if you have questions on the code itself.

Sorry for the late answer @BMamba. As @idowza rightfully answered to you, there's nothing I can do to make a version for an older iOS version available on the App Store. Apple is making the rules and I try to support as old an iOS as they allow me to. Technically, it could be possible, but it would be quite some effort to adapt to the older frameworks and libraries of iOS 9, which I don't think is worth it especially for a free application. both these are coming soon (during this September)

Thanks to all of you for answering my questions!

The following actions don't disengage the autopilot for me, although they're supposed to: - paddle switch (yes, I checked the binding was fine) - alt flaps extended I was wondering if others have the same issue, and then is it really an issue or just missing feature for now?

Same here: F/A 18 radar causes lots of stuttering in VR. It's not so much a FPS loss but very unstable FPS, especially every time you point the plane nose to another direction. Just pushing the "SIL" OSB to silence the radar removes all stuttering.

Retried today and had no crash at all, neither with Mi-24 neither with Apache. I can't really compare to what I did last week, because I updated some settings in DCS today, like reducing trees and scenery details. For sure Apache goes up to 94 % of my VRAM, but works fine with good FPS and all. Let's close this thread for now.

Didn't find a zip file for the date of the crash. Perhaps I didn't ask for saving the crash information when it happened. I'll retry next weekend. However, the texture size reason seems weird to me for several reasons: - I'm using Medium for the quality for the textures - Tomcat loads with no problem; I thought it was a hog for textures - why would there be a difference in texture size between MT and not MT? I have no problem with any plane or map in non MT.

Big thanks to ED for the MT preview!!! Tried this weekend MT preview + VR (OpenXR): huge FPS improvements for all aircraft and all maps. (The only exceptions are: Mi24 and Apache and Sinai Map crash DCS + F15E missing most of cockpit instrument textures. Reported in MT bug thread in this forum)

- I tried all the DCS aircraft I have (that is all existing but Mosquito): All aircrafts run fine, but Apache and Mi-24 crash DCS right when starting any instant action. F15E runs fine, but most of the instrument textures are missing - Same for maps (I have all except for South Atlantic): all run fine, but Sinai crashes DCS.

Are are you launching Steam version or standalone? With Steam version, configure launch options "--force_enable_VR --force_OpenXR" (you find launch options by right-clicking "DCS", select "Properties" and "General section") and select "multi-threaded preview" in the Steam launch selector.

Was there ever any answer from ED on this topic (F-16 variants)? I wish all the planes we have in DCS would get more variants, allowing for scenarios in more timeframes and with more countries. As of today, only few aircrafts, like F14, Gazelle, FW190, etc... have at least 2 variants.

not sure what you mean by best of both worlds ? you mean using a VR headset and iUFCExport on an iPad at the same time?

Release new version 1.7.1 this weekend. It's just a patch to fix some button push issues (not registered or stuck in DCS). (It was also to make sure I could still build and publish it in the Apple App Store, since I haven't touched it for a while )

All, I'd like to give some news about iUFCExport. A few months ago, I bought a Quest 2 and went into VR with DCS. As you can imagine, an iPad is unfortunately no use in VR and as many of you read from VR thread in this forum, once you used DCS in VR and found good graphic settings, it's very difficult to go back to a flat screen However, I got requests to enhance my iPad application for new planes and new panels. Once my work gets a little less crazy, I'll spend again time on this app. Adding new panels is not too hard actually. I'll try to write some guidelines for those with some development background so that they could contribute to the source code on GitHub. Stay tuned!

yes, already had both set. didn't help

So, today I checked my settings and indeed texture setting was Medium, but: - changing textures to High only marginally improved the cockpit labels, mostly the ones that were already sharp enough - why is it that regardless of Medium or High textures, a few cockpit switch labels are blurry and all the other ones are sharp?

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.