New FSXBA Hornet

[Panic]

Awesome Thanks for the Update Jimi!! I'm starting to love this legacy hornet over my VRS.....

[micpni]

Little test with VW 360/16kt (No gust) and Boat 020/25kt =>WOD 40kt

http://royalefrenchnavy.restauravia.fr/Test/01.mp4

[KC]

Hello

Great Work

But I found something in combination with the FS Recorder.
The Refueling Probe is in replay always displayed as extended.
Also the hook isn't working and is always up.
In older versions like 15.6 this was never a Problem.
Might this be in combination with the changes in multiplayer use?

Thanks for help

greetings  Cyrill

[bisinchi]

Hi all,

New on this forum, I may have missed info about it, but I downloaded the latest version yesterday, I'm running FSX and have FCS fail written on the HUD and pressing SHIFT F9 confirms that FCS is not loaded properly. Am I missing any step, do the hornetfcs.dll need to be moved to a specific folder?

Great aircraft, congrats to the team for such quality airplane!!

F.

[jimi08]

Hi all,

New on this forum, I may have missed info about it, but I downloaded the latest version yesterday, I'm running FSX and have FCS fail written on the HUD and pressing SHIFT F9 confirms that FCS is not loaded properly. Am I missing any step, do the hornetfcs.dll need to be moved to a specific folder?

Great aircraft, congrats to the team for such quality airplane!!

F.

Hey bisinchi,

What platform are you using (fsx, p3d, P3Dv4)?  Did you use the auto installer?

[PhantomTweak]

Hey Jimi, and all the others on this fantastic Team!
First, wonderful bird, truly wonderful. Flys for a treat! I can finally make some decent traps, which is such a nice change

I think Mr. Bisinchi said he had FSX, no?
I think what may have happened is this: He downloaded and installed the v17.1.31, which has no auto-installer. It's just a zipped up folder with the plane in it. If he just unzipped and installed, could he be missing the .NET Framework file the auto-installer puts in for one?

Which reminds me, is the v17.1.31 and update, that should be ADDED to v17.1.30, over-writing where applicable, or is it a stand-alone install? If it's an update to over-write existing files from the v17.1.30, I messed up. I unzipped and placed it manually, and deleted the v17.1.30. If it's a stand-alone, I'm golden, but maybe you should have made an autoinstaller for it, so that folks just finding this amazing plane will get all the files  they need, where they need them?

I don't know if this is any help, but I hope it is...
Pat☺

[jimi08]

Thought I uploaded the auto installer version.

Please let me know if this is the auto installer. I am away from my computer at the moment and can't confirm myself

https://drive.google.com/file/d/0B3So3WwTLPRZemdlb0ZiYTg4aUk/view?usp=drivesdk

[ctec1]

Yes, the above link points to an auto installer. Your previous link to the new version pointed to a manual install as Pat described.

Thx for the update . 

[micpni]

Using Showmarkers, these values seem to be good... but only for a test.

[tailhook]
tailhook_length = 4.00
tailhook_position = -54.0, 0, -4.0
cable_force_adjust = 1.80

[bisinchi]

Hi all,

New on this forum, I may have missed info about it, but I downloaded the latest version yesterday, I'm running FSX and have FCS fail written on the HUD and pressing SHIFT F9 confirms that FCS is not loaded properly. Am I missing any step, do the hornetfcs.dll need to be moved to a specific folder?

Great aircraft, congrats to the team for such quality airplane!!

F.

Hey bisinchi,

What platform are you using (fsx, p3d, P3Dv4)?  Did you use the auto installer?

Hi, I'm running FSX and I downloaded the file which did not contain an autoinstaller (or I didn't see it). I copied the files onto my FSX simobject/aircraft folder. So seems like I may have missed a .NET environnement that may come with the autoinstall.

François

[PhantomTweak]

Yeah, Francois (sorry I don't have the ability to make that fancy C you used),
I believe that's what happened. You should download the latest posted by Jimi. I has the auto-installer, and will install the correct .NET Framework you need to make everything work. Delete the plane you installed manually, so the auto-installer has a clean slate to work with. Not critical, but it's a good idea, just in case.

A small note about the .NET Framework installer: Sometimes it can SEEM to lock-up, or stop doing anything. It's not locked. Just let it run until it finishes. It can take some time, sometimes (confusing, isn't it?  ), so just go get a cuppa, or take a walk around the block, or whatever. Just leave it alone, and it will do the job. It just can take a while, and look like it's locked up. Just thought you should know.
Other than that, the auto-installer works great. Then go enjoy this wonderful, amazing plane! I know I do 
Pat☺

