Error loading bitmap

[Delphia]

Hi!

When I tried to test a new payload model in FsP it says:

"ERROR!!! Unable to load background image"

The image I used meets the required specs (jpg, resolution), but it seems something is wrong with it.
Are there any other things to pay attention to?

Thanks for help, Hagen.

[Drew]

silly q - the jpg file is in the payload folder???

[Delphia]

Of course... together with the ini where it´s supposed to be...

I wonder if the filesize is of interest? Just tried it, but that didn´t work either. It was around 100K before and is now 45K.

Someone else any idea?



Post Edited ( 11-18-05 22:45 )

[Delphia]

Sorry, folks, seems I found the problem now...

Well, you shouldn´t change the name of the image without resaving the ini-file.

I had to change the filenames for my payload model because it didn´t appear in the dropdown selection.
I did it outside the payloadeditor and that´s why the ini-file still had a link to the old image name.

What I´d still like to know is, why doesn´t my customized payload model appear? Since I renamed it to the default "737-800.ini" and "737-
800.jpg" it´s selectable, but with extension ( "737-800_AB.ini" and "737-800_AB.jpg" ) it wasn´t!

I thought the filename and/or its lenght doesn´t matter? It works as described above, but what if I want to have more payload variations for
the plane? Obviously FsP only accepts the default model...

Has anyone else tried my payload model encountering the same odd thing?

Hagen

[Drew]

so basically - the jpg file (the one relating to the ini file) wasnt in the payload folder

glad its sorted

oh, about the file, are you remaning the ini file to match the name in the cfg file? there was a post about it just the other day

[DanSteph]

if you want any variation it's juts a matter of using another name.

remember:

1st RULES: payload model is choosed if any part of the aircraft's name match the ini name.

example:

aircraft name: PMDG 737-800 with lufthansa livery Virtual Cockpit

Any of those ini will be available in the drop box (example):

737.ini
PMDG.ini
737-800.ini
PMDG 737-800.ini
PMDG 737-800 with lufthansa.ini
PMDG 737-800 with lufthansa livery Virtual Cockpit.ini


2nd RULES: the ini name that have the longer name is choosed first when you bring the payload loader, other that match are available in the drop box. (ie: you can select them)

In our example this ini: "PMDG 737-800 with lufthansa livery Virtual Cockpit.ini" will be available at first when you bring the payload loader dialog, others will be available in the drop box.

3nd RULES: the more your ini name is generic the more it will work with a lot of aircraft

"737.ini" will work with almost every 737 (any aircraft that have at least "737" keyword in their name)
"PMDG 737-800 with lufthansa livery Virtual Cockpit.ini" will work probably for only one aircraft.


3nd RULES: adding "(cargo)" keyword in the ini name will make a ini file available also without this keyword being taken in account for name match.

example:

737 (cargo).ini will be available for aircraft that have "737" in their name AFTER an eventual "737.ini" payload model.

this is usefull for "cargo" only variation of an aircraft.


4nd RULES: the JPG image is not assigned to a payload model (ini) when their name match but only when you choose it with the payload editor. Renaming the jpg image will therefore simply make the "ini" file not found the image anymore.

the 4nd rules mean that you can rename and copy all the ini you want they will always find the image as the jpg filename is included in the ini file as choosed by the payload editor.


Hope this help ?

Dan



Post Edited ( 11-18-05 23:44 )

[Drew]

just to add...

copied from Pegase post...


What you have to know:
-What FsP call "name" is what is in the entry called "title" in aircraft.cfg.
-You have as many entries "title" than sections [fltsim.0], [fltsim.1]....[fltsim.x]
-You have as many sections [fltsim.x] that you have versions of a given plane each of these sections giving what is specific to the version
like the texture, VC or not VC etc...

Give the same title to all versions you want to fly and the job is done.

