Textures disappear - pitiful misperfection.

[Grome]

Problem: The liveries textures disappear soon after the FSP flight starts. Only the entire computer reset fixes the problem.

Synopsis: Soon after the FSP flight is started I can't see the textures, only the grey model. It does not affest the framerate, or the
simulation or any other process. The liveries would not come back after the flight, they would not appear after the MSFS restart. Only after
the system reboot. Seen on all planes.

Additional info: MSFS 2004, localised (non-English) licensed version. PSS airbuses show the error that they can't find the textures and
point to the non-existent directories - relative to the system root, not the FS root as it should be. The latest non-registered FSP version,
downloaded from here. The latest registered FSUIPC. Celeron 2.66, 512Mb, Radeon 9600Pro, 128Mb, Catalyst 05.7

The problem never seen before.

Is it fixable? Any ideas?

[DanSteph]

can you post please the log.txt from FsPassengers folder ?

Thanks

dan

[Grome]

[Just skipped as Nothing interesting]



Post Edited ( 09-06-05 09:14 )

[Grome]

Additional info: WinXP SP2 - intl.

I guess that for some reasons the dll fails to read the WinXP long directory names. Some part of the code does not free the memory as it
should do, so, the error appears. Of course, that is only a guess.

[DanSteph]

can you start a flight and post again the log because there is no usefull info if you don't start a file.

Dan

[olseric]

I'm gonna take a guess here and say that you are overtaxing your system.

Had a similar problem with my ATI AIW 9700 card. Just upgraded to an ATI x800 Pro and no more problems.

If your graphic settings are really high, and you have a ton of AI aircraft, starting FS PAX might be just that little "boost" that pushes your
video card over the edge.

[Grome]

OK.. Had to fly again to have the problem - the second flight. Here is the log:

payload count 1
Payload ini> search loadmodel for: Boeing 777-300 House Colours
Payload ini> Found models: 777-300
Payload ini> Found models: 777
Payload ini> best match: 777-300
Payload ini> Loaded: 777-300.ini
payload count 7
Payload ini> search loadmodel for: Boeing 777-300 House Colours
Payload ini> Found models: 777-300
Payload ini> Found models: 777
Payload ini> best match: 777-300
Payload ini> Loaded: 777-300.ini
payload count 7
Payload ini> Zero Cg Pos found: 1.00000
original CGPos= -0.34177
payload count 7
Payload ini> search passenger lon: -122.38 lat:37.62 maxpass: 349
Payload ini> zone nbr: 0 use zone list name (self-1): 0 passengers found 349
payload count 7
payload count 7
payload count 7
payload count 7
payload count 7
payload count 7
payload count 7

Module and mem Listing:
------------------------------------
Total Virtual: 2147352576
Total Avail virtual: 1112690688
Total free mem: 1034661888
0X20600000 ABLSCPT.DLL
0X20650000 ACONTAIN.DLL
0X00AA0000 ActiveCamera2004.dll
0X01090000 ActiveRadar
0X01090000 ActiveRadar.dll
0X20670000 AI_PLAYR.DLL
0X20690000 ATC.DLL
0X20710000 CONTROLS.DLL
0X20740000 DEMO.DLL
0X20760000 DYNAMIC.DLL
0X20770000 FACILITIES.DLL
0X207B0000 FE.DLL
0X207D0000 FLIGHT.DLL
0X65000000 FsPassengers.dll
0X69A80000 FSSound.dll
0X20800000 FSUI.DLL
0X61000000 FSUIPC.dll
0X20900000 G2D.DLL
0X20C10000 G3D.DLL
0X20CE0000 GLOBAL.DLL
0X20CF0000 gps.DLL
0X20D10000 gps_export.DLL
0X20D20000 INSTRUCTOR.DLL
0X20D30000 MAIN.DLL
0X20D60000 mpchat.DLL
0X20D70000 MULTIPLAYER.DLL
0X20D90000 PANELS.DLL
0X09B10000 PMDGOptions.DLL
0X20E10000 REALITY.DLL
0X20E20000 SIM1.dll
0X20EC0000 SimScheduler.DLL
0X20ED0000 SOUND.DLL
0X20EF0000 SYMMAP.DLL
0X20F20000 TERRAIN.DLL
0X21080000 Traffic.DLL
0X01150000 TrafficInfo.DLL
0X210B0000 UTIL.DLL
0X210E0000 VISUALFX.DLL
0X21120000 Weather.DLL
0X21160000 WINDOW.DLL
End of module listing