[Kea]

It's been a while, but for anyone who is interested, updated and corrected Aggressor Hornet paints for the following:

F/A-18C (current 17.1... version) -

NSAWC 22 (standard grey with white "tips")
NSAWC 25 (blue camo scheme)
NSAWC 26 (grey camo scheme)
NSAWC 27 (brown camo scheme)
NSAWC 30 (Persian camo scheme)
NSAWC 31 (blue camo scheme)
NSAWC 32 (standard grey)

F/A-18D (15.6 version) -

NSAWC 00 (standard grey)
NSAWC 02 (brown camo scheme)
VFC-12 12 (SU-34 shark scheme)

Aircraft cfg lines included. Each set uses the fallback texture folder so if you have issues with blank bits, check in the respective model's "texture" folder first for a solution, otherwise sing out if anyone has any issues adding/using these.

https://drive.google.com/open?id=0B_KeMXMmL3b3WlhfUkdrcjFqTDA

Great jet Jimi and co, heartening to see projects like this still alive and well (and free!) for the FSX/P3D community. Long may it last.

[PhantomTweak]

A small detail that's been noted by several: The wing flex no longer functions at all. With or without TACPAC, in FSX, FSX:SE, or P3Dv3.4. I know it's not a big deal, but it would be nice.

Was this disabled on purpose, or is it something that is easily fixed?

Just wanted to let the Team know.
Still a fantastic plane, and getting better all the time! Thanks SO much.
Pat☺

[bisinchi]

Yeah, Francois (sorry I don't have the ability to make that fancy C you used),
I believe that's what happened. You should download the latest posted by Jimi. I has the auto-installer, and will install the correct .NET Framework you need to make everything work. Delete the plane you installed manually, so the auto-installer has a clean slate to work with. Not critical, but it's a good idea, just in case.

A small note about the .NET Framework installer: Sometimes it can SEEM to lock-up, or stop doing anything. It's not locked. Just let it run until it finishes. It can take some time, sometimes (confusing, isn't it?  ), so just go get a cuppa, or take a walk around the block, or whatever. Just leave it alone, and it will do the job. It just can take a while, and look like it's locked up. Just thought you should know.
Other than that, the auto-installer works great. Then go enjoy this wonderful, amazing plane! I know I do 
Pat☺

Got the auto-installer, things seem a bit better, I can see the effects (After burner, cloud above the LEX) and plane flies much better, but still have FCS fail and on the alerts screen (front right of the cockpit, I see FCS hot, not sure what it means). Also, when I load up weapons, I can see centerline tank, sidewinders, and that's pretty much it. Do I need tac pack to see the weapons (I'm not talking firing them as I understand you need tac pack for that). Do I need any additional .NET material?
Anyway, the plane is a fun to fly as it is.
François

[PhantomTweak]

(front right of the cockpit, I see FCS hot, not sure what it means).

Well, hmmm. Let's see...
When you have the FCS HOT warning, are the engines, OR the APU running? If neither, try starting the APU, then starting the engines, and once one is started, try pressing then releasing the FCS RESET button aft of the throttle quadrant, left side. An FCS HOT warning is usually caused by a lack of AVIONICS COOLING air, which is bleed from the engines. I believe the APU can provide cooling air as well, but I may be wrong on that. I'll check the NATOPS, though, and see what it says about it all.

The NATOPS has this to say about FCS HOT:

2.8.2.7.1 FCS HOT Caution. The FCS HOT caution light and FCS HOT caution on the DDI
indicates an overtemperature in FCC A or the right transformer-rectifier.
2.8.2.7.2 FCS or AV COOL Switch
NORM Both FCC and both transformer-rectifiers cooled by avionics air.
EMERG FCC A and right transformer-rectifier cooled by ram air.
FCC B and left transformer-rectifier cooled by avionics air.
Once EMERG selected, selection of NORM does not switch FCC A and right
transformer-rectifier cooling back to avionics air.

So it seems that a lack of cooling air may be the trouble. Try what I said above, and see if it helps. If not, we'll see what else I can dig up. I've never seen that warning, but I never start cold-n-dark, either.
Just a thought: Is your default flight/plane the generic, default Trike over Friday Harbour, or a different plane? If not, try making it so, and see if that has any effect.

Do I need tac pack to see the weapons

No. I tried earlier today, and I could see them all. Try selecting GUNS ONLY first, THEN other weapons and see what shows up. Just a thought.

Hope this helps. If not, we'll keep digging
Pat☺