|
|
Post by grayrider on Sept 17, 2010 23:40:03 GMT
Hello all. I'm still at it trying to get at least one acft installed and working in FSX I used your 1st method for installing.The acft.I'm trying to install with one paint is the EC-135 with the Bird of pray paint I downloaded all the necessary files for the plane.The panel I used just to try it is the 707-320 panel. I installed the core pack as well as the effects into the main FSX Guages/sound and effects. I then went to the sim objects/airplanes,and in there I added the new folder FSFSCONV etc.I then dropped the 707-320 panel into it.Than I opened the panel folder and found there were two config's.I re-named both of them as required in the instructions. I then went back to the main aircraft folder and opened the config and changed it to show alias=FSFSCONV\panel.b707-320. I then went and added the texture folder and added the config info as required by the instructions.In this case it's 1. Then I added the sound package to the main aircraft sound folder,which required me to overwrite the sound config. Everything I did was by following the one of the methods instructions etc. When I fired up FSX,there is no HJG acft. showing to even select it Hmmm. As a note.My complete FSX is not on my "C" drive.I have it installed on my "F" drive.This should not be an issue,since when I had FS9 is was installed on another drive as well. I have attached a jpeg of my acft config,because the problem may be there.The texture= matches the texture folder etc. Still need some assistance.I'm trying.Sooner or later I'll find the issues.If I can get one installed,I'll be ably to take off with it and add others THX GrayRider  |
|
|
|
Post by aerofoto - HJG Admin on Sept 18, 2010 0:28:07 GMT
WELL .... all of our aircraft are FSX compatible (with the exception of the BAe 146/ARJ, and CARAVELLE) .... be they port overs or not.
Please pay attention to the excellent installation tutorial provided by Dan .... and posted on this forum page.
A few things I can immediately suggest that you check are as follows ....
Check the CFG.FILE aliasing of both the default PANEL and SOUND folders accompanying each aircraft base pack. These are, intentionally, set up according to default FS2004 conventions which point to the B737-400 .... HOWEVER .... for FSX I believe these need to be edited to read B737-800.
Also .... check that you have activated the FSX version AIR.FILE accompanying each aircraft base pack. Again .... by default .... all of our base pack files download ready for use in FS2004.
Additionally .... check that you are using the right textures with the correct aircraft base packs .... as displayed on our aircraft downloads page sections.
Failure to observe any of these details will result in aircraft not appearing within the FS Aircraft Selection Menu.
"FAILING ALL OF THIS" .... kindly refer to Dan's excellent FSX installtion tutorials as requested.
Mark C
BOG/CO
|
|
|
|
Post by Dan K. Hansen on Sept 18, 2010 1:50:21 GMT
Im sure it is some kind of alias error, it most usually is
|
|
|
|
Post by grayrider on Sept 18, 2010 1:55:21 GMT
I re-checked the EC-135 base pack.In it there are 5 models/1 panel/1 sound folder.There 2 config files and 1 air file.
I'm not sure what you mean by activating the FSX version air.file.In the EC-135 base package,there is only one air.file to use,unless there should be two air.files one for FS( and one for FSX??.
I already aliased the panel config to alias=FSFSCONV\panel.b707-320
I down loaded the TF-33 sound set I wanted,and copied the contents in the sound folder,and over wrote the sound config that was in it,which was defailt.
I am using the correct texture.The paint texture I downloaded is is for this base package.In it there are five EC-135 models etc.I downloaded the texture for the EC-135E model.
I was using the first of Dan's tutorials as a guide.So unless someone may see something in my screenshot that isn't correct.I'm not sure what the Issue is.Not yet anyway.
The only thing I aliased was the panel I'm using and I did add the new folder FSFSCONV into my Sim Objects/Airplane folders.The panel is in it,and I did change the config's as required,following the panel install procedure etc.
GrayRider
|
|
|
|
Post by bluestar on Sept 18, 2010 3:23:00 GMT
There should be something after b707-320. I use the 320b so my "alias" looks this:
"alias=fsfsconv\panel.b707-320badv.1970"
I do not see anything after b707-320. The alias must match the panel file name in "fsfsconv" exactly.
Bill
|
|
|
|
Post by Herman on Sept 18, 2010 3:30:08 GMT
Hello GrayRider;
This issue seems to come up very frequently.
It somehow seems to depend how your file extensions are set up.
On my system ( Vista ) I have to rename the aircraft.cfg to aircraft, only,not aircraft.cfg.
The same applies to the panel cfg. ...panel only not panel.cfg
The same applies to the sound cfg.
There is only one air file.
I think what Mark meant is to make sure you use the FSX aircraft , panel and sound cfg files.
Also make sure the DX10 prevue in FSX is unchecked.
Give that a try and let us know how you make out.
Cheers; Herman
|
|
|
|
Post by grayrider on Sept 18, 2010 5:39:05 GMT
Based on Bluestars reply.
I went back to the downloads.I went to the boeing core and panel files.
Looking thru them there are three or four b707-320 panels that can be used.The one I chose was the first one which is the b707-320.The next one down is the b707-320b panel.Below the 320b panel,there is a couple more,advanced type etc.
I put in the first one,which is the b707-320.When I extracted the panel to a temp folder,the panel is called panel.b707-320.I put that panel in the FSFSCONV folder.I then went to the aircraft folder and opened the panel folder and aliased the config to alias=fsfsconv\panel.b707-320 and it does match.
I am running Windows 7 Pro and I don't have DX10 or run Vista.
If my problem has something to do with an alias error.I have no Idea what to do next or try etc.
Maybe someone could look in the panel downloads,and look at the plain b707-320 panel I downloaded and extract it to a temp folder and have a look at what the extracted panel folder is called,and go from there.
GrayRider
|
|
|
|
Post by aerofoto - HJG Admin on Sept 18, 2010 13:05:28 GMT
I must defer to our FSX gurus to provide more precise instruction (beyond what's already provided on this forum page) in regard to that FS version and since I'm FS2004 .... HOWEVER .... I can advise as follows and if it will help ....
I note you're using the EC135-E and -C aircraft. Please note, from th following quoted list, our recommended panel assignments for all of the military C135 CLASS aircraft ....
Any panel change from what you currently have to the above recommendations will not affect your gauges set .... since the gauges for all of these panels are contained within the 3 separate files provided within the B707 PANEL GAUGES CORE FILES package .... and precisely the same also applies to the PANEL SOUNDS as well.
That's correct if he was using the default panel and sound asignments and which would then require editing the PANEL.CFG and SOUND.CFG (using Notepad) to read "B737-800" rather than the current B737-400 assignment for these particular CFG files .... HOWEVER .... since he's trying to install the recommended B707 panel and soundpacks then this cross-check and edit is automatically anulled. If the "SOUND" folder from his selected soundpack has been installed inside his EC135 aircraft base pack (replacing the default Sound folder) .... then that's fine .... and as things should be. If he's got his recommended B707 panel installed inside the "FSFSCONV" folder .... then that's fine also .... and then all he's got do do here is check that the ALIAS= data on the CFG file in his default Panel folder is edited correctly/precisely acording to the new FSFSFCONV panel assignment.
It then remains to check the following ....
1. Check that the ADD TO AIRCRAFT/CFG data is correct according to the SIM=, MODEL=, and TEXTURE= data .... and in relation to the files provided within the aircraft base pack .... or .... in the case of the add-on textures those files selected.
2. If installing these files in FSX .... he needs to do 2 more things also ....
- Open the selected B707 panel folder. Dump the PANEL.CFG named "PANEL" (only). Identify the 2nd PANEL.CFG provided (which should be named PANEL.FSX or something like that) and rename it to read "PANEL.CFG" .... in place of the FS2004 version which should have been dumped as indicated above.
- Open the EC135 aircraft base pack folder. Dump the AIRCRAFT.CFG named "AIRCRAFT" (only). Identify the 2nd AIRCRAFT.CFG provided (which should be named AIRCRAFT.FSX or something like that) and rename it to read "AIRCRAFT.CFG" .... in place of the FS2004 version which should have been dumped as indicated above.
See how you go with this.
Any further lack of co-operation by your selected aircraft in relation to its apprearance within the FS Aircraft Selection Menue is then bound to be the result of yet another remaining (or still miisunderstood/incomplete) ALIAS= error !!!!
Sorry about the length here .... but .... I'd sooner/rather make things long and drawn-out afairs simply so as to try'n be "AS CLEAR AS POSSIBLE" !
Mark C
BOG/CO
|
|
|
|
Post by grayrider on Sept 18, 2010 17:03:17 GMT
From my last reply from Mark.Here are some other shots of the plane I'm trying to install into my FSX etc. Maybe some one will see an error in some of these new shots,installing the EC-135E with one paint       In the acft and panel config's.I did use the one related to and for FSX users.I did dump the one's related to FS9,and re-named both config's, to panel.cfg and aircraft.cfg which you will see in the screen shots. I think maybe the problem is inside the aircraft config itself,but I don't see a problem in there if there is one. I am trying though.I really miss these HJG Airforce planes and the 727's,when I had them in my FS9,but thats long gone. GrayRider |
|
|
|
Post by Dan K. Hansen on Sept 18, 2010 17:21:21 GMT
I've just send you a PM grayrider.
|
|
|
|
Post by grayrider on Sept 18, 2010 20:38:42 GMT
I replied to your PM Dan
GrayRider
|
|
|
|
Post by Herman on Sept 19, 2010 0:03:48 GMT
Hello grayrider;
Once you get everything sorted out, and your aircraft is available to fly in FSX, I would appreciate it very much, if you could let me know, exactly what you had to do.
Thank you, Herman
|
|
|
|
Post by grayrider on Sept 19, 2010 0:22:21 GMT
I'm still playing with it,in the meantime.Based on the reply's it must be a config entry somewhere,so I'm not sure I'll ever find it.I've been trying to install just one plane into my FSX for the past two months,and it still won't show up to fly it.I have been using one of the three guides listed.
I even printed the guide out etc.
I'll let you know,and what was done,if I get to that point.
If I can get one installed and working,than I can go after the rest of the planes I used to have when I had FS9 installed.
GrayRider
|
|
|
|
Post by Herman on Sept 19, 2010 1:10:50 GMT
Have you tried the method that I outlined with regards to you renaming your your aircraft. cfg and your panel cfg to aircraft only and your panel.cfg to....aircraft... only and ...panel... only.
That is what I needed to do in order for my aircraft to show in FSX.
Try it...you have nothing to loose if it does'nt work.
I looked at all your file screen shots and everything looks OK to me.
Herman
|
|
|
|
Post by aerofoto - HJG Admin on Sept 19, 2010 1:23:06 GMT
Again .... apart from making "SUGGESTIONS" .... I'd rather leave this issue for the FSX gurus to try'n resolve .... HOWEVER .... I did notice in 1 of your above screenshots that your FSFSCONV folder appears in capital font .... whereas the ALIAS= data line in you PANEL.CFG displays this folder name in lower case font (i.e "fsfsconv"). What happens if you then edit that data line to show just the FSFSCONV (only) portion of that reference in capital font .... as per the actual folder name (i.e "FSFSCONV"). The rest of that data line can then stay in lower case font .... as-is .... as that's still consistent with the panel folder name. This suggestion might not make a shread of difference though  I know it doesn't in my FS2004 installation .... but .... maybe  .... FSX is a little more sensitive in this respect .... and it certainly won't hurt to try  .... I guess !  Beyond this final suggestion, from me, I'm out of my depth here .... and, again, need to leave you with the FSX gurus ! Mark C BOG/CO |
|
.... FSX is a little more sensitive in this respect 
.... I guess ! 