warning - contact_point returned zero, setting gears speed to 250kts
Use FSP ATC ID
ATC Aircraft MTOW is: 759600.00000
Heavy Value before change= 7
Heavy flag set
Starting FsPassengers adventure
Loading Crew sound from user chosen directory Sound/CrewPack/Default/
Loading crew sound, default voice pack used
Disabled penalty flag 0
Mainloop Use timer
Total Percentage of failure= 5
Cruise sound loop started at seconds: 1772
Cruise sound number: played at second : data1: 8 data2: 1772
Cruise sound loop started at seconds: 3098
Cruise sound loop started at seconds: 4420
Cruise sound loop started at seconds: 5556
Cruise sound loop started at seconds: 6619
Cruise sound number: played at second : data1: 4 data2: 6619
Cruise sound loop started at seconds: 7349
Cruise sound loop started at seconds: 7756
Cruise sound loop started at seconds: 8477
Cruise sound loop started at seconds: 9110
Cruise sound loop started at seconds: 10075
Cruise sound number: played at second : data1: 8 data2: 10075
Cruise sound loop started at seconds: 11359
Cruise sound loop started at seconds: 12597
Cruise sound loop started at seconds: 13231
Cruise sound loop started at seconds: 13945
Cruise sound loop started at seconds: 14402
Cruise sound loop started at seconds: 14863
Cruise sound number: played at second : data1: 4 data2: 14863
Cruise sound loop started at seconds: 15428
Cruise sound loop started at seconds: 16008
Cruise sound loop started at seconds: 16742
Cruise sound loop started at seconds: 17425
Cruise sound loop started at seconds: 17958
Cruise sound loop started at seconds: 18569
Cruise sound loop started at seconds: 19374
Pausing FsPassengers adventure
UnPausing FsPassengers adventure
Cruise sound loop started at seconds: 19879
Cruise sound loop started at seconds: 20701
Cruise sound loop started at seconds: 21369
Cruise sound loop started at seconds: 22199
Cruise sound loop started at seconds: 22979
Cruise sound loop started at seconds: 24342
Cruise sound loop started at seconds: 25429
Pausing FsPassengers adventure
UnPausing FsPassengers adventure
Gps release
Ending FsPassengers adventure

Well.. You know, the video card issue can take place, of course. But the most pitiful thing is that even such a heavy crafts as e/g/ 707
(legendary) worked OK and I have that damned grey bottles only when I try to fly with FSP (GREAT thing, as I said before) and only on the
second and more flights. So, that makes me to suspect, that something is still not as good as it should be with the FSP..

[SWAFO]

To me it sounds more like an issue with FS, as opposed to FSP. FSP does not interfer with textures at all, and from what you're
describing, it seems like your textures simply aren't loading on top of the model (all FS9 related). Do you give it some time to load?
Occasionally large textures can be quite taxing on your system, and might take a while to load.

I'm guessing that your issue isn't FSP related. You might want to try removing/re-installing some of your current textures that are causing
problems, or simply removing and re-installing FS9 altogether. This seems to fix most issues.

[jboweruk]

I'd have to agree with Brad, FSP doesn't load any textures, so it's unlikely that FSP is causing it. You dont' say whether these are DXT3 or
32 bit textures either, if 32 bit then be prepared not only for long load times but lame framerates. Looking again at your post I'm
suspecting a graphics driver problem. Try updating your drivers for your video card and see if that helps. Alternatively try reinstalling the
textures for the aircraft.

Hope these suggestions help.

[Grome]

OK.. Perhaps I wrote it not so clear - I am convinced, that the problem is NOT in the textures, neither it is in the textures rendering!

"grey bottles" appear on the SECOND flight and more. First flight (before the system reboot) is OK. The problem appears on all aircrafts
in the stables, including the default planes, most FPS friendly ever available.

And one else phenomena: As you probably know, usually the liveries (aka skins) are stored in e.g. c:\Program Files\FS9\Aircraft\[model
name]\Texture PSS Airbuses also have some textures - e.g. the textures for the certain engines, in the c:\Program Files\FS9\Pss\Texture
folder. When the 'grey bottle' phenomena occurs, I get an error message, that c:\Pss\Texture folder can't be found. (of course, it
can't be found as it does not exist!) This never happens when the FSP flight was not started, no matter how many other processes and
how heavy processes are active on the computer. Only the complete system reboot helpes. Not the FS restart.

All that make me to believe that somewhere in the core code of FSP there is some process, that causes a memory cycle, which does not
stop when the FSP DLLs are unloaded. This cycle prevents the program root reading (c:\Program Files\FS9\ in my example) and makes
the MSFS DLLs, responsible for the aircraft textures reading to apply to the SYSTEM root (c:\ in my example).

On the other hand, having no idea at all how does the raw code of FSP looks like, I can't insist on my idea. Such as I can't say for sure that
the 'grey bottle' phenomena is not caused by some mistake, or inaccuracy in the MSFS code.

My intention is just to pay the authors' of the wonderful addon attention on the possible misperfection in their great (I mean it!) work.

[DanSteph]

that look really strange....

Now to help me detect what is happening I need some PRECISE test and report, be warned that ONE wrong
answer to a test can destroy all the "detective work" I can do the best things would be of course that you send me you
computer I'm sure I would see what happen in no time but I'm affraid that's not possible.

I wrote a big mail with some test but before posting it I see a strange things that I want you to check:
FsPassengers log say that there is two activeradar in the DLL list at the same location.

0X01090000 ActiveRadar
0X01090000 ActiveRadar.dll

That sound strange to me....

So can you go in your module folder and MOVE all activeradar things OUTSIDE of modules folders
even NOT on a subdirectory and DON'T rename them, simply move them in your desktop for example
ready to copy them back in modules folder. Also be sure to even move ALL "activeradar" files
even if the don't have a "dll" at the end.

By the same occasion to be sure move also the following DLL On your desktop:
ActiveCamera2004.dll
ActiveRadar.dll
FSSound.dll
PMDGOptions.DLL
FSUIPC.DLL

move also all strange ini or other files. Keep only the core DLL and the FsPassengers DLL in the modules folder.
Start Fs9 and do as usuall to reproduce the problem, see if it happen and PLEASE POST THE LOG.TXT
after you quit Fs9.

Once done of course move all the saved files from your desktop to Fs9/modules folder so you get all back.

Thanks

Dan



Post Edited ( 09-06-05 15:15 )