Tom68

Just to close the loop for those in the future who may be having the same issue. I believe John's solution to be correct. The problem has not re-occurred in about 20 flights. And I see no ill side effects due to the changes.

Thanks for the help.

OK, the WASM did indeed crash. I’ve made the changes you suggested. What are the implications of the scan frequency change? It seems like it would mean any aircraft type change would require restarting MSFS, true? For the scan delay, the manual says “the delay in seconds between when the Ready To Fly stage is reached and the initial scan for lvars is performed”. When does the “initial scan” take place? When I select the aircraft type, or when I select “fly” from the world map, or when I select “Ready to Fly”? I ask because the A2A Comanche, when it loads, has a delay after selecting “Ready to Fly”. You can see that with the tablet of the aircraft open. There’s a progress bar that takes about 10 seconds to complete. The A2A explanation is that the sound is loading. So I’m asking is the 10 seconds enough? Or is this a question for A2A? Finally, I won’t know if this solves the problem for a few days, since this occurrence seems random. When I feel comfortable that its resolved, I'll reply to this thread just for others in the future who may have the same issue. Thanks Tom

I found it. The manual says its in the community folder, but its not. C:\Users\TomS\AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work Is the manual in error or is there something wrong with my installation?

I don't seem to have the log. I've got a Steam install. C:\Users\TomS\AppData\Roaming\Microsoft Flight Simulator\Packages\Community\fsuipc-lvar-module There is no "work" directory as the user guide says. Could this be a clue? I have WASM enbled, I checked that in FSUIPC add on tab. Here's my FSUIPC_WASM.ini file: [General] ; LogLevel: Disable, Info, Debug, Trace LogLevel=Info ; LogType: File, Console, Both LogType=File ; LvarUpdateFrequency: frequency to update internal lvar values list and set in CDA ; Accept values: Off, 6Hz, Second, VisualFrame. If using 'Off', update timer must be active in a client LvarUpdateFrequency=6Hz ;LvarScanFrequency: the frequency of scans to detect new lvars ; - positive numbers indicate maximum number of scans per second ; - negative numbers indicate minimum number of seconds between scans ;Values for this parameter are constrained to between -30 and +4 ;A value of 0 will disable scanning for new lvars LvarScanFrequency=-2 ;LvarScanPeriod: the period (in minutes), starting from aircraft load, when lvar scans will be performed ;Values for this parameter must be positive LvarScanPeriod=10 ;LvarScanDelay: the delay in seconds between when the Ready To Fly stage is reached and the initial scan for lvars is performed ;It is recommended to increase this if using complex aircraft or airliners as it can take a while for some lvars to be created ;for such aircraft. ;Note that lvars created after the initial scan will be found and pushed to clients if the LvarScanFrequency is non-zero. LvarScanDelay=5

Thanks for your response. I'll give those ideas a try.

I think this may be a FSUIPC problem, but I’m not sure. Any ideas on how I can narrow this down will be greatly appreciated. MSFS 2020 and FSUIPC7, Saitek Yoke, and 2 throttle quadrants, Thrustmaster rudder pedals. 2 DIY panels of switches and axes made from an Arduino micro and a Leo Bodnar BU0836A and setup as joysticks. 90% of the time everything works fine. 10% certain switches stop working. The failed ones are all LVARs that I’ve used macros to operate. When they cease working, while still in the cockpit, I open the FSUIPC window and I can see it recognizes if I actuate the failed switches. I can also see them in the FSUIPC log while in the failed state. Windows control panel also shows the switches working. It happens to all aircraft I try. However, I’ve only tried 5. Also note, other switches within the same panel that do not use macros continue to work. I’ve included a few excerpts from my profile for the A2A Comanche 250 to help see what I’m doing. Also, I've been thru this with A2A as I first thought it was just the Comanche. Primer and landing gear both fail. Comanche macro: 5=L:PrimerScrew=SET 6=L:PrimerState=INC ; parameter 2 7=L:PrimerState=SET ; parameter 0 10=L:LandingGearLeverPos=SET Comanche ini 309=PH,20,CM3:6,2 -{Macro 2-Camanche250: L:PrimerState inc}- 310=PH,19,CM3:7,0 -{Macro 2-Camanche250: L:PrimerState set}- 312=PA,30,CM3:10,0 -{Macro 2-Camanche250: L:LandingGearLeverPos set}- 313=UA,30,CM3:10,1 -{Macro 2-Camanche250: L:LandingGearLeverPos set}- 314=PA,24,CM3:10,2 -{Macro 2-Camanche250: L:LandingGearLeverPos set}- 315=UA,24,CM3:10,1 -{Macro 2-Camanche250: L:LandingGearLeverPos set}- Thanks.

