Hi gang,I just got ###### about the fact that I haven't been able to save my panel status anymore with the v1.3 patch (the external HW patch, that has something else as well...).I found a solution to the problem. It isn't that beautiful but at least it works.You have to use the older APS.DLL from the ORIGINAL FS2002 patch when saving flights. With the older module it WILL save the flight correctly with the panel status as well! After you have saved all the flights you need, just put the newer version back in again, and you are set!Step by step (if you have v1.3 patch installed!):1. Take a back-up from your current APS.DLL inside the FS2002MODULES (file is 560kB, date Jul 22nd 2002)2. Extract the original FS2002 patch to a temporary directory3. Copy the APS.DLL (544kB, date Feb 4th 2002) inside that patch, from the temporary directory, under "MODULES", to your X:FS2002MODULES and overwrite the existing version there.4. Start FS2002 and save all the flights & panel status you need (for example a correct panel status for a REAL cold & dark, real line operations never have a panel status that has EVERYTHING turned off, for example the L&R PRIM HYD pumps are always on, to name one :))5. Exit FS2002 and put your back-up copy of the newer APS.DLL back into X:FS2002MODULES, ie. overwrite the older version that you copied there before.Done.Tero

Tero,Kiitos!Will try this workaround tonight. If it works, I'll buy you a beer next time I'm in Helsinki! Kind regards,Stephan Haashttp://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg

Hi Tero,>I just got ###### about the fact that I haven't been able to>save my panel status anymore with the v1.3 patch (the external>HW patch, that has something else as well...).I'm still not sure you should blame the v1.3 patch, because I have no problems saving my panel state, and I do have 1.3...!!!!I used to have the same problems like you, and I think I found the following work around (though I'm not sure):1. Take your preferred position at a gate;2. Load a 'fresh' panel e.g. '767 PIC Engine Start' from PIC-->Panel-->Load a panel from a flight...3. Adapt your panel to your liking4. Save the panel.Reload the saved flight and check whether it worked or not.It's also a mystery for me why it goes fine here, and not with you or others. I really don't know all the answers, but IMHO patch 1.3 should not be condemned without evidence...Regards,Nicowww.nicokaan.nl

Nico,Very interesting.I have tried everything in my power, and then I noticed that the particular DLL is something that is updated in the v1.3 installation. I replaced that with the old FS2002 patch version, and was again able to save the panel status! Hence the reasoning behind that one...Nico, could you tell me the date and size of your APS.DLL ? Just out of curiosity... my "workaround" has been the only way for me to save panels so far. I might try your suggestion at some point though, so thanks for that!Tero

I want to add something to avoid confusion: After my 4 step procedure my 'FS2002/PIC767 state' was back to normal and I could save other flights directly, starting from the correct one and moving to other airports and slewing to the gate.And I forgot to say that you're work around is also a very good addition to our PIC/Aerosoft MCP addicts..;-)Nico

Tero,I have APS.DLL 560Kb 20-7-2002 in my Modules directory.Also I found out that the only file that has been changed by the 1.3 patch is B767WAfds.gau, size 1848Kb, date 20-7-2002Sounds logical, because the MCP is part of the Autopilot Flight Director System, and they had to patch that in order to communicate with the MCP hardware (Good work by the way, we have to thank them for that again.!!.). I also do not see why the patch would interfere with panel state saving....Nico

I also don't have a problem doing it Nico's way - panel is saved. I will also recheck this issue.