See below
[fltsim.0]
title=Project Opensky - Airbus A340-313E Air France VC <---------- THIS IS THE FsP NAME
sim=A340-313E-GE-CFM56-5C4
model=VC
panel=VC
sound=
texture=
checklists=

atc_airline=AIR FRANCE
atc_id=F-GLZR
atc_flight_number=1
atc_heavy=1
atc_parking_types=GATE, RAMP, CARGO
atc_parking_code=AFR

ui_manufacturer=Airbus
ui_type=A340-300
ui_variation=Air France (Virtual Cockpit)
visual_damage=1
description=Project Opensky \nAirbus 340-313E High Gross\nVersion 2004.8.1\n\nFS2004 Only\n\nEngine Type: GE CFM56-
5C4/P\n\nModel Designer\n Shervin Ahooraei\n\nFlight Dynamics Designer\n Warren C. Daniel\n\nMaster Texture Designer\n Ben
Hewitt\n\nTechnical Resource\n Simon Ng\n\nTest Pilots\n Project Opensky Members\n\nFor proper operation: See A340 manual at:
\n http://www.projectopensky.com


[fltsim.1]
title=Project Opensky - Airbus A340-313E Air France WV <------------------------- THIS IS THE FsP NAME
sim=A340-313E-GE-CFM56-5C4
model=WV
panel=WV
sound=
texture=
checklists=

atc_airline=AIR FRANCE
atc_id=F-GLZR
atc_flight_number=1
atc_heavy=1
atc_parking_types=GATE, RAMP, CARGO
atc_parking_code=AFR

ui_manufacturer=Airbus
ui_type=A340-300
ui_variation=Air France (Wing View)
visual_damage=1
description=Project Opensky \nAirbus 340-313E High Gross\nVersion 2004.8.1\n\nFS2004 Only\n\nEngine Type: GE CFM56-
5C4/P\n\nModel Designer\n Shervin Ahooraei\n\nFlight Dynamics Designer\n Warren C. Daniel\n\nMaster Texture Designer\n Ben
Hewitt\n\nTechnical Resource\n Simon Ng\n\nTest Pilots\n Project Opensky Members\n\nFor proper operation: See A340 manual at:
\n http://www.projectopensky.com

[Delphia]

@Dan

Thanks, that helped me to understand the naming rules

@Drew

Well, the image was in the right directory all the time but as I stated above the failure was that I renamed it outside the payloadeditor
instead of changing it using the editor.

So for my payload model I´d use "B737-800 Air Berlin.ini" and "B737-800 Air Berlin.jpg". This should work, right?

Thanks to all, Hagen.

[DanSteph]

Delphia wrote:
So for my payload model I´d use &quot;B737-800 Air Berlin.ini&quot; and &quot;B737-800 Air Berlin.jpg&quot;. This should work, right?

As I'm not sure 100% you get the jpg name stuff:

You can call your JPG "XdfWreT56GFH.jpg" as long
as you select it in the payload editor and save your ini your ini will "find it"

Now you can call all jpg of the world the same name than an ini file if
you don't select it in the payload editor it will never work.

Hope it clarify ?

Dan

[Delphia]

No, Dan, I think I got that already. I know that the jpg can have any name as long as it is chosen in the dropdown and saved in the ini-file.
That´s clear so far.

