prestonflying

In DCS -> Settings -> Monitor drop down menu -> Set it to 1 screen (I think that is what it is called). You can also try deleting your Saved Games/DCS.openbeta/Config/options.lua (Make a backup first, but a fresh one is created each time you boot up DCS if there is not one). Removing the options.lua will only remove graphical stuff, key binds and all other settings will stay.

Can you attach a dcs log of when you pick a plane and load into the game? This can be found under Saved Games -> DCS Folder -> Logs -> dcs.log

Are you able to click the empty spot like shown in these photos to unselect the Display ID?

Added to the project!

If @Lekaa confirms that worked I can add this updated F16 to the project repo

@Lekaa Interesting, sounds released to what Wostg brought up last week. Can you attach the logs of a cold start F16 mission with the UFC Patch files included, seeing the dcs.log file will help determine why. I do not have the F16 so I can not test, but it can help us understand what is happening.

Agreed the cold start fixes should be addressed, I will take a stab this week and try to get a clean fix added for all modules. Thanks for raising this folks!

@WostgTry going into SimApp Pro and forcing the brightness of the UFC, perhaps on cold start the message for backlight is not being properly handled (NVM this is probabaly not the case as you say it works if you hard code the values UFC Payload). Or perhaps the script is crashing if you check dcs.log. I suspect this is the issue here. It is most likely trying to access a list indication that is returning null or empty. Logs should show if this is happening I also only had Harrier on trial so I can not re-test @ANDR0IDmerged in your base profile! Updating Forum post now to include link

Bump, HP G2 with 3080 and also struggling with shimmering on straight objects like power lines, distance buildings, etc. Ill look into Negative LOD Bias as well

@Wostg I added your AH64 + F16 to the main repo! Great work

Ah, that is because for this mod/add-on to work, the export script tells SimApp Pro the user is flying an F18 (so the UFC can display data). Without this add-on, SimApp Pro can handle the lighting states for other aircraft, but for the UFC add on to work, we are limited to spoofing the current aircraft as an F18. See code here Otherwise, the ufc data would not appear. The proper fix would be for each module in this ufc add-on, to also extract the backlight values and send to SimApp Pro (I would have to test this to get it working). In addition, you could also in SimApp Pro change the backlight settings to be bound to an axis so it would work regardless of your aircraft.

Which module are you using?

Wostg suggestion is a good start, SimApp Pro will override the lua files causing the add-on to not work which is most likely what is happening. Can you DM or upload the associated dcs.log file next time this happens?

Love seeing the new work for the AH64, I do not have it personally, so if others test it out and like it I will include in the main project so others can easily use! Thanks for everyones work and contributions, glad to see this being used and expanded! Re triangle/ww update: @Lekaa SimApp Pro would be responsible for drawing the triangle on the UFC USB device, so AFAIK no change to the wwt export is needed. That said, I will do a check to see if anything new has been added recently that should be in the wwtExport.lua file that is included in this project

Hey, Wostg uploaded the A4 module. I have no personally tried it, but it has some cool features (Here is the latest release which includes it). Or is there another module you were asking about?

@Wostgsounds like a plan! Happy to pair on discord if you wanna try and tackle DED or other features. When its ready either 1. create a PR on Github, or 2. zip up the folder and direct message and ill update the project!

Hey! This is a limitation of the Winwing SimApp Pro + export scripts. By default only the F18C UFC data is shown on the WW UFC. Here is a forum post about the “Universal UFC” that allows for other modules to export any type of data to the WW UFC. Feel free to read over the post and leave a comment with the request for the Super Hornet Mod, someone or myself will work on it and get it added to the list of supported planes!

Update: Found the answer if anyone ever needs it: local camPos = LoGetCameraPosition() local position = camPos["p"] local x = position["x"] local z = position["z"] local coords = LoLoCoordinatesToGeoCoordinates(x,z); log.write("exportTest", log.INFO, coords["latitude"].." "..coords["longitude"])

Working on a project, and trying to get lat lon of the camera via lua exports. I found `LoGetCameraPosition()` and that is good; however, it exports position as meters relative to an origin lat/lon. Is there a simple and clean way to get camera positoin in lat lon without offsetting from a starting point and adding meters then converting back to lat/long (especially since DCS is a flat world and most calculations use WSG84 when adding meters to a GPS location) Thanks in advance

New Profiles added to Github Release V1.0.5 (Download from original post or visit the release and follow instructions). Shout out to @ANDR0IDfor adding EVEN more profiles. This new release includes the JF17 and TF51D. See his posts above for screenshots of the new fields for these modules.

It sounds like you are trying to fit an 8 digit alpha-numeric string EX: (1234ABCD, 12345678, AAAABBBB) onto the UFC? The only place this is do-able is the main scratch pad. If you send more information on the type of data you want to display and where on the UFC I might be able to give a more helpful answer! Nice work with the JF17 updates

Amazing thanks for PRs! All approved and I updated the release .zip file to include these changes

Attach the Saved Games/DCS/Logs/dcs.log file when it happens, the wwtExport.lua file is throwing an error I believe. The export lua tries to access aircraft values to export but throws an exception that is uncaught, thus the exports stop. This would affect anything related to export from WW. I reported this (2 months ago) to WW but they have not fixed. I have a fix in my lua file for it and can share if it’s the same issue. I have found it does not always happen, but about 40% of the time I crash/reslot my export script was stopping.

Update fixed: - Graphic settings set to VR in-game settings incase something was wrong there - Launched OpenXR in safe mode (this might have helped?)

Running latest patch with MT launching with VR (openBeta non-steam). RTX 3080, i12700KF, 64GB Ram, HP G2 OpenXR v1.2.4 Main Menu loads fine in VR, 90 FPS matches headset. Picking any mission with any aircraft yields the following. Any suggestions? null