lwalter

Thanks @silverdevil. I have already read it, but I have no account binding anywhere and I don't remember I ever did for DCS. So it can't solve my issue.

While waiting for this situation to be fixed, I wanted to switch to IL2 GB.... and surprise: same issue. No more authorizations to launch the game either... I wonder if it's a general Steam issue or a general issue with the DCS and IL2 servers...

I read somewhere that there was now an issue from Steam users of DCS, especially the ones mixing Steam and standalone modules. I'm launching and buying DCS modules exclusively from Steam. Why can't I get any more authorizations from DCS and have my 89 DLCs disabled? I checked in my DCS profile on DCS Web site and didn't find anything about "binding" as other thread mentioned. Exact error message at start is: Failed to get authorization data. Error code is 502. No saved authorization found.

Have you tried to switch to Dark Mode? It looks like it does what you're asking for.

yes, I saw you could order replacement parts on their web site and I did so.

Thanks for the feedback! WSO UFC is not supported yet. The vol rotaries are not implemented. I used that free space to put the channel increment/decrement instead, because the white button is already used for push. If it's too disturbing, I can change the increment/decrement position. I noticed the radio frequency decimal position issue. I'll fix that this weekend. I know the PB10 button doesn't get a display update, but I didn't notice that the MENU button does the same. I'll check that.

You're welcome ! I noticed the problem with PB10 too. For now, I don't understand what's going on. It's as if DCS wasn't sending any update after you push this button and only this button. Will analyze more this weekend. WSO seat is not supported yet.

Note that I'll stay with MFG Crosswind. In their Web site, you can order any replacement part, which is pretty cool.

My MFG Crosswind has a broken USB port. It was a in weak state since the beginning, but was still working fine until today. I'll try fixing it, but in case I can't fix it, what would you recommend as replacement pedals?

-- And here are finally the updated Lua files: https://github.com/wluc9875/iUFCExport-LuaScript/releases/tag/v1.8

-- The new version is now released on the App Store. I realized I missed one thing: publishing the updated Lua script. I'll do that in an hour or two. Meanwhile, your display will remain empty. Sorry about that.

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.

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)

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?