But when I used an ini named "737-800_AB.ini" (the jpg was named that way too) it didn´t appear in the dropdown within FsP
(only "737", "737 (cargo) and "737-800" ). I then made a backup of the original "737-800.ini" and "737-800.jpg" and resaved my payload
model files to "737-800.xxx". After that I had my payload model in the payload dropdown and it worked.

Actually the question was, why it doesn´t work anymore when its labeled ***_AB.*** ?

Just to clarify, your example again:

aircraft name: PMDG 737-800 with airberlin livery Virtual Cockpit

Any of those ini will be available in the drop box:

737.ini
PMDG.ini
737-800.ini
PMDG 737-800.ini
PMDG 737-800 with airberlin.ini
PMDG 737-800 with airberlin livery Virtual Cockpit.ini

and 737-800_AB.ini -> but this one never showed up

According to your naming rules mentioned earlier my caption should work... Well I even tried the name "737-800 AB" for the underscore
might have been the problem - but it made no difference.

Am I too stupid?

Hope, I made the problem clear now. If you don´t know what I mean, could you (or anyone flying the B737) please try my uploaded model
and tell me whether you can use it or not?

[DanSteph]

Delphia wrote:
aircraft name: PMDG 737-800 with airberlin livery Virtual Cockpit
and 737-800_AB.ini -&amp;gt but this one never showed up

Mhhh ?

Find the difference beetween those two strings:

"737-800_AB"

"737-800 with airberlin"

As you see there is not much matching beetween the two....
there is a "_" where it expect a space, a "A" where it expect a "w"
and a "B" where it expect a "I"


sorry but I think you still don't get this name stuff.
the string name in the ini file must match EXACTLY any part of the aircraft name...

Let take an example with this aircraft name: PMDG 737-800 with airberlin livery Virtual Cockpit

This ini file will match: "737-800 with airberlin.ini" as this one "737-800 with ai.ini"
but this one "737-800_with airberlin.ini" will NOT ("_" character) as this one : "737-800 with ab.ini" ("ab" when it expect "ai) and this one "747-800 with airberlin.ini" ("747" where it expect "737")


Again the INI name mutch match exactly ANY part of the aircraft name see below an extrem
example of a part that match:

"ry Virtual Cockpit.ini"
"PMDG 737-800 with airberlin livery Virtual Cockpit"


Post your aicraft name if you still fail I'll give you a valid name.

Dan



Post Edited ( 11-19-05 03:38 )

[Delphia]

Ok, Dan, sorry for my incompetence!

NOW I got it, really!

I totally misunderstood that aircraft thing. I thought it would be enough to have "737-800" in the name and everything coming before or
after that doesn´t matter. But as I see now it must be exactly a part of the aircraft name in the aircraft.cfg in order to appear in the
dropdown. And 737-800_AB isn´t for sure! Right you are! ...well as long as I don´t rename it in the aircraft.cfg, right?

So, to make it work properly I have to name it for example "730-800 Air Berlin" when in the aircraft.cfg is "title=B737-800 Air Berlin -
Winglets". This way most of 737-800s with Air Berlin livery should be able to use it.

Thanks for your patience, Dan!

Hagen

P.S: It was definitely too late for me to understand the whole naming stuff . . . it´s 4a.m. and that´s why I go to sleep now . . .



Post Edited ( 11-19-05 04:20 )

[DanSteph]

Delphia wrote:
Thanks for your patience, Dan!

You welcome

Fortunately It's not case sensitive "737-800 AIR BERLIN" will work the same than "737-800 air berlin"

As you see if you want to make different payload model you have plenty of choice taken that your aircraft
is not named with one letter only

for example you can add the following payload model for the "B737-800 Air Berlin - Winglets"
each one with a different image:

Two class:
B737-800 Air.ini

Three Class:
B737-800 Air B.ini

One Class:
B737-800 Air Ber.ini

Charter:
B737-800 Air Berlin.ini

Cargo:
B737-800 Air Berlin (cargo).ini

In this case the last "B737-800 Air Berlin" will show by default as it's the longer ini name but the other will be available
in the drop box of the FSP payload dialog.

As long as the aicraft name is enough long to have plenty of variation
you can have as much as 10 payload model for each livery. (or much more)

Dan

[Delphia]

Dan, just read your last post...

Now that I understood everthing I should update the payload model... or anyone trying to use it may encounter the same problem.

Can I mail you the new zip-file or do I have to upload again?

Hagen, tired but happy

[DanSteph]

upload again and send me a mail or contact me to delete your outdated addon.

I go to bed also

Dan