John, Sorry about creating the other thread, I thought I was doing the right thing. I felt the new question I was asking was more general about presets even though it had to do with the Duckworks DC3. And it would be more clear to anyone reading the post for help in the future. Sorry. However, I thought I was following exactly the thread you pointed me to. I do want to divide by 32767 and add 0.5. My quadrant generates -16382 to +16384. The Duckworks preset wants 0.0 to 1.0. Divide by 32767 gives -0.5 ro +0.5. Adding 0.5 gives 0.0 to 1.0. Exactly what was in the post you pointed me toward. I directly copied what was there. So what am I misunderstanding?

Ok, I'm about out of ideas to try. I'm doing something wrong and can't figure it out. I've searched and read a number of posts on the topic. I've read the manuals as well. Here's what I am doing: Two Siatek throttle quadrants (joys B & C). MSFS2020. I created myevents.txt and add the following two lines: DuckWorks_DC3_Throttle1#@ 32767.0 / 0.5 + (>L:DUCKWORKS_THROTTLE1_SET) DuckWorks_DC3_Throttle2#@ 32767.0 / 0.5 + (>L:DUCKWORKS_THROTTLE2_SET) I assign the axes by checking "Send to FS as normal axis", and "Select for Preset". The I click the dropdown box and select my preset. Finally I calibrate a single range from -16384 to +16384. It just doesn't work. I see some curious lines in my DC3 profile ini file. 2=BZ,256 3=BZ,B,-16384,16383,PDuckWorks_DC3_Throttle1,0 -{ Entering=Preset Control }- 4=CX,256 5=CX,B,-16384,16383,PDuckWorks_DC3_Throttle2,0 -{ Entering=Preset Control }- I have no idea what lines 2 & 4 are. I tried deleting them and FSUIPC just puts them back Any ideas on what I'm doing wrong? (I attached some docs to help define what I'm doing.) Thanks in advance. DC3-A.ini myevents.txt FSUIPC7.ini

John, Thanks much for the quick response. Yes, I'm using the Duckworks DC3. So, I'll look at that thread you pointed me to. Tom

FSUIPC 7, Windows 10, MSFS 2020. Question: When clicking on Assignments -> Axes, “Profile Specific” is always checked and its grayed out so it cannot be changed. How can I assign an axis for all planes? Question: ExcludeThrottleSet. The manual says “Only disable this option if you have anything which is feeding…”. Sorry, but I’m confused by the wording: Since the option is excluding something, does “disable this option” mean checked or unchecked for the normal situation? Issue: I’m not sure if this is FSUIPC or MSFS. I’m trying to assign my two Saitek throttle quads to props, throttle, mixture for the DC3. The props work fine. Throttles and mixtures do not. Throttle 1 did work a single time, but then stopped. They all when assigned thru MSFS. I had programed both props and they worked. I then programmed the throttle 1 and it worked, but the two props stopped. I reprogrammed the two props and they again worked, but the throttle would no longer work. I can program them for the C172 and Beechcraft G58. Things seem to program OK, (I can assign them and the numbers move in the calibration tab), but they just don’t work in the plane. Oh, and I’m using profiles. IS it possible this is FSUIPC? Or something in the DC3? (I've attached my DC3 profile and FSUIPC.ini) Thanks. DC3-A.ini FSUIPC7.ini

After installing the trial version and working with it, it works good (just as it did in FSX, Yea!). I upgraded to 7 on simMarket. I was sent an email with links, but they don't lead to the license key. How do I acquire it (I assume all I now need is the key since I've already got it installed)? Thanks.

OK, I've updated my email and login on simMarket. The October expiration gives me enough time to evaluate FSUIPC7. Please PM the key to me. Thanks.

Sorry, 2 more questions. Where do I get the trial license? I downloaded the "demo" from simMarket and installed. My FSUIPC 4 license was registered to an email address I no longer have access to. How should I handle this when I purchase?

FSUIPC 4 user for years with FSX. I've recently upgraded to msfs 2020. I'd like to try FSUIPC 7. Is there a discount for upgrading from 4 to 7? How long is the free trial (I won't have time to try it for 4-5 days)? Thanks.