ANDR0ID

I've built/submitted a "general" profile which should work for any full fidelity module or mod that doesn't have a separate profile. Currently built to display vertical speed (FPM), Altitude (Feet), Magnetic Heading, Fuel (%), and Airspeed (knots), as well as Flare/Chaff count. Fuel may be off depending on the module, but most I've tested seem to be able to show it as a %. I still plan to build more detailed profiles for modules/mods as time and access to them allows, but this should provide the basics for almost everything now. Note: FC3 planes are NOT supported... and there may be some other outliers I'm not aware of as I haven't tested this with every full fidelity module or mod.

@Wostg Great work on the Apache profile, especially the KU page... much better than my original plan. I did take the liberty of editing your profile with some of the items I was working on, interested in what you and the community think. Changes: Updated altitude to be a constant 4 digit value, ie on the ground is "0000" (currently radar alt, but easy change to barometric) Updated heading to a constant 3 digit value + M for magnetic Added (total) Fuel in pounds Edited the speed conversion... the values originally used didn't seem to be on for meters/sec to knots? Added a status window for Master Arm/Safe which will also display Master Warning and Caution alerts Edited the Vertical Speed readout to display Feet per Minute to align with the AH-64 HUD Added Chaff and Flare Counts to the main and KU pages. _____ Edit: I found a heading bug Shows negative values for 353-359 Magnetic, will correct in the next version. wwtapachev2.zip

I started to work on this, but it appears the CJS Super Hornets work just fine off the default F-18 profile... no new profile required.

I have basic profiles built for all FC3 aircraft, but the last time I worked on it they would not load on the UFC, even just static data.... jump into a full fidelity aircraft and everything works. That issue is why I haven't release them yet and I haven't had time to revisit the issue.

Awesome! I won't have any hard feelings if someone beats me on making a profile. Its great to see others building on prestonflying's work to support the community.

Apache was actually gifted to me already... I've made some progress on an AH-64 profile for the WinWing but its been slow going between the extra complexity of the module and real life commitments. Not dead, just on the back burner currently.

I've identified a number of the data strings, unfortunately the raw data is not useful for exporting to the UFC. I'm working on code to make it useful but life has been busy lately so progress is slow. The Apache code is less friendly for data export compared to the other modules I've done, but is probably a good learning experience as I expect more and more future modules will probably use a similar data architecture.

Thanks to the generosity of @rrutko I've started work on an AH-64 profile... static data is working, now the more challenging part for dynamic data. I expect this profile to take some time as I learn the module and how it exports data.

Just for fun... TF-51D profile with radio frequency, altimeter, and true heading. This may also be directly applicable to the paid P-51 modules but I am not able to test that myself. Proposed code uploaded to github.

Cross posting in the JF-17 forum for improved visibility: A JF-17 profile for the WinWing UFC has been developed. Its not perfect due to the differences between the F-18 UFC and JF-17 UFCP layouts, but is practical within the physical and programing limits we're dealing with. Picture attached and additional information in this thread:

JF-17 profile has be uploaded to github for approval. Thanks to prestonflying for helping me better understand string data to make this possible. I was able to correct the delays for master arm status and mode status so they now update in real time. Additionally, radio frequency will now shift based on the last radio programmed, and both comm channels are displayed. There are some peculiarities forcing the JF-17 data into a F-18 format, but I think this set up is the most logical for the constraints we have and the physical layout of the WinWIng UFC.

@Wostg Thanks for that info!

Thanks for the extra info. I'm working on FC3 profiles now (F-15, Mig-29, Su-25, etc.)... I'm not sure we'll be able to do anything beyond static data, but I'm open to suggestions with the understanding we'll probably be more limited in what we can do when compared to full fidelity modules. Also, with the FC3 planes I'm seeing an issue where the UFC will blank out when switching aircraft... like it recognizes we're in a different aircraft, but wont load the corresponding UFC data. Open to thoughts anyone may have as to why as I can swap to a full fidelity plane and not have an issue, but not back to FC3.

@DD_FriarThe instructions in the original post for the UH-60L only have two files updated, Tools.lua and uh60l_engine.lua. A third file, uh60l_Aircraft.lua also needs to be updated as it references Tools.lua... which is now uh60l_Tools.lua per the fix. Thanks again.

@DD_Friar It looks like an additional file needs to be updated for the UH-60L... uh60l_Aircraft.lua in Sounds/Sounders/Aircraft. Same changes as previously, changing tools.lua to uh60l_tools.lua Credit to @Tanuki44

Couldn't edit my post, but here is an updated prototype profile for the JF-17. Master Arm: A = Armed, S = Sim, X = Safe Mode: A = A/A, 1 = AG1, 2 = AG2 Questions from my above post remain. @Kurothas

I gave the code to the SRS team, we expect an SRS update to be pushed this weekend depending on Ciribob's schedule. For those who can't wait, the required file to update SRS is on the UH-60 discord.

Initial crack at a JF-17 profile. Generally works, although it gets "hung up" sometimes depending what is selected/changed. @prestonflying or anyone else, do you think its possible to apply a similar code for the strings as is done with number over 9 to get more characters displayed like with comm1 and comm2? It would be "squished" but I we could squeeze the JF-17's eight digits onto the WinWing display if the programing would allow... I just don't understand the string coding very well.

The UH-60L update (v1.3.2) is on the UH-60 gitnub. We're still awaiting the corresponding SRS update. All the required files are also available on the UH-60 discord.

It could be that the server side UH-60 files are causing the issue.

Thanks. I'm not sure why Rotorhead APAC results in a 200 mHz vs 225 mHz but regardless... I found a solution for the radio issue. Proposed changes have been placed on the UH-60L and SRS githubs, pending approval and release. Edit: v1.3.2 (HOTFIX) for the UH-60L is out... standing-by for the accompanying SRS update to put this behind us.

Was this on Rotorheads APAC? There has been some work to try to resolve this issue on the UH-60L discord, but I was under the impression 225 mHz was the lowest we could get the radios... see that you had an out of 200 mHz is interesting to say the least.

Just dropped some updates to the UH-60L and MH-60R files on github to correct a display error related to the AN/ARC-164 UHF radios. Edit: Also proposed some updates to the A-10C_2 and added support for the original A-10C

If someone wants to buy me the Apache I'd be willing to work on it... no guarantees of success though