|
|
Post by lsutigers93 on Aug 22, 2010 4:17:15 GMT
Newbie to the FSX world. Love the forum...
I followed to the letter the original download instructions and cannot see my 707 in the available aircraft screen in FSX. I had the instructions pulled up as I followed them--they seemed easier to follow than the second version--and I do not know what mistake I could have made! I love the older aircraft so any help would be greatly appreciated! Desktop is a stock Dell Inspiron 545--have new graphics card, waiting to obtain uprated power supply.
|
|
|
|
Post by aerofoto - HJG Admin on Aug 22, 2010 12:53:20 GMT
I usually prefer Dan to comment regarding FSX matters .... but .... I'd say, from your description, that it's a very minor CFG editing error which is preventing FS from recognizing/displaying your aircraft of choice.
Check that your first ADD TO AIRCRAFT/CFG entry is edited "0" .... as follows ....
[fltsim.0]
Check that the MODEL line of your CFG is correct for the texture and B707 base pack you're using
Check that the SIM= line of your CFG agrees with the AIR.FILE name.
Check that the TEXTURE= line of your CFG is correct according to the actual texture you're using.
Check that you're using the correct texture/s with the correct B707 aircraft base pack models.
If you're an FSX'er then make sure you've activated the FSX specific FDE too .... since the default activated versions are for FS9 only.
It would also help us "greatly" .... to know "precisely" which B707 version and textures you're trying to install too.
Again .... I'm sure what you're trying to sort out is the result of a very minor CFG editing error !
Mark C
BOG/CO
|
|
|
|
Post by Herman on Aug 22, 2010 16:42:44 GMT
Hmm....could this be the old misleading and "wrong instructions" that I have been complaining about, rearing it's ugly head again and again. ;D ;D ;D
You know the one.... that tells you to re-name the Aircraft FSX file to" Aircraft cfg" when it should only be renamed "Aircraft".
This also applies to the "panel" and "sound "instruction.
Also make sure that if you are using "Vista" that the DX10 prevue is unchecked.
Herman
|
|
|
|
Post by lsutigers93 on Aug 23, 2010 0:15:18 GMT
I usually prefer Dan to comment regarding FSX matters .... but .... I'd say, from your description, that it's a very minor CFG editing error which is preventing FS from recognizing/displaying your aircraft of choice. Check that your first ADD TO AIRCRAFT/CFG entry is edited "0" .... as follows .... [fltsim.0] checkCheck that the MODEL line of your CFG is correct for the texture and B707 base pack you're using checkCheck that the SIM= line of your CFG agrees with the AIR.FILE name. checkCheck that the TEXTURE= line of your CFG is correct according to the actual texture you're using. checkCheck that you're using the correct texture/s with the correct B707 aircraft base pack models. checkIf you're an FSX'er then make sure you've activated the FSX specific FDE too .... since the default activated versions are for FS9 only. what is this??It would also help us "greatly" .... to know "precisely" which B707 version and textures you're trying to install too. HJG B720B Trans World Airlines (1961)twa_b720-051b_n793tw_1961Again .... I'm sure what you're trying to sort out is the result of a very minor CFG editing error ! Mark C BOG/CO |
|
|
|
Post by lsutigers93 on Aug 23, 2010 0:16:07 GMT
Hmm....could this be the old misleading and "wrong instructions" that I have been complaining about, rearing it's ugly head again and again. ;D ;D ;D You know the one.... that tells you to re-name the Aircraft FSX file to" Aircraft cfg" when it should only be renamed "Aircraft". This also applies to the "panel" and "sound "instruction. Also make sure that if you are using "Vista" that the DX10 prevue is unchecked. Herman corrected... |
|
|
|
Post by lsutigers93 on Aug 23, 2010 0:16:27 GMT
I am running Windows 7 Home Premium...
|
|
|
|
Post by lsutigers93 on Aug 23, 2010 0:39:15 GMT
OK...have the airplane available to fly!! No sound though...I can go into C>program files>microsoft games>microsoft flight simulator x>sim objects>airplanes>hjg boeing 720b v7>sound and listen to the sounds...do i make a fsfxconv folder for sound like i did for the panel and change the aliases?
|
|
|
|
Post by Dan K. Hansen on Aug 23, 2010 7:54:38 GMT
Read the instructions  then you should be able to both hear the sounds, see tha panel, and fly the aircraft. Actually I've provided 3 different approaches to install in FSX, all of them valid, so just pick one of them, and run it through step-by step ... that should sort you out ... |
|
|
|
Post by aerofoto - HJG Admin on Aug 23, 2010 13:13:44 GMT
Just a small detail which I'd like to "chime in" regarding here .... It's not that the installation instructioinms are incorrect .... because they're "NOT". I think a problem arises for some folk through interpretation .... and more so because on some PC systems the AIRCRAFT.CFG and AIR.FILE names will appear as follows .... aircraft (for the AIRCRAFT.CFG title) .... and .... B707-320B (for the AIR.FILE title .... this is an example only in the case of B707-320B ADVC) .... whereas on other PC systems these FDE files will appear with their full/extended file names as follows .... aircraft.cfg (for the AIRCRAFT.CFG title) .... and .... B707-320B.air (for the AIR:FILE title) We "must" assume (in order to avoid loosing time   since, for us ;D, this is a hobby only and unfortunately not a full time paid profession  ) that folk undertstand their own PC/FS file structure .... and .... on the basis of our instructions (which I think are pretty clear/adequate) understand precisely "what to do" and "what not to do". I think Dan briefly touched on this in another thread recently on another one of our forum pages and in relation to this subject .... or .... something similar  Mark C BOG/CO |
|
|
|
Post by Herman on Aug 23, 2010 17:18:31 GMT
Gentlemen; I do appologize for my commets about the instructions being wrong, however, I still think that they are misleading because they only cover the one type of file structure. Over the last couple of months there have been at least 3 instances where a problem arose due to this and it was stated by the user that these install instructions should be changed. I personally have used two operating systems (Windows XP and Vista) and both these systems displayed the aircraftcfg file as "aircraft" only. So... perhaps it would be a good idea to add to the install instruction to cover the other possibility??? I can't comment on Windows 7, but perhaps" lsutigers " could let us know what was done "corrected" for the airplane to show in FSX. "lsutigers"...as far as your "sound problem" is concerned there are a few possibilities. The "sound "file in your B720B base pack is aliased by default to the B737-400, so you should be hearing the sound of the 737-400 engines. Make sure that your "Sound" in your FSX options is checked on. You also have the option to install the HJG sounds for the B720B ( found in the download ) section under "Sounds" and as Dan would say "just follow the instructions". Please do let us know how you make out. Herman |
|
|
|
Post by aerofoto - HJG Admin on Aug 23, 2010 17:33:35 GMT
"NO PROBLEM AT ALL" Herman I/we always appreciate your more than positive and helpful contributions to this website Mark C BOG/CO |
|
|
|
Post by Dan K. Hansen on Aug 23, 2010 21:24:19 GMT
If the sound aliases to the B737-400 you sure won't be hearing anything in FSX, as the default B737 is named B737-800 ..... otherwise Herman is quite right.
OK, I'll say it one more time and then I won't say it any more.
Microsoft has "blessed" us by displaying known filetypes without displaying their extensions (or lastname if you will) this is a setting that you can set or "unset" personally I prefer to see the whole filename inclusive the extension, but each to his own.
As the extensions are hidden per default, you have to active set them to be visible.
If you don't know how to do it, Google "show file extensions" and you'll get all the help you want. When I wrote the instructions, I (naively) presumed that people knew that files where made from firstname.lastname. Well apparently they didn't, but alas that's how it goes.
My instructions have now been updated with the following line:
MAKE SURE FILES ARE SHOWN INCLUSIVE THE EXTENSIONS
I hope this will once and for all stop this discussion.
|
|
|
|
Post by lsutigers93 on Aug 24, 2010 1:04:47 GMT
As stated, I'm new to this. I had FS98 (?) on a computer about 10 years ago and before that my main computer (esp. programming) experience was writing simple DOS programs for a Franklin ACE-1000 in 8th grade...so the intricacy is somewhat new to me. In any case I re-installed FSX and will try the "easier" procedure again. In my one 707 flight I did notice that it is a far easier a/c to fly with a yoke/throttle quadrant/pedals instead of my current keyboard/mouse/hand-held controller setup.
I appreciate all the help and will post results when I have time to get this done.
Thanks,
John E.
Louisville, KY USA
|
|
|
|
Post by Herman on Aug 24, 2010 1:42:53 GMT
Sorry Dan...but I only brought this up again because it appeared that John was experiencing the same problem as a few others had....like myself initially, but because I was fairly familiar with "my" FS files I realized that I had to rename my cfg file "Aircraft", and not "Aircraft.cfg"in order for the aircraft to display in FSX.
I admit, when it comes to other than FS matters my computer knowledge is quite limited. I don't recall making any specific choices re- file extentions, so what I ended up with, I guess, were Microsoft default settings.
Hopefully your addition to the installation instruction will solve this problem and no further discussions are necessary.
Herman
|
|
then you should be able to both hear the sounds, see tha panel, and fly the aircraft. Actually I've provided 3 different approaches to install in FSX, all of them valid, so just pick one of them, and run it through step-by step ... that should sort you out ...
since, for us ;D, this is a hobby only 
) that folk undertstand their own PC/FS file structure .... and .... on the basis of our instructions (which I think are pretty clear/adequate) understand precisely "what to do" and "what not to do".