honanhal Posted September 24, 2017 Report Share Posted September 24, 2017 I'm sure I'm doing something very simple wrong here, but I've tried to follow both the FSUIPC manual and what I've found online from people using P3D. Never had any problems with FSX. The extra files never get culled -- they keep building up. [AutoSave] Next=2 Interval=600 Files=3 SaveOnGround=No AutoSaveEnabled=Yes AlsoManage1=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.0.rte AlsoManage2=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.1.rte AlsoManage3=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.2.rte AlsoManage4=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.fxml.fmc AlsoManage5=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.fxml.sav AlsoManage6=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\*.fxml.0.rte AlsoManage7=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\*.fxml.1.rte AlsoManage8=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\*.fxml.2.rte AlsoManage9=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\*.fxml.fmc AlsoManage10=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\*.fxml.sav AlsoManage11=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.0.rte AlsoManage12=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.1.rte AlsoManage13=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.2.rte AlsoManage14=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.fmc AlsoManage15=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.sav 1=Sun 155203 2=Sat 221713 3=Sat 222713 Appreciate any help! Thanks, James Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 25, 2017 Report Share Posted September 25, 2017 12 hours ago, honanhal said: I'm sure I'm doing something very simple wrong here, but I've tried to follow both the FSUIPC manual and what I've found online from people using P3D. Never had any problems with FSX. The extra files never get culled -- they keep building up. The code is identical in FSUIPC5 to that in FSUIPC4, but maybe there's a 32-64 bit difference I've missed. I'll have to do some tests here. Do those AlsoManage lines work okay in FSUIPC4? I'm wondering if you need "" around the complete path, because of the spaces in the folder names. (FSUIPC doesn't process INI lines directly, it uses a standard Windows function). I'll come back to this when I've done some tests myself. Meanwhile can you confirm that you are using the latest version, 5.121a? I don't want to waste time if it is something fixed by a recent change. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 25, 2017 Report Share Posted September 25, 2017 I've tested this here with FSUIPC 5.121a, and i cannot make it go wrong. It deletes the files it is supposed to every time. Pete Link to comment Share on other sites More sharing options...
honanhal Posted September 26, 2017 Author Report Share Posted September 26, 2017 Pete, Just checked, and I had been on a slightly earlier version of FSUIPC5, but I just installed the latest version. No difference -- it's still not deleting the files. No idea if the AlsoManage lines work in FSUIPC4, unfortunately. I went straight from FSX to P3D last month and FSUIPC5 is the first version I'm using with P3D. Can you clarify a bit where exactly I'd put the quotemarks around the complete path, in case that's the issue? e.g. is it AlsoManage1="C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.0.rte" Thanks, James Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 26, 2017 Report Share Posted September 26, 2017 7 hours ago, honanhal said: Can you clarify a bit where exactly I'd put the quotemarks around the complete path, in case that's the issue? e.g. is it AlsoManage1="C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\*.0.rte" Yes, it would be. But I tried without quotes and it did work here. Can you double check that the pathname is exactly right too? I've added some extra AutoSave logging. Download this: FSUIPC5.121b. Copy the DLL into the Modules folder, and edit the FSUIPC5.INI file, adding: Debug=Please LogExtras=4 to the [General] section. This will make FSUIPC log each autosave and the deletions, with an error number if the latter fail. Pete Link to comment Share on other sites More sharing options...
honanhal Posted September 27, 2017 Author Report Share Posted September 27, 2017 Pete, Just installed the updated module and tested it. Here's the relevant part of the log file (I was flying the NGX): 631016 Autosave started: next file entry 0 631016 Autosave: deleting "C:\Users\James\Documents\Prepar3D v4 Files\AutoSave Sun 203950" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 631016 *** ERROR: Autosave couldn't delete "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" (error 1) 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" 631016 *** ERROR: Autosave couldn't delete "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" (error 1) 631016 *** ERROR: Autosave couldn't delete "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" (error 1) 631016 ... Autosave finished 1230516 Autosave started: next file entry 1 1230516 Autosave: deleting "C:\Users\James\Documents\Prepar3D v4 Files\AutoSave Sun 204950" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 777X\PanelState\" 1230516 *** ERROR: Autosave couldn't delete "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" (error 1) 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" 1230516 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" 1230516 *** ERROR: Autosave couldn't delete "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" (error 1) 1230516 *** ERROR: Autosave couldn't delete "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\" (error 1) 1230516 ... Autosave finished Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 27, 2017 Report Share Posted September 27, 2017 6 hours ago, honanhal said: Just installed the updated module and tested it. Here's the relevant part of the log file (I was flying the NGX): Oops! I made a silly error in the logging I'm afraid, so it isn't as informative as it should be. This log line is correct: 631016 Autosave: deleting "C:\Users\James\Documents\Prepar3D v4 Files\AutoSave Sun 203950"The .FXML and .WX parts aren't included in the log line, but this log line is certainly wrong: 631016 Autosave: deleting "C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 747 QOTS II\PanelState\" It should have the the full filename. I'll fix that now so we get proper logging. I'll also fix it so that it doesn't log an error line for the 5 x 747 deletions, plus 5 x 777 deletions, when those files won't exist in any case when using the 737. However, though I can't tell precisely from the log which files were deleted okay and which not, in your INI you have 5 files referenced for the 737. The log (which because of my error is showing error 1 for good deletions and no error for deletion failed or file not present) seems to indicate that those I've highlighted here in RED were, in fact, deleted okay: AlsoManage11=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.0.rteAlsoManage12=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.1.rteAlsoManage13=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.2.rteAlsoManage14=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.fmcAlsoManage15=C:\Lockheed Martin\Prepar3D v4\PMDG\PMDG 737 NGX\PanelState\*.fxml.sav Are they ALL actually generated each time, or only those three of them? Please clarify. What files are NOT being deleted? If those were the only three generated, and they are NOT being deleted, then I can only think it is because FSUIPC cannot access that folder for deletions. But in that case it should get an error saying access denied. Anyway, for clarity in the logging, fixing my stupod (hurried) mods, please download this and replace the DLL and run the test again. I've not changed the version number or date in the file, so please destroy the previous one to avoid any confusion. FSUIPC5121b2.zip Regards Pete Link to comment Share on other sites More sharing options...
honanhal Posted September 28, 2017 Author Report Share Posted September 28, 2017 Pete, apologies -- I see now that it's correctly deleting new files as it goes, but that it wasn't culling older autosaves from before when I put the "alsomanage" lines in. Sorry to waste your time! I've manually deleted the old files, and it should be good to go from here on in. Thanks again, James Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 28, 2017 Report Share Posted September 28, 2017 5 hours ago, honanhal said: I see now that it's correctly deleting new files as it goes, but that it wasn't culling older autosaves from before when I put the "alsomanage" lines in Ah, that explains why I couldn't reproduce it here! ;-) Pete Link to comment Share on other sites More sharing options...
d809dp Posted December 13, 2018 Report Share Posted December 13, 2018 Hi There, Can I also ask for some help? Here's the text from my .ini file... all addons are being well managed, apart from QualityWIngs... any ideas? THanks, Tom [AutoSave] Next=2 Interval=15 Files=2 SaveOnGround=Yes AutoSaveEnabled=Yes 1=Thu 070436 2=Thu 070422 3=Mon 202840 4=Mon 204020 5=Mon 205159 6=Tue 214007 7=Tue 214106 8=Tue 214206 9=Tue 214305 10=Tue 214405 AlsoManage1=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.sav AlsoManage2=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.1.rte AlsoManage3=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.fmc AlsoManage4=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.efb0 AlsoManage5=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.efb1 AlsoManage6=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.4.rte AlsoManage7=D:\Tom\Documents\Prepar3D v4 Add-ons\FSLabs\A320\PanelState\*.fxml.sav AlsoManage8=D:\Tom\Documents\Prepar3D v4 Add-ons\FSLabs\A320\PanelState\*.fxml.xml AlsoManage9=D:\Tom\Documents\Prepar3D v4 Add-ons\FSLabs\A320\PanelState\*.fxml.FM1 AlsoManage10=D:\Tom\Documents\Prepar3D v4 Add-ons\FSLabs\A320\PanelState\*.fxml.FM2 AlsoManage11=QualityWings\QW787\PanelStates\*.PNL AlsoManage12=PMDG\PMDG 747 QOTS II\PanelState\*.fxml.0.rte Link to comment Share on other sites More sharing options...
John Dowson Posted December 13, 2018 Report Share Posted December 13, 2018 Hi, what files are not being deleted? Try adding the additional logging flags to your FSUIPC5.ini file, as mentioned above: Quote Debug=Please LogExtras=4 Cheers, John Link to comment Share on other sites More sharing options...
d809dp Posted December 13, 2018 Report Share Posted December 13, 2018 Hi there... does any of this help you? The file which is not being deleted is the quality wings panel state file. "Also manage number 11". Thanks, Tom 0 System time = 13/12/2018 20:41:11 0 FLT path = "D:\Tom\Documents\Prepar3D v4 Files\" 0 Using DialogMode 16 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v4\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= Saitek X52 Flight Control System 94 Manufacturer= Saitek 94 Vendor=06A3, Product=075C (Version 1.16) 94 GUIDs returned for product: VID_06A3&PID_075C: 94 GUID= {1F008440-786F-11E7-8008-444553540000} 94 Details: Btns=34, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X2047,Y2047,Z255 94 ------------------------------------------------------------------- 110 Device acquired for use: 110 Joystick ID = 0 (Registry okay) 110 0=X52 H.O.T.A.S. 110 0.GUID={1F008440-786F-11E7-8008-444553540000} 110 ------------------------------------------------------------------- 110 LogOptions=00000000 00000051 110 ------------------------------------------------------------------- 110 SimConnect_Open succeeded: waiting to check version okay 110 Opened separate AI Traffic client okay 10516 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 11375 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0) 11375 Initialising SimConnect data requests now 11375 FSUIPC Menu entry added 11375 ... Using Prepar3D with Professional License 11391 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 11407 C:\Users\Tom\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 11407 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 11610 Deactivated for PID=12300, "VATSpy.exe" 30110 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\QualityWings 787-9\Boeing 787-9 RR.air 81829 Loading Complete ... 82891 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 82891 Aircraft loaded: running normally now ... 82969 User Aircraft ID 2 supplied, now being used 83391 System time = 13/12/2018 20:42:35, Simulator time = 20:41:24 (04:41Z) 83391 Aircraft="QualityWings 787-9 Virgin Atlantic Airways -SATCOM" 85079 Deactivated for PID=6880, "explorer.exe" 85079 Lost focus to PID=6880, "explorer.exe" 90344 -------------------- Starting everything now ---------------------- 90344 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 90391 ASN active function link set 90391 Ready for ActiveSky WX radar with additional data 91250 Deactivated for PID=8624, "PFPX.exe" 91250 Lost focus to PID=8624, "PFPX.exe" 93016 Weather Mode now = Theme 93688 Advanced Weather Interface Enabled 99594 Autosave started: next file entry 1 99594 Autosave: deleting "D:\Tom\Documents\Prepar3D v4 Files\AutoSave Thu 204030" 99594 ... Autosave finished 108266 Deactivated for PID=6880, "explorer.exe" 108282 Lost focus to PID=6880, "explorer.exe" 108344 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 108344 Sim stopped: average frame rate for last 25 secs = 31.2 fps 108344 Max AI traffic was 0 aircraft 108860 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 109094 Autosave started: next file entry 0 109094 Autosave: deleting "D:\Tom\Documents\Prepar3D v4 Files\AutoSave Thu 204040" 109110 ... Autosave finished 112079 Deactivated: culprit unknown 112079 Focus lost: culprit unknown 118594 Autosave started: next file entry 1 118594 Autosave: deleting "D:\Tom\Documents\Prepar3D v4 Files\AutoSave Thu 204251" 118594 ... Autosave finished 128172 Autosave started: next file entry 0 128172 Autosave: deleting "D:\Tom\Documents\Prepar3D v4 Files\AutoSave Thu 204300" 128172 ... Autosave finished 133985 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 133985 Sim stopped: average frame rate for last 25 secs = 33.4 fps 133985 Max AI traffic was 0 aircraft 134954 === Closing session: waiting for DLLStop to be called ... 145907 === DLLStop called ... 145907 === Closing external processes we started ... 146907 === About to kill any Lua plug-ins still running ... 147063 === Closing global Lua thread 148079 === About to kill my timers ... 148266 === Restoring window procs ... 148266 === Unloading libraries ... 148266 === stopping other threads ... 148266 === ... Button scanning ... 148375 === ... Axis scanning ... 148469 === Releasing joystick devices ... 148469 === Freeing macro memory 148469 === Removing any offset overrides 148469 === Clearing any displays left 148469 === NOTE: not calling SimConnect_Close ... 148469 === AI slots deleted! 148469 === Freeing button memory ... 148469 === Deleting wxstationlist.bin file ... 148469 === Closing my Windows ... 148469 === Freeing FS libraries ... 149469 === Closing devices ... 149469 === Closing the Log ... Bye Bye! ... 149469 System time = 13/12/2018 20:43:41, Simulator time = 20:43:24 (04:43Z) 149469 *** FSUIPC log file being closed Minimum frame rate was 29.3 fps, Maximum was 35.0 fps Average frame rate for running time of 50 secs = 32.3 fps Maximum AI traffic for session was 0 aircraft Memory managed: 23 Allocs, 22 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 13, 2018 Report Share Posted December 13, 2018 Hi, As John asked, "what files are not being deleted?"? Although your thread title sweepingly states "AlsoManage not working ...", are you reallly sating "Alsomanage isn't working for this one add-on aircraft"?, because you seem to have quote a few AlsoManage entries. Do i assume this is the entry which you say doesn't work? AlsoManage11=QualityWings\QW787\PanelStates\*.PNL Do you think you could actually list the files which you think should be deleted and which were not. If there's a lot, just give a batch please. The LOG file, with the settings John gave you, would have listed an error if the deletion failed, which it doesn't, which makes me think you are really talking about some variations not covered by the *.PNL template, where the * is replaced by the usual "AutoSave Thu 204040" type of naming which is what Autosave generates (obviously with different days and times). Pete Link to comment Share on other sites More sharing options...
d809dp Posted December 14, 2018 Report Share Posted December 14, 2018 Hi Pete, Not actually my title, I'm afraid. What I am saying is that this file, AUTOSAVE FRI 073515-FLT.PNL, in this directory, C:\Program Files\Lockheed Martin\Prepar3D v4\QualityWings\QW787\PanelStates is not being deleted. It's only one file, but it doesn't seem to be deleted. I think you're thinking along the right lines. I suspect the error is in the instruction I've created in the .ini file, but I'm not sure what it is. Thanks, Tom Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 14, 2018 Report Share Posted December 14, 2018 3 hours ago, d809dp said: What I am saying is that this file, AUTOSAVE FRI 073515-FLT.PNL, in this directory, C:\Program Files\Lockheed Martin\Prepar3D v4\QualityWings\QW787\PanelStates is not being deleted. It's only one file, but it doesn't seem to be deleted. Aha! This is what you should have said in the first place! 😉 It isn't just "*.PNL", it is *-FLT.PNL" you need! The Autosave only fills in the AUTOSAVE FRI 073515 part. It cannot guess the bit you missed out! Pete Link to comment Share on other sites More sharing options...
d809dp Posted December 14, 2018 Report Share Posted December 14, 2018 Hi Pete. That's great - working like a dream - just like it says on the tin. I didn't realise how much of the file name was addon-specific. Maybe the (excellent) documentation could be added to on this point? But again - thanks for your help - that's great support. Cheers, Tom Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now