Heads up on SIMAPPPRO setting change (causing performance impact)

[rob10]

Those that have had WinWing for a while will remember back to when running SimAppPro had a significant performance hit.  Then a user discovered there was a setting in the wwtExport.lua file in the Saved Games/Scripts/WWT file that was causing it to poll the controls at about 100 fps.  They changed it eventually to 1.0 which solved a lot of the issues.

Somewhere one of the recent updates it seems that it got changed back to 0.03 AND the setting for it to NOT change this file no longer works.  Set it to READ ONLY and it will stop it from changing back each time you re-launch SimAppPro

EDIT: see this post for a workaround on it changing on re-launch without going read only:

I discovered all this because my performance on the deck on the carrier had got crappy.

Edited July 22, 2024 by rob10
added new information

[Wostg]

Will check it out - have edited the backup file in \SimAppPro\resources\app.asar.unpacked\Events\wwt as well

[mkel2010]

@rob10  Is this the line in the lua file you're talking about (Line 19?)

_winwing.interval=0.03

Edited July 21, 2024 by mkel2010

[rob10]

9 minutes ago, mkel2010 said:

@rob10  Is this the line in the lua file you're talking about (Line 19?)

_winwing.interval=0.03

Yes.

For those who are interested, here is a link to the original (and detailed) post that includes this (note that it was at line 18 (rather than the current 19) at the time):

 

Edited July 21, 2024 by rob10

[mkel2010]

4 hours ago, rob10 said:

Yes.

For those who are interested, here is a link to the original (and detailed) post that includes this (note that it was at line 18 (rather than the current 19) at the time):

 

 

Thanks for the link. 

I would caution against making the file read only, however. You never know what other changes might be made during subsequent updates that could cause unforeseen issues. This may be one of those things that will need to be manually changed with each update.

[rob10]

5 hours ago, mkel2010 said:

I would caution against making the file read only, however. You never know what other changes might be made during subsequent updates that could cause unforeseen issues. This may be one of those things that will need to be manually changed with each update.

I agree with that sentiment, but the problem is that it changes that value back each time you RUN SimAppPro, not each time it's updated .  There is a check box in the settings that used to stop it from changing that file, but it no longer seems to be working (although I haven't tried unchecking and rechecking it to see if that makes it work again).  I wouldn't have read only'ed it if the checkbox was still working.

[Wostg]

Also edit the 'master backup' in the \SimAppPro\resources\app.asar.unpacked\Events\wwt folder and it will copy from there, so you won't have to make it read only. That should last at least until you next update SAP. (thanks Preston)

[rob10]

18 hours ago, Wostg said:

Also edit the 'master backup' in the \SimAppPro\resources\app.asar.unpacked\Events\wwt folder and it will copy from there, so you won't have to make it read only. That should last at least until you next update SAP. (thanks Preston)

Thanks for that.  I didn't really dig back through the post so I didn't catch that.

[Canada_Moose]

I changed this as discussed in this thread but now the inputs onto the keypad are delayed along with many other button presses. Not sure the value of 1.0 is good based on my experience

[MustangSally]

Haven't seen any performance impact all.

[rob10]

2 hours ago, Canada_Moose said:

I changed this as discussed in this thread but now the inputs onto the keypad are delayed along with many other button presses. Not sure the value of 1.0 is good based on my experience

1.0 isn't really a magic number.  I'd start lowering it until you get the results you're looking for.

[Dunska]

I've been setting this to 0.1 for a long time by editing the master wwtExport.lua file in the \SimAppPro\resources\app.asar.unpacked\Events\wwt folder.