|
Post by moosje on May 6, 2020 9:41:48 GMT
Hello ,
IN FS9 the 737-400 wont show up , 733 and 735 are working fine , only the 400series dont Anyone who could help me ?
Kind regards
|
|
|
Post by aerofoto - HJG Admin on May 6, 2020 20:15:27 GMT
It can't not show up .... "if" it's been installed correctly .... and more-so given they are FS9/FS2004 native whilst also being FSX portable. What we need to know, from you, is precisely how you've tried to installed it. Saying the B737-400's don't display tells us "nothing at all" 1. Which B737-400 aircraft base pack are you trying to install. 2. Which B737-400 textures are you trying to install .... and into which base pack/s 3. It would be helpful to see the entire ADD TO AIRCRAFT/FLTSIM.XX section (only) of your B737-400 aircraft base pack/s .... COPY & PASTE that data "HERE" please (just the FLTSIM.XX data onlt and not the entire AIRCRAFT.CFG).4. It's also often helpful to post an image "HERE" showing your aircraft base pack and its contents. Common errors are .... - People installing textures inside the wrong base packs. - People not checking their FLTSIM.XX are correctly edited "in strict numerical sequence" (or at all) .... or that certain other standard lines are "consistent" with the FLTSIM.XX data for everything else they have installed for a particular aircraft type version. - People not taking care to ensure "valid FS destined folders" aren't still contained inside containing folders from the original ZIP file/s. There's any number of possibilities for an "FS NO SHOW" .... ranging from End User errors with their installations to minor oversights on our part (even) which haven't been detected pre-release by our normally very thorough inspection processes .... and there's also, in the past, been situations where some files have been corrupted during uploading/downloading process and over which nobody has any control. The above are a few of the the most commone reasons for "FS NO SHOWS", but, until you provide "much clearer/more definitive information" .... then .... we're only "guessing". Provide the information requested .... please Mark C AKL/NZ
|
|
|
Post by moosje on May 7, 2020 16:32:18 GMT
Downloaded basepack 737-400C and also CONVERTIBLE FREIGHTER
Bluebird cargo textures: 2016 - TF-BBH - B737-4Y0 SF and 2016 - TF-BBJ - B737-476 SF
[fltsim.0] // Change "xx" to next number in sequence starting from 0 title=HJG_737-400C Bluebird Cargo Airlines (TF-BBJ) 2016 sim=HJG_737-400 model=734_no-brow panel= sound= texture=bluebird_cargo_2016_476sf_tf-bbj kb_checklists= ui_manufacturer=Boeing ui_type=737-400SF ui_variation=Bluebird Cargo Airlines - TF-BBJ (2016) atc_heavy=0 atc_id=TF-BBJ atc_airline=BLUE CARGO atc_parking_codes=BBD atc_parking_types=CARGO atc_flight_number=734 description=One should hardly be surprised that the world's most prolific manufacturer of commercial aircraft is also the producer of the world's most popular jetliner. The 737 became the best-selling commercial jetliner worldwide when orders for it hit 1,831 in June 1987 (surpassing Boeing's own 727 as the previous champ). However, it wasn't always that way\s in the first few years of production, there were so few orders that Boeing considered canceling the program. They didn't, and the airplane has more than proven itself in over three decades of service. Texture by Peter LIDDELL
Did thesame instal like other HJG models like the 733 and 5 and they work
Thanks !
|
|
|
Post by aerofoto - HJG Admin on May 7, 2020 22:33:20 GMT
Need you to clarify something here ....
When you say "the 737-400 wont show up" .... Are you meaning your B737-400 "are not" appearing/are not visible to be selected within the FS9 Aircraft Selection Menu ? .... or .... Are you meaning your B737-400 "is there" to be selected within the FS9 Aircraft Selection Menu, but, "isn't" displaying it's assigned BLUE BIRD CARGO texture ?
There's a very big difference between these 2 extremes and i need you to confirm which applies in your case
Mark C AKL/NZ
|
|
|
Post by Erik Ingram - HJG on May 7, 2020 23:17:30 GMT
Assuming the aircraft.cfg is copied exactly as it exists in the file, it looks like there's just a small change in the model line that should get you sorted. The model folder uses an underscore in its name (model.734_no_brow), so just replace the dash (so that it reads model=734_no_brow) and it should work as expected.
I'd just check the rest of your entries just to be sure the same line is formatted properly if any other liveries aren't showing.
|
|
|
Post by aerofoto - HJG Admin on May 7, 2020 23:49:18 GMT
Thanks for trying to help there Erik .... I believe I've found the/a problem I've just inspected the BLUEBIRD CARGO B737-400SF 2016 TF-BBJ file. The file downloads and unzips fine .... so .... there's no problem/s there. I suspect what you've been trying to communicate, to us, is the B737-400 appears and is selectable inside your FS9 Aircraft Selection Menu .... but .... it's "not" displaying the BLUEBIRD CARGO texture you've assigned to it. This result would be "totally consistent" in view what I've discovered when examining this particular file. The TEXTURE= data line within the supporting FLTSIM.XX data reads (correctly) as follows .... texture=bluebird_cargo_2016_476sf_tf-bbj .... HOWEVER .... the texture folder for this subjects reads (incorrectly) as follows .... texture.Bluebird_Cargo_737-476SF_TF-BBJ_2016 As can be seen above there's an obvious discrepancy between the TEXTURE= FLTSIM.XX data and the TEXTURE FOLDER NAME .... and this "will" cause this particular BLUEBBIRD CARGO 2016 TF-BBJ texture to "not display" on the 3D model until corrected. "THIS" .... is actually "MY FAULT" .... and is exemplary of what can happen when I'm suddenly interrupted during file building processes (bloody phone) or through tiredness sometimes when working well into the late hours of any evening/early hours of the morning .... mistakes "can and do" sometimes happen On the basis of the above discovery all one needs to do is edit the TEXTURE FOLDER name (only) to read precisely as follows .... so it then agrees with the FLTSIM.XX based TEXTURE= data line .... texture=bluebird_cargo_2016_476sf_tf-bbj.... and that "will"/should solve the problem Be sure to use this particular texture with our "B737-400C" configuration (Cargo .... not Combi or PAX versions) aircraft base pack .... and the B737-300/400/500 panel we offer .... along with our B737-400 version CFM-56 sound pack too (not the B737-300 or -500 sound pack versions) .... in order to complete and ensure this package is correctly configured. Do all of the above properly, as stated, and no problems should ever result .... short of any yet undisclosed installation errors. I've recompiled this particular texture file. The new version, when released, will be suffixed "V2" .... and we'll advise once it's available .... otherwise this particular issue is perfectly fixable as described above and at End User level. I've also additionally rechecked the other 2 BLUEBIRD CARGO B737-400SF textures too and each of these appear to be perfectly fine, so, only the TF-BBJ 2016 texture file was ever affected. Mark C AKL/NZ
|
|
|
Post by aerofoto - HJG Admin on May 8, 2020 19:52:28 GMT
As stated above .... this file was inspected following "MOOSJE's" report. A mismatch between the TEXTURE= "data line" within the FLTSIM.XX data for this particular texture (this particular data line is/was always correct) and the TEXTURE FOLDER "name" were discovered .... and which is why the B737-400 3D model wouldn't/couldn't display this BLUEBIRD CARGO 2016 TF-BBJ texture. This's now been "corrected" .... and a new/replacement texture file for this particular subject now uploaded. The new/replacement texture ZIP file is named as follows .... b737-400sf_bluebird_cargo_2016_476sf_tf-bbj_v2Folks now have 2 options available to them .... 1. Anyone in possession of the original file only needs to rename the TEXTURE FOLDER .... precisely as instructed within my (above) posting of yesterday. 2. "DUMP" the original file .... and replace it with the latest/new "V2" file for this particular subject (absolutely no alteration/s have been made to any of the texture BMP's for this subject since such isn't necessry). Either way .... all roads lead to Rome since either resolution "will" resolve the reported problem .... provided the file is installed correctly to start with" Use this particular texture with the aircraft base pack, panel, and sound pack assignments stipulated wihin my last posting (above). When accessing our DOWNLOADS section .... and the "737-400 SCD" page (within which this particular texture file is located) .... "REFRESH" your internet browser (select keyboard commands CTRL+F5) "prior to" attempting to download the "new/replacement" file. This action simply ensures nothing but the intended/latest file version is accessible. "THANKS" to Peter LIDDELL for his prompt action with this file replacement Mark C AKL/NZ
|
|
|
Post by moosje on May 11, 2020 10:56:37 GMT
I found the problem ,
in the aircraft map the model is named : 734_no_brow and the livery you downloaded in Add to aircraft.cfg its named 734_no-brow
now its working Thanks for all the help !
|
|
|
Post by aerofoto - HJG Admin on May 12, 2020 0:58:37 GMT
OK .... looks like my own file installation was correct (after the first correction .... hence the above images), but, it also looks like I cocked-it-up "AGAIN" .... per the corrected release file version file .... so .... sorry about that The actual MODEL FILE names as supplied inside each of the aircraft base packs "ARE CORRECT" .... so .... for God sake don't go editing these in order to correct any error or one will potentially be in trouble with other textures added to the same base pack later. The error is associated with what's stated within the MODEL= data line within the ADD TO AIRCRAFT/FLTSIM.XX data for that texture .... and it's only this particular data which, where appropriate, needs to be checked and edited to read precisely as follows .... model=734_no_brow.... that's with "underscores" as displayed above and "not" with hyphens. It was a simple COPY & PASTE error that occurred to several B737-400's (only) within the same upload and which wasn't detected, at the time, or even during the last check, and that's despite 3 separate pre-release checks having been performed. "TIREDNESS" is the culprit .... after staring at multiple CFG data for too long it's very easy for one's eyes to overlook a detail as small/minor as a hyphen versus what should have been an "underscore" Once again .... we'll get a new file uploaded (and we'll also reupload new files for each of the several other implicated textures too) .... and advise once these are ready to be plundered. Mark C AKL/NZ
|
|
|
Post by aerofoto - HJG Admin on May 16, 2020 7:28:45 GMT
I've had a lot on my mind/plate recently (all good/better and more interesting stuff though) and forgot to follow through in regard to this particular inquiry We've now uploaded a new "V3" texture file for this same "B737-476 SF BLUEBIRD CARGO 2016 TF-BBJ" subject. PLEASE NOTE: The MODEL= data line within the ADD TO AIRCRAFT/FLTSIM.XX data for this particular texture subject has its previously erroneous hyphen corrected to now read as an "underscore" in regard to the MODEL= data line for this particular file. We've also seized this opportunity to re-check the ADD TO AIRCRAFT/FLTSIM.XX data MODEL= data line for other B737-400's released since April 2018 (these being the only files to which this original "copy & paste" error can apply) and discovered several other textures needing identical data corrections, which have also now been similarly corrected and re-uploaded as "V2" files. Each of these corrected files are as follows .... - B737-4Q8 SF AERCARBIBE 2016 HK-5228 "V2" - B737-4Y0 SF BUEBIRD CARGO 2016 TF-BBH "V2" - B737-476 SF BUEBIRD CARGO 2016 TF-BBJ "V3" - B737-4Q8 SF BLUEBIRD NORDIC 2016 TF-BBM "V2" - B737-406 Combi FIRST AIR 2019 C-FFNF "V2" - B737-4C9 SF KALITTA CHARTERS 2017 N730CK "v2" - B737-4C9 SF KALITTA CHARTERS / DHL 2017 N730CK "V2" - B737-476 SF PARCELAIR 2019 ZK-PAQ 'V2" - B737-484 SF TOLL AVIATION 2014 ZK-TLL "V2" - B737-436 SF WEST ATLANTIC CARGO 2019 G-NPTZ "V2" - B737-406 SF WEST ATLANTIC CARGO / DHL 2019 G-JMCX "V2"Sorry about this .... but .... as explained per my last posting above it's just one of those things that can, and does, occasionally happen I want to thank Peter LIDDELL for the manner in which he's so promptly attended to these re-uploads and without the slightest hint of any complaint or fuss .... "THANKS" Peter Each of the above listed/re-uploaded files are now available for download. Remember to refresh your internet browser (select key board commands SHIFT+F5 "prior to" attempting to download any of these files from our "B737-400 SCD" downloads page.Use these textures with our "B737-400C" (all SF subjects only) and "B737-400 COMBI" (FIRST AIR subject only) Aircraft Base Packs .... along with the "B737-300/400/500 Panel" we offer and our "B737-400 version CFM-56 Sound Pack" too (not B737-300 or -500 Sound Pack versions) in order to ensure these simulations are correctly configured for optimum performance. Mark C AKL/NZ
|
|
|
Post by darrenvox on May 17, 2020 18:35:39 GMT
Thanks for trying to help there Erik .... I believe I've found the/a problem "THIS" .... is actually "MY FAULT" .... and is exemplary of what can happen when I'm suddenly interrupted during file building processes (bloody phone) or through tiredness sometimes when working well into the late hours of any evening/early hours of the morning .... mistakes "can and do" sometimes happen On the basis of the above discovery all one needs to do is edit the TEXTURE FOLDER name (only) to read precisely as follows .... so it then agrees with the FLTSIM.XX based TEXTURE= data line .... duly noted... it does happen when trying to finish a scenetuy or a texture and you forget somethibng, just lije the last few weeks i downloade a lockheed electra varig livery was installing other textures for various aircraft i had downooaded and was wondering why it wasnt loading up propberly and voila just last night i realized the [fltsim] section had not had a number added aftert the dot...and was say9ng XXX and i chagned it and wowo!! syntax is used quite alot here...want to watch out for that, as if you dont marry up each filename you wont see it shwoing up!!
|
|