prestonflying

I got some F15EX grips, all buttons work on my Super Taurus, even vibration on both grips. I ordered my Taurus August 2022. Perhaps some older Taurus units are not fully capable.

We could do some damage with a large dot matrix screen! If I get it, I will look into updating the repo and figuring out how the F16 ICP works

@AlphaDecayHere is a small repo that does the python script where it mocks SimApp Pro messsages https://github.com/llamaXc/winwing_ufc_custom_text I can help on discord, but you need to nullrun the python file and you can edit the contents it sends to the UFC. See the image of the example being run on the UFC and what each text window represents Launch SimApp Pro first, then run the `python main.py` script to send the UFC data message. You can custom the UFC static text in the `main.py` file, just edit the `ufc_payload` dictionary values. No super user-friendly, but can make easier to use if people end up using this. I created this just to show how it is done and an easy example to follow along

@rrutko There is a generic variable you can use, here is a code snippet. The only way to get VVI on all helicopter is to add the following code into your files locally. It could also be added to the GitHub so all users could enjoy via a Pull Request or Feature Request You can paste this into the UH-1H profile to get VVI. There is also a free slot on the UFC for the Huey which you can add it, like this inside `ufcPatch\aircraft\ufcPatchHuey.lua`. option4 = string.format('%.0f', math.floor(LoGetVerticalVelocity() * 196.85))

DCS F15E crash with log file. Here is the crash stacktrace from the dcs.log file. I will also include the whole log file. I was flying with pilot, I had a player WSO in the back. Midflight I had a CTD. Neither of us modified the laser code. Is this a known issue? 2023-10-13 00:13:25.372 INFO EDCORE (6536): # -------------- 20231013-001325 -------------- 2023-10-13 00:13:25.372 INFO EDCORE (6536): DCS/2.8.8.43704 (x86_64; MT; Windows NT 10.0.22621) 2023-10-13 00:13:25.373 INFO EDCORE (6536): C:\Users\Preston\Games\DCS World OpenBeta\bin-mt\ModelDesc.dll 2023-10-13 00:13:25.373 INFO EDCORE (6536): # C0000005 ACCESS_VIOLATION at 00007ffd6ee3f9b9 00:00000000 2023-10-13 00:13:25.374 INFO EDCORE (6536): SymInit: Symbol-SearchPath: 'C:\Users\Preston\Games\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'Preston' 2023-10-13 00:13:25.375 INFO EDCORE (6536): OS-Version: 10.0.22621 () 0x300-0x1 2023-10-13 00:13:25.378 INFO EDCORE (6536): 0x000000000001f9b9 (ModelDesc): model::ShellNode::intersect + 0x29 2023-10-13 00:13:25.378 INFO EDCORE (6536): 0x000000000001df05 (ModelDesc): model::RootNode::testWithSegment + 0x95 2023-10-13 00:13:25.378 INFO EDCORE (6536): 0x000000000003902b (NGModel): model::NGModelLodsMT::testWithSegment + 0x2FB 2023-10-13 00:13:25.379 INFO EDCORE (6536): 0x000000000000ab2d (edObjects): wShape::operator= + 0x33D 2023-10-13 00:13:25.379 INFO EDCORE (6536): 0x000000000000e420 (edObjects): Evoker<LandObjectDestroyNotifierBase,Link<LandObjectDestroyNotifierBase> >::onStartEvoke + 0xD0 2023-10-13 00:13:25.379 INFO EDCORE (6536): 0x0000000000011802 (edObjects): viSearch::TestAndInsert + 0x52 2023-10-13 00:13:25.379 INFO EDCORE (6536): 0x000000000001da28 (edObjects): DamageInfo::GetDamager + 0x15C8 2023-10-13 00:13:25.379 INFO EDCORE (6536): 0x000000000001db01 (edObjects): DamageInfo::GetDamager + 0x16A1 2023-10-13 00:13:25.380 WARNING LOG (1352): 12 duplicate message(s) skipped. 2023-10-13 00:13:25.380 INFO EDCORE (6536): 0x000000000000ba6f (edObjects): viObjectManager::GetObjects + 0x9F 2023-10-13 00:13:25.380 INFO EDCORE (6536): 0x000000000000c385 (edObjects): viObjectManager::GetSegmentList + 0x865 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x000000000000dc75 (edObjects): Evoker<LandObjectDestroyNotifierBase,Link<LandObjectDestroyNotifierBase> >::evoke + 0x245 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x000000000000dd17 (edObjects): Evoker<LandObjectDestroyNotifierBase,Link<LandObjectDestroyNotifierBase> >::evoke + 0x2E7 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x000000000037bca5 (F15E_CPT): cockpit::F15E_Systems::avF15EWeapons::l_toggle_laser_code_panel + 0x55BA5 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x000000000037b4a1 (F15E_CPT): cockpit::F15E_Systems::avF15EWeapons::l_toggle_laser_code_panel + 0x553A1 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x000000000035471c (F15E_CPT): cockpit::F15E_Systems::avF15EWeapons::l_toggle_laser_code_panel + 0x2E61C 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x0000000000354ad0 (F15E_CPT): cockpit::F15E_Systems::avF15EWeapons::l_toggle_laser_code_panel + 0x2E9D0 2023-10-13 00:13:25.381 INFO EDCORE (6536): 0x0000000000352e0f (F15E_CPT): cockpit::F15E_Systems::avF15EWeapons::l_toggle_laser_code_panel + 0x2CD0F 2023-10-13 00:13:25.382 INFO EDCORE (6536): 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 2023-10-13 00:13:25.382 INFO EDCORE (6536): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2023-10-13 00:13:25.653 INFO EDCORE (6536): Minidump created. dcs_crash_f15e_laser_code.log