Tero, Nico,OK, here goes:Tried the Tero workaround, no luckTried the Nico workaround: no luck(and no, the combo didn't work either)When trying to load a panel state from a saved flight it only offers a few options (mostly the original flights). Most of my own saved flight don't come into view in this menu (they do in the flight loading menu).I tend to agree with Nico that it's not a patch 1.3 problem but something else. I'll leave it for now. later this year when I migrate to a new flightcomputer I'll do a new install and see what that brings.Kind regards,Stephan Haashttp://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg

Stephan,bump>It's also a mystery for me why it goes fine here, >and not with you or others. >I really don't know all the answers, but IMHO patch 1.3 should not >be condemned without evidence...Let's offer some money for the guy who comes up with the real solution. ;-) ;-) ;-)Nico

Guys,I really don't know...These I do know:The 1.3 patch changes the APS.DLL, because the size AND date are different in the 1.2 version (as quoted in my original message), AND the date matches that of the gauge file Nico mentioned, that had been updated in the 1.3 patch.I could NOT save panel status before. Only after trying "my method" it worked flawlessly... Not much to add...Terops. Btw, I just remembered that I had the FMCWP directory "commented out" under FS2002 (I just renamed it to _FMCWP), because I did some updating and stuff. That couldn't have any effect on this, could it... ?

Hello PIC-flyers,I also discovered the problems mentioned above. With the 1.3 patch under Win98 FS2002 crashed, when saving a flight with PIC. After using WIN XP the flight was saved, but only with the original FS2002 settings, not the PIC-specific panel settings.In the .FLT-files are first all original FS2002-settings listed, follwoed by the PIC-settings from PIC_AFDS to PIC_FMC. Since the 1.3 patch PIC is unable, to save these settings in the .FLT-files.You can't save new PIC panel settings and you can't save changes in these settings. But you can edit the .FLT file and copy the PIC settings from an existing FLT-file with PIC settings beginning with PIC_AFDS until the end of the file. This way you can add the panel settings to an existing flight: 1) Make all FS settings (Position, weather, engine etc.) and all PIC panel settings and save the flight. You should set the cockpit completly in the state you want to save it or it may be that the FS values are set diffenrent from the PIC values and this can cause problems. 2) Look for the FLT-file with the name you gave it under FLIGHTS -> MYFLTS and edit it with notepad. Look for a FLT-file with the PIC-settings you want (dark cockpit, running engines ...) and copy the sections above ( PIC_AFDS to PIC_FMC ) to the end of the new FLT-File. You can even change some values in this section. 3) Save the changed FLT-file.From now you can load the flight and the PIC-settings are ok. If you want, you can chnge the settings in the FLT.file or copy them into other FLT-files. In the PIC-Menu under load settings / save settings are only FLT-files / flights listed, which have the PIC sections. Because the settings are not saved when you save a flight, PIC doesn't recognice these flights as PIC-flights. If you added the PIC section manually, it does!There is another problem. After saving a flight or a changed flight with PIC, the FLT-File can be corruped. At the beginning of the file are the first lines twice present, showing different entries. You have to delete the wrong second entries, or FS doesn't accept this file and doesn't show it. So you can't load it from the menu.Maybe I did not discover all problems with saving panels and flights. But I think, the method above can help to avoid the problems caused by the 1.3 patch.Kind regards,Tony

Tony,Great information!I think this settles our problems for good. The entries in the FLT-file are clear and self-explanatory, and there shouldn't be any trouble in editing it to one's liking...Nice...Tero

Tony,As (almost) always: the answer is right before our very eyes, if we would only look for it.Great thinking and yes, it did work for me. Thank you!Kind regards,Stephan Haashttp://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg

Hi Tony,Thanks you for your contribution. It seems to help others, like Stephan, to work around this problem, which is great!However, I do not agree with your statement:>Since the 1.3 patch PIC is unable, to save these settings in>the .FLT-files.I have inspected my latest .FLT file, created at Aug 4, and found all the PIC-settings present.... Like I said before, I have no problems saving my panel state with patch 1.3.There must be something else that's causing this...Nicowww.nicokaan.nl

Nico,This is so weird.My flight saving trouble started immediately after installing the 1.3 patch. Immediately. BUT... take note that you do HAVE the external MCP installed (I do too, but it's home made and connected via FSBUS), whereas I don't.I'm suspecting that with people who are running the 1.3 patch AND the external HW, the PIC-panel "sniffs" some settings from the MCP module before saving the data to the .FLT file. I don't have the MCP installed, so I guess the sniff-procedure fails and the PIC settings are NOT therefore saved to the file. This is pure speculation, but it would be logical.Also, the DLL swapping cured my problem. And it didn't work with Stephen :(. Anyway, now that we know that there are separate and easily editable PIC-settings in the FLT-file, there should be no problem for anyone to save desired panel states :).Tero