|
Post by londonlad on Oct 1, 2014 8:03:15 GMT -5
Running Windows 8.1 I wanted to add an additional livery to my DC-6Bs. Downloaded the Northeast file from Avsim library. I unzipped and pasted the aircraft.cfg into my DC-6B CB-17 file. I placed it between the PAA and the line: ATC_Parking_codes=PAA and the line: Camera definition.001. The aircraft appears in the Aircraft Select Menu but after clicking OK, I get a dialogue box that states: Aircraft initiation failure. Douglas DC-6B Northeast Airlines. Then FS9 crashes. Can anyone help me with this? Thanks in advance
|
|
|
Post by FSMuseum on Oct 1, 2014 8:49:45 GMT -5
Have you checked to make sure the Sim= line in your cfg is correct in the new livery? It should be exactly the same as the name of the .air file in the aircraft folder without the .air extension on the end, for example, Sim=Boeing737_400
|
|
|
Post by londonlad on Oct 1, 2014 11:25:36 GMT -5
The sim line reads: sim=dc6b Didn't change it. Not sure where the .air file is located but think this sim line is OK. Thanks for your input.
|
|
|
Post by Tom/CalClassic on Oct 1, 2014 11:26:57 GMT -5
How about the model= line? Should be the same as at least one other livery.
|
|
|
Post by londonlad on Oct 1, 2014 15:16:38 GMT -5
I changed the model= to model=spinner also added _17 to the kb check list line and _17 to the kb reference line.
The aircraft now appears in FS9 but no colors or windows, etc.
Thanks for you help, Tom. Is there anything else I should look at?
|
|
|
Post by FSMuseum on Oct 1, 2014 15:24:07 GMT -5
Try changing the format of the textures using DXTBMP to either DXT1 or 24 Bit
|
|
|
Post by Tom/CalClassic on Oct 1, 2014 15:50:21 GMT -5
The texture format should be OK.
BTW, this should really be in the DC-6B CB-16 folder (domestic version), not the CB-17 (international version). And it should be model=, not model=spinner (no large spinners)
What is the name of your northeast texture folder?
If texture.ne (for example), the line in the aircraft.cfg file should read:
texture=ne (what ever comes after the period in the folder name).
If that is OK, open the NEA texture folder and look at the texture file names. Do they match the United folder texture names?
Did you follow the instructions in the Adding Liveries.txt file?
Hope this helps,
|
|
|
Post by londonlad on Oct 2, 2014 11:16:21 GMT -5
Deleted everything from the CB-17 file and recopied to the CB-16 file The name of the texture folder is: texture.ne. and is how it is in the aircraft.cfg file. Nothing follows the period. The NEA and UAL texture folders appear identical. I followed the instructions to the best of my ability which I admit is often weak. I can usually follow instructions but at times I find the instructions to be a bit ambiguous.
After moving to the CB-16 folder, I get the aircraft listed in the Select menu but when clicking OK, the aircraft appears without color or windows, etc. The flaps, rudder, ailerons and elevator all operate normally. Hope you can help. Thanks so much in advance
|
|
|
Post by Tom/CalClassic on Oct 2, 2014 11:48:17 GMT -5
Post the livery sections of the DC-6B CB-16 aircraft.cfg file, and a picture or list of the folders inside the DC-6B CB-16 folder.
|
|
|
Post by Dennis the menace on Oct 2, 2014 12:01:28 GMT -5
If the aircraft appears with no textures on it, then usually the error is in the aircraft.cfg file.
For some reason it is not showing the path to the texture folder.
There are two main possibilities for this problem to occur.
1. You MUST have the texture= line read the exact same name as the aircraft's texture folder. If for example, the texture folder you wish to use is named Delta61, for example, then you must have in the aircraft.cfg this entry: texture=Delta61. No misspellings or spaces are allowed. It MUST be exactly the same as the name on the texture folder itself. Deviate from that one bit in the least and no textures will be shown in FS!
2. Another possibility (and it has happened to me) is that in the texture folder instead of there being many bmps, there is another folder. Some people will do this when they zip up a file - I don't know why they do it, but some do. I have seen a texture folder with a folder inside of that, and yet again ANOTHER folder inside of that one that had the actual bmps in it. All of the bmps must be ONLY in the initial texture folder. No folders inside of folders are allowed!
3. There is one last possibility, but it is rare and I seriously doubt it is your issue here. That is the textures are in the wrong format. Once I downloaded an aircraft and no textures were visible on the airplane, just complete model gray. It turned out that the textures had been uploaded in 24 bit millions of colors, which of course FS will not display. If by chance the textures are not in the power of two or off by even one pixel in dimensions, then FS will crash, or lock up to the point where you have to do a cold computer reboot.
If you only get an aircraft showing up in its model colors, then 99.9% chance the issue is one of the first two, usually the first.
|
|
|
Post by Tom/CalClassic on Oct 2, 2014 12:04:53 GMT -5
OK, I checked it out. 1. Downloaded ne6b.zip from AVSIM. 2. Opened the zip file by double clicking it. 3. Opened the ne6b folder by double clicking it. 4. Clicked on the texture.ne folder, right clicked it and chose Copy 5. Right clicked in the FS\Aircraft\DC-6B CB-16 folder and chose Paste 6. Opened the Readme.txt file by double clicking it, and copied this section (drag to highlight, right click and choose Copy): [fltsim.xx] title=Douglas DC-6B Northeast Airlines sim=dc6b model= panel= sound= texture=ne kb_checklists= kb_reference=dc6b_ref atc_id=N6586C ui_manufacturer=Douglas ui_type=DC-6B ui_variation=Northeast Airlines 1958 description=The DC-6B was generally considered to possess the best operating economics of any piston airliner built. Passengers also appreciated their smooth, quiet ride. United had 43 DC-6B's, and used them throughout their US system. atc_airline=Northeast atc_flight_number=345 atc_heavy=0 visual_damage=1 prop_anim_ratio=0.9 7. Opened the DC-6B CB-16 aircraft.cfg file by double clicking it. 8. Located the last fltsim section, and right clicked just below that section. Chose Paste. 9. Edited this section by changing the line: [fltsim.xx] to: [fltsim.9] since the last section in my file was [fltsim.8] (they must be numerical). I saved the aircraft.cfg file. Started FS9, selected the plane, and: Hope this helps,
|
|
|
Post by londonlad on Oct 2, 2014 20:34:45 GMT -5
First off, thanks Tom, Dennis and the others who tried to help. I appreciate your willingness to help a computer illiterate. I tried all the things you suggested but still get an airplane with no color, windows, etc. I did notice that the props were just a transparent blur with only a suggestion of motion. When shut down, the proops looked normal. The virtual cockpit (which I rarely use) had no red objects. Not at all sure what steps to take next. Thanks again for all your help and concern. Bill R
|
|
|
Post by Tom/CalClassic on Oct 2, 2014 20:58:09 GMT -5
If you have an OS later than WinXP and have installed FS into any of the Program Files folders, the OS may not let certain files load. This can lead to problems like this. To test this, go to Control Panel/User Accounts and click the link "Change User Account Control Settings". Then move the slider all the way to the bottom and restart FS. Do the textures show up now? Move the slider back for a computer that will warn you of potential security problems.
Hope this helps,
|
|
|
Post by londonlad on Oct 3, 2014 10:45:17 GMT -5
Thanks again, Tom FS9 is not in a program file. I created an additional folder named "touchngo" and installed FS9 there. I had to do the user account thing when installing the DC-6B base packs. Tried the same with the livery issue but still remains a bare aircraft. I guess I will just live with the 2 liveries. Thanks for all your help, Cheers Bill
|
|
|
Post by Tom/CalClassic on Oct 3, 2014 12:00:50 GMT -5
We'll get this figured out. Can you post the fltsim sections (all of them) from the plane's aircraft.cfg file, and take a picture or list the folders present in the DC-6B CB-16 folder?
|
|