+- FsPassengers Forums (http://www.fspassengers.com/forum)
+-- Forum: FsPassengers (http://www.fspassengers.com/forum/forumdisplay.php?fid=3)
+--- Forum: FsPassengers Support (http://www.fspassengers.com/forum/forumdisplay.php?fid=5)
+--- Thread: Another PSS Problem (/showthread.php?tid=6978)
Another PSS Problem - Sjef - 10-05-2007
Hello,
I've searched for my exact problem but didn't find a solution:
I have the PSS Airbus 330/340 and I'd like to use it with FSP too. When flying it "stand alone" the plane works perfect but as soon as I use
it together with FSPassengers for some strange reason the gear won't come up after take off. I've checked 3 times to see if I did
everything exactly as I did it without FSP.
Does anyone know of this problem or better have the solution.
Thanks,
Sjef...
Re: Another PSS Problem - poden - 11-05-2007
Its possible FS Passengers has the plane marked as "damaged". If you bought it used in FSP, it may have needed some repairs. Try starting a flight with the Airbus you bought, then go into the company manager, and aircraft maintenance. Planes needing maintenance/repair should show up on this list. Just click on its name to check the cost of the repair/maintenance, and decide if you want to do the repair (assuming your company has enough money and all that). This is the same dialog you do when maintaining aircraft after each flight.
Before buying a plane, you can check for pre-existing damage on used planes by going into the "read more info about this plane" dialog.
Best of luck!
Post Edited ( 05-11-07 01:02 )
Re: Another PSS Problem - Sjef - 11-05-2007
I bought the plane brand new, so that shouldn't be the problem, but I'll check to make sure!
Re: Another PSS Problem - pegase - 13-05-2007
The PSS A340 has a bug in the electric power management: The battery gets empty in some 15-20 minutes whatever you connect or not
APU or Generators. When this occures, nav lights and strobes become inoperative and YOU CANNOT PULL UP THE GEARS.
The only relation with FsP is that probably you take more time on ground, then, the battery is empty when its time to pull your gears up.
The only efficient way to get rid of this bug is to check the endless battery load option in FSUIPC (need the registered version).
Re: Another PSS Problem - FsP Dennis - 13-05-2007
That bug should be corrected! It has been known for a long time! Too bad PSS....
Re: Another PSS Problem - Sjef - 13-05-2007
OK, I don't have a registered FSUIPC. Guess if I want to use the pss busses I'll have to buy it someday.
Is that the same problem the PSS a320 has?
Re: Another PSS Problem - Sjef - 15-05-2007
Hmmm, as soon as I register my fsuipc there goes something wrong: other addons don't work anymore, smoothai - activesky and
squawkbox! Are there any fsuipc specialists here who kwow how to solve this?
Re: Another PSS Problem - DSW334 - 15-05-2007
I am not sure.. But I seem to remember that I have read somewhere that some add-on's don't like a certain version of fsuipc because
there was an issue with backwards compability.. you might try to search for that on avsim, or google.
Re: Another PSS Problem - pegase - 15-05-2007
Perhaps it is a FSUIPC version problem or some settings in FSUIPC ?
I just have activesky in your list and did not get problems with it.
It is OK too with RC4, Fsinn and Ivap.
The latest version is 3.74 and comes with some clues in the user guide about addons stopping to work with FSUIPC in page 49
I just cut pasted this section, I hope it helps
HELP: “My utility program doesn’t work with FSUIPC!”
The most likely reason for any application program or add-in module or gauge not being able to access FSUIPC properly is
that your FSUIPC is not registered, and the application, add-in or panel is not a version which is accredited for use with this
version of FSUIPC. Look in the FSUIPC.LOG file (in the Modules folder) using any text editor. It may well confirm that this
is the problem.
Another, thankfully less common reason, is a bad user Key for FSUIPC or WideFS. If your application works when you
remove or delete the FSUIPC.KEY file from the FS Modules folder, but not when FSUIPC says it (or WideFS) is properly
user registered, then it is likely that one or both such keys is one generated by one of the pirate key generators about. Stop
using such keys immediately, as on top of being illegal they cause odd problems throughout FSUIPC and WideFS operations.
If you believe your key is good, purchased correctly from a bona fide dealer, then tell me about it on the Support Forum. But
do not publish your details nor your keys.
Otherwise, the program is not accredited. You have two options to choose from: either register FSUIPC so that it works with
all such programs, or contact the author or supplier of the program to see if there’s an update or Access Key, which he can
supply to solve the problem.
If the program you are trying to use is obsolete, and no longer being maintained, sold or supplied by anyone, then you can
apply to me, via the Support Forum (see front page) to see if it is possible to get a free access key for it. The same applies to
active freeware, but in that case it should always be the author who arranges for the key.
If FS crashes with FSUIPC installed, but not without it
A crash on exiting FS is not unusual, although it should be very rare with the recent versions of FSUIPC. It seems to be due
to the way FS closes down its modules. FSUIPC is multithreaded and occasionally the extra threads are left running till last,
after data they wish to access has been removed from memory.
If you find this annoying, one way around it seems to be to make sure the FSUIPC is the first module loaded and unloaded.
To do this, make a temporary folder somewhere, then move all of the .DLL files out of the FS Modules folder, move just
FSUIPC.DLL back, and then all the others. Take care not to mislay any in doing this!
If you get a crash in FS at any other time, and either it identifies FSUIPC.DLL as the ‘culprit’, or you believe it must be
FSUIPC because that’s the only thing you’ve changed, then please do the following:
49
1. If you are using FS2002 or FS2004, you first need to edit the FS CFG file. Use an ordinary text editor, like Notepad. Find
the section [MAIN] and add the line “ReportErrors=0” (without the quotes). This stops FS handling the error itself, so
allowing you to collect data in other ways.
2. Before running FS again, run DrWatson.EXE (in Win2000 or WinXP it is DrWtsn32.EXE and it is in the
Windows\System32 folder). To do this, simply click the Windows Start button, then Run, type ‘DrWatson’ (for example)
and hit return. It will run and place a little icon in the system tray, which you can ignore. (On Windows 2000 and
Windows XP it might come up with a set of options first. It is the Log you want, not the Dump, so note where that is
going to be placed, or choose a different suitable folder for it).
3. Run FS and attempt to provoke the crash by generating the same conditions again.
4. When the crash occurs, DrWatson will collect all the information I need. Find the latest .WLG type file in the
Windows\DrWatson folder (in Windows2000 or XP the filename and location will be different. The file will be a normal
text file and will normally have file type .LOG), Zip it up (very important! <G>), and send it to me with a description of
what you were doing when the crash occurred.
Re: Another PSS Problem - hobeprime - 19-08-2007
Hello!
I've been having loads of problems with gears and autopilots on PSS Airbuses. They have all vanished since I do the following:
1.) Load a FS standard aircraft (737 or 777)
2.) Start it's engines. Ctrl + E
3.) After all engines are running, cut the engines Ctrl + Shift + F1
4.) Now switch to your aircraft of choice (and start FS Passengers)
Regards,
Dennis