Looks like its in C/Program Files x86/SimaAppPro/resources/app.asar.unpacked/Events/DefaultConfiguration/<MODULE>

Awesome write up

This looks unrelated to the wwtExport.lua file SimApp Pro uses to power the F15EX shaking I would try the following: Remove all Export.lua entries, either comment out like -- dofile, or rename the file for testing so it is not loading the export lua functions. Load into a standard instant action mission This will most likely work, then re-enable the wwtExport lua line entry in Export.lua, I suspect this will also work. This would indicate an issue with something else, most likely a mod or another lua file. And the whole log file would be great also, there is more information like which Export lua files are being loaded and might give a hint. The call stack shown appears to be related to setting clipboard text, perhaps from another mod or a custom mission. Best of luck, and report back with any findings

Hey, try attaching your log files from your Saved Games/Logs/dcs.log when you notice the crash. Might be some clues in there

@maikchaos Thanks for the ping, just uploaded the fix! It is available in release V1.0.12

There is a fix for this. The issue is in the lua file from WinWing, they do not have a null check when sending the export data. It’s a simple 2 line fix here is a more detailed post with a fix if you want to try it. I have submitted to winwing but no update was added for it

@maikchaos your log file helps, this is happening because the harrier displays are turned off then the export script fails to find data when the jet is turned off. I can get a fix out for this later this tomorrow and will post back when it’s fixed.

@AlphaDecay if you want to use the UFC standalone from DCS you have 2 options. 1. write a script spoofs SimApp Pro messages from DCS to set some default text. Example, SimApp pro listens for a start message, then an aircraft message, then the export lua sends the ufc payload like in my GitHub project. 2. write a program described in this post that mimics SimApp pro and writes straight to the UFC HID Device if I have time later this week I can update my GitHub project to include a python script that mocks the messages so SimApp Pro sets the ufc device text properly

Have an ability I am looking to implement a feature. I have used lua within DCS but only for export scripts. I am try to re-slot a player in a multiplayer server (I am server owner) during certain triggers. Similar to `lshift + R` in a single player mission (mission restart). Is this a capability MIST or DCS can do natively? If not, any related tools that could help with this?

New to dcs mission scripting, not new to programming. Looking for tips to automatically re-slot the player upon death into a new fresh aircraft. Has anyone done something similar? If you know of related functions or methods to achieve please leave a comment! Thanks

Greetings, trying to figure out the best solution for this crash. Anyone else getting crashes with latest NVIDA drivers? 2023-07-12 00:11:20.509 INFO DX11BACKEND (6784): NVIDIA Display Driver Version 53640.r536_08 ... 2023-07-12 00:11:27.772 INFO APP (Main): gDescription: "NVIDIA GeForce RTX 3070" gVendorId: 4318 gDeviceId: 9348 gMemory: 8031 MB ... Flying for 2+ hours ... 2023-07-12 02:55:20.861 INFO EDCORE (4564): try to write dump information 2023-07-12 02:55:20.864 INFO EDCORE (4564): # -------------- 20230712-025521 -------------- 2023-07-12 02:55:20.864 INFO EDCORE (4564): DCS/2.8.6.41363 (x86_64; MT; Windows NT 10.0.22621) 2023-07-12 02:55:20.865 INFO EDCORE (4564): C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5b6e4554b945d508\nvwgf2umx.dll 2023-07-12 02:55:20.866 INFO EDCORE (4564): # C0000005 ACCESS_VIOLATION at 00007fffa4885559 00:00000000 2023-07-12 02:55:20.867 INFO EDCORE (4564): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'SAVVAS' 2023-07-12 02:55:20.867 INFO EDCORE (4564): OS-Version: 10.0.22621 () 0x300-0x1 2023-07-12 02:55:20.868 INFO EDCORE (4564): 0x00000000001d5559 (nvwgf2umx): NVENCODEAPI_Thunk + 0x5EB09 2023-07-12 02:55:20.868 INFO EDCORE (4564): 0x000000000155f62f (nvwgf2umx): NVAPI_Thunk + 0x11FFE7F 2023-07-12 02:55:20.869 INFO EDCORE (4564): 0x000000000155f58f (nvwgf2umx): NVAPI_Thunk + 0x11FFDDF 2023-07-12 02:55:20.869 INFO EDCORE (4564): 0x000000000155443d (nvwgf2umx): NVAPI_Thunk + 0x11F4C8D 2023-07-12 02:55:20.869 INFO EDCORE (4564): 0x0000000000573eba (nvwgf2umx): NVAPI_Thunk + 0x21470A 2023-07-12 02:55:20.869 INFO EDCORE (4564): 0x0000000001da822e (nvwgf2umx): OpenAdapter12 + 0x66AABE 2023-07-12 02:55:20.869 INFO EDCORE (4564): 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D 2023-07-12 02:55:22.786 INFO EDCORE (4564): Minidump created. 2023-07-12 02:55:22.786 INFO Lua::Config (4564): stack traceback: 2023-07-12 02:55:22.795 WARNING LOG (3628): 3 duplicate message(s) skipped.

Increasing page file size and getting 64 gb of ram fixed it. Done dozens of flights no issues!

@Kurothas SimApp Pro will make a fresh Export.lua and also makes a backup file, look for Export_Backup_xyz and you can grab the old tac view lua entry and add it back into Exports.lua Here is the lua entry for TacView assuming you had TacView installed and working which should make it work again local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

@Wostg I had a similar idea when starting this, turns out SimApp Pro is our interface to the USB UFC scratch pad, thus we send data to SimApp Pro, then SimApp Pro sends data to the UFC. SimApp Pro does not support letters, thus nothing would show. I have another forum post that shows how to bypass SimApp Pro and directly write data to the UFC. This approach would be required to get full control over the segmented displays, and would require a re-work of how this UFC Patch program works. In pseudo code; we would make a new program that reads export dcs data, then writes to the UFC directly, skipping SimApp Pro altogether. I do not think it is worth the work, but is always possible!

@Wostg @Lekaa F-15E Has been added to latest version (1.0.11)! Thank you for helping create this profile and test it!

@Kurothas hey there! Let’s first just try to get your dcs exports working, then we can re install the UFC edited files. 1. Can you confirm your Saved Games/DCS_Folder/Scripts/Export.lua includes the wwt lines? You can run “repair lua” in SimApp Pro -> setting to repopulate those. Perhaps the upgrade removed the old entries. 2. Start up DCS after confirming your Export.lua has the lines. Do you see any errors in your dcs.log file?

I’ll check out bios and see about hyper threading and try out ST. I have 32gb ram but have 64GB on the way, hopefully that plus larger page file size helps

I was flying the Raven One Dominate Fury campaign mission 4, as I hit quit from the in-game menu my game crashed. Here is the error log. I have been having a string of crashes but unsure if it is the campaign mission or something else. Log: attached dcs.log

From the sounds of your post, it seems you have narrowed it down to SimApp Pro being open. A few things you could try: 1. Update SimApp Pro? 2. Run as administrator? 3. Open up windows "set up usb game controllers" and see if your stick events are detected in real-time there (no input lag) 4. Could try updating the firmware on the winwing devices (read up on this as it can be tricky sometimes) 5. Could try commenting out the winwing lua script in Saved Games/DCS/Scripts/Export.lua (add a -- to comment out a line or just delete it) to see if the export is causing it. I doubt this is the issue as it sounds like SimApp Pro is what you detected being the problem.

Dang this is odd! Try cleaning then repairing DCS, also update DCS if you havent already. You could try launching ST VR vs MT VR? There is a VR forum that might be able to help more in depth