FSDreamTeam forum
General Category => Unofficial F/A-18 Acceleration Pack board => Topic started by: jimi08 on September 19, 2017, 12:46:07 am
-
2018 FSX BLUE ANGELS F/A-18C HORNET
DEVELOPER NOTES:
LATEST NEWS:
-16 SEP 2018: Hey everyone. Just a quick update. First of all, thanks for all of the sound feedback on the latest release. It has become quickly apparent that although much has been added to the jet, it still isn't quite ready for prime time yet. There are still many things to fix and tweak. Because of that, I'm going to re-title this 18.4 as a "Prototype" or "Test" version for those to check out and test and re-name the 18.3 as the latest stable release until I get the 18.4 smoothened out. Thanks again everyone for the support and understanding.
-31 AUG 2018: Hey everyone. I know it's been a while and a little quiet, but I assure you steady progress has been made on the jet. This update comes with a fair amount of fixes for noted problems as well as a few new features, in particular the TACPACKers. A LOT of coding rework was done on this version, so I have to warn you that there may be a few new bugs in this version compared to older ones. But this version is definitely a push forward none-the-less.
(https://i.imgur.com/dgVtyE1.png?1)
New RADAR & Forward Looking InfraRed (FLIR) Display
(https://i.imgur.com/zaFyRdG.png?1)
New Electronic Warfare (EW) & RADAR Warning Receiver (RWR) Displays
(https://i.imgur.com/td9Bgt7.png?1)
New Helmet Mounted Display (HMD)
New features include:
1. RADIOS: A lot of work has been done on revamping both the COM and NAV radios to have better functionality. The new radios allow both VORTAC Freqs as well as TACAN channels to be entered and tuned. ILS needles and CRS arrows have been fixed as well. This includes both land and carrier ops.
***With the new radios, please note that you will have to first turn on the NAV & ILS radios before you can set frequencies. This is done by using the ON/OFF button located at the bottom of the UFC, opposite of the AP button. The ON/OFF status of the radio is indicated in the scratchpad as "ON" for on and "OF" for off.***
2. AUTOPILOT: Autopilot functionality has been adjusted. Still working on it though...
3. TACPACK Stores Management System (SMS) (TACPACK ONLY): Both the SMS display and Fire control system has been redone to closer match the real deal and for smoother and more consistent operation. User now has the option to select between HI and LO gun rate via DDI display. Framework has been set up for future weapon deployment options and details.
4. DDI Menu Layout: New DDI Menu hierarchy has been implemented. Displays are now divided into two primary menu pages, the "TAC" page that display all tactical related displays, and the "SUPT" for support related displays. The user can switch between TAC and SUPT menus by first pressing MENU at the bottom center of the DDI and then pressing MENU again to switch from one to another. Please not that "MENU" lettering changes to local zulu time (minutes and seconds) once airborne. Menu functionality however, still remains the same.
5. RADAR WARNING RECEIVER (RWR) (FSX TACPACK ONLY): New RADAR Warning Receiver (RWR) has been implemented on the circular scope just below the right DDI. As most of you know, it's purpose is to warn of incoming threats by displaying icons on the display based on the azimuth of the threat and priority, which determines which ring in which the threat is displayed. Although functional, this new feature is still being tweaked.
6. Electronic Warfare (EW) (FSX TACPACK ONLY): Also new and using the same logic as the RWR, is the new Electronic Warfare (EW) Page which shows same info as RWR but on DDI along with Chaff/Flare status and option to arm Jammer. The EW page can be selected by selecting the "EW" option on the TAC menu.
7. Forward Looking Infra Red (FLIR) Display: New (and basic) Forward Looking Infrared (FLIR) capability added to the jet. Please note that it is in its infant stages of development currently, and has the following restrictions:
-The FLIR display only shows on the Right DDI due to coding limitations from VRS.
-Both the ASQ-228 must be selected from the Payload Manager (Shift + 7) and the FLIR switches much be on for the display to be shown. The switches are located on the right, rear panel (where your right hip would be).
-Basic functionality has been built into the display such as contrast, brightness, zoom and polarization. These options are displayed on the right DDI within the FLIR Display.
-Currently, the FLIR camera is set to automatically point to whatever ground contact you have selected on your RADAR through the use of the "TUP" and "TDN" options. There is no option to independently move or slew the camera as of this time.
8. Helmet Mounted Display (HMD) (FSX TACPACK ONLY): Just as new for the jet is again, a very basic Helmet Mounted Display As of now, it just displays basic HUD info. The HMD can be activated and deactivated by clicking on the small knob titled "HMD" located just above the stripped "SPIN RCVY" switch, which can be found on the right side of the right DDI.
9. FUEL SYSTEM: New fuel system actually takes into account whether or not external fuel tanks are hung on the jet and adds/subtracts fuel accordingly
10. TMAP RADAR (TACPACK ONLY): New TMAP Radar installed on the aircraft that brings better capability for TACPACK operations. Working modes include a basic Air to Air Mode, as well as MAP, GMT and SEA Air to Ground Modes. Please note the following with this new RADAR:
-Tracks a maximum of 8 targets at a time, depending on which mode is selected. RWS (AA), MAP (AG), GMT (AG) and SEA (AG) modes all track up to 8 contacts simultaneously. TWS (AA) tracks up to 4 contacts at once, while ST (AA) tracks only one.
-Contacts shown can be cycled through by pressing the TUP and TDN options located on the right side of the display. Once selected, a bracket will appear around the contact, as well as the contacts altitude (in thousands of feet), airspeed (in mach) and a tail indicating the heading in which the contact is headed.
11. FCS RESET BUTTON: The FCS Reset button on the left panel is now functional. Once pressed, all of the Proportional Integral Derivative (PID) Devices that controls the aircraft's Flight Control System (FCS) are momentarily blanked and reset. This is useful for uncommanded pitch, roll or yaw oscillations encountered while in flight where the FCS starts to go wonky.
12. TEXTURES: Updated cockpit and canopy textures. Thanks Kea and Ed!
Well those are the biggies. Bunch of other smaller fixes and adds. Big thanks goes to Corrado, Dino Cattaneo, Pat (PhantomTweak), Kea and Ed for all the updates, textures, help and testing!
As usual, I'm always open for comments, discoveries, recommendations and feedback. I've provided an autoinstaller this time. Should be easier and more straightforward to install.
And......and....as usual.....don't ask about the Delta (two-seater) version.
2018 FSX BLUE ANGELS F/A-18C HORNET
LATEST FSX VERSION DOWNLOAD LINK:
FSXBA F/A-18C Hornet ver. 18.3 link (as of 5 MAY 2018): https://drive.google.com/open?id=1wpfjdjyaaLfuDdxOMk7VLdVrG0koa2jM
LATEST P3Dv4 VERSION DOWNLOAD LINK:
FSXBA F/A-18C Hornet ver. 18.3 link (as of 5 MAY 2018): https://drive.google.com/open?id=1cxJ3_NdSO-dLhFN9Y2jVc3XxMuEyaF54
PREVIOUS FSX VERSION DOWNLOAD LINKS:
FSXBA F/A-18C Hornet ver. 17.31 link (as of 5 SEP 2017): https://drive.google.com/file/d/0B3So3WwTLPRZemdlb0ZiYTg4aUk/view?usp=drivesdk
PREVIOUS P3Dv4 VERSION DOWNLOAD LINKS:
FSXBA F/A-18C Hornet ver. 18.2 link (as of 4 APR 2018): https://drive.google.com/open?id=1cKFVqr_yBHzlTwlKEvq5Z2hEmanTk99t
FSXBA F/A-18C Hornet ver. 18.1 link (as of 4 MAR 2018): https://drive.google.com/open?id=1SmfnVagsNYlpHVgjqjDq1VdleK4n_-SD
LATEST PROTOTYPE/TEST VERSION DOWNLOAD LINK:
FSXBA F/A-18C Hornet ver. 18.4 (FSX) link (as of 31 AUGUST 2018): https://drive.google.com/open?id=1Qn3y2uldzgZrPJbth2uW9S5GlgrBiykh
FSXBA F/A-18C Hornet ver. 18.4 (P3Dv4)link (as of 31 AUGUST 2018): https://drive.google.com/open?id=1FF6uavVqDkpSPRkWk9DjYM--dhF_LkyO
(http://i.imgur.com/mxeG2dYl.png)
(http://i.imgur.com/vkTo9XYl.png)
(http://i.imgur.com/rHFdzGcl.png)
A BUNCH OF CHANGES since the 16.1 release! Changes include, but certainly not limited to:
1. FCS & Flight Characteristics: Thanks goes out to ORION and ROY HOLMES for their help here!
--UA & PA Mode Blending: In the previous model, there was a notching or jerking that would occur when flight control logic was transitioning from Powered Approach to Up and Away, or vice versa. This has since been remedied thanks to ORION. The system now smoothly transitions from one mode to the other. If flaps and gear are lowered at approximately the same time, the system will automatically trim the jet to 8.1 once airspeed is within 30 KIAS of calculated landing speed. Once automatically set to 8.1, the pilot is free to reset the trim as he/she sees fit. If gear and flaps are lowered at different times, the autotrim to 8.1 will not occur and the pilot is free to set the trim as he/she sees fit. AUTO FLAP operation has been tweaked to better account for variances in the aircraft's speed.
(http://i.imgur.com/HCoHUFUl.png)
--Available for P3Dv4: In addition to the aforementioned, ORION has recompiled the FCS.dll to work for P3Dv4 as well! Unfortunately, avionics still do not work. Recoding avionics in currently in progress...
--Engine Performance Update: Working with ROY HOLMES, we were able to more accurately reflect engine performance at both low altitude (sea level) and at high altitude (36,000 ft)
2. 3D MODEL: Because of the great work and contributions of CORRADO and KEA, we have made some long awaited and significant strides in the project regarding both the 3D model of the jet and TACPACK integration. Because of their work, we were able to accomplish the following...
(http://i.imgur.com/FRXFVjql.png)
(http://i.imgur.com/vM1xza5l.png)
--Payload Configurator: A payload configurator is now available for the jet! Although it works jets (except for the Blue Angel variants) with or without TACPACK, you will need TACPACK in order to release the missiles, bombs or rockets. The configurator is accessible by pressing Shift+7. You will need to click the "GUNS ONLY" option in order to show the pylons, then you can simply click on which stores you want on the jet. Although stores weight hasn't been adjusted for non TACPACKed aircraft, drag is. You should notice that more power is required to fly equivalent airspeeds depending on what you have attached to the jet.
(http://i.imgur.com/eM4m5CJl.png)
--Weapons Viewable From Inside Cockpit: In addition to seeing ordnance from the exterior, you can now see the ordnance from inside the cockpit as well!
(http://i.imgur.com/HlQSeIOl.png)
--Viewable In Multiplayer: Tail hook, Wing fold and Refueling Probe from other FSXBA F/A-18C Hornets are all now visible in multiplayer.
(http://i.imgur.com/4sOArdpl.png)
--Blue Angels Gloss Textures: High gloss textures have been implemented on the Blue Angels variants of the jet thanks to CORRADO.
(http://i.imgur.com/E88BLPol.png)
3. AVIONICS: We are currently starting the lengthy and painful process of transitioning the avionics of the aircraft from those used on the Acceleration F/A-18. This is mainly due to the incompatibility of the existing avionics with newer versions of P3D and Flight Sim World and the increasing functionality of the jet that needs to be integrated into the jet's avionics.
--SMS Page: A new SMS page has been upgraded, so that players can now see what stores they have loaded on the aircraft, in addition to having the ability to select and arm the ordnance that they would like to employ for those who have TACPACK installed. This now page is available by pressing the "MENU" button at the bottom of the Left or Right DDI, then pressing the button next to "SMS".
--FCS Page: A new SMS page has also been added as well. It reflects the basic FCS readouts for the flight control surfaces. It can be accessed by pressing the "MENU" button and then pressing the bottom button on the right column of buttons on the left or right DDI (FCS option is not labeled on MENU page).
--ENG RPM Readout: Engine MIL and Afterburner RPM has been adjusted to better reflect throughout altitude envelope.
(http://i.imgur.com/mLVETrKl.png)
4. GAUGES: Updated a few gauges...
--Carrier Landing & Refueling Gauges: Now automatically pop up when either the hook is lowered or the probe is extended respectively. The Carrier Landing Gauge has been reorganized to better work and display in conjunction with other gauges.
--FCS Gauges: The two FCS gauges that were originally assigned to Shift+7 and Shift+9 have been consolidated and assigned to Shift+9.
--Audio Warnings: Thanks to RAZOR, new audio warnings have been added such as "Roll Left/Right" warnings which are transmitted when the aircraft is at a low altitude with excessive bank, a radio chime has been added once the battery is turned on, and updated audio warning cycle has been included with is triggered by the "LIGHT TEST" switch on the right panel.
5. TEXTURES:
--Thanks to the contributions of GROOM LAKE SIMULATIONS and a few others, we now have over 80 great textures for the jets!
(http://i.imgur.com/raMlMZel.png)
6. OTHER:
--Functional Checklist: Thanks to HENRY from cNATRA who has included a new functional check list for the jet.
(http://i.imgur.com/NVYWUC1l.png)
7. STILL TO FIX: There are still a few things that we are working on that we know are messed up. Those include:
-ANIMATIONS: Throughout our work on the 3D models some animations were lost such as the Throttle Cutoff animations. Working to get those working again.
-AVIONICS IN P3Dv4: As mentioned earlier, many of the avionic displays are no longer functioning in the new, 64-bit FSX based simulators such as P3Dv4 and FSW. We have started the process of updating the avionics so that they will eventually work on those platforms. Currently no ETA on when they will be complete though.
-FIRE CONTROL: Although the fire control system does work for TACPACK, there are still some glitches here and there. Still working to fix.
-ADDITIONAL FUEL WITH DROP TANKS: Still working on being able to have additional fuel when adding drop tanks.
As usual, if you see anything, report it! I'll be out of pocket for major changes for the next couple of months, but will get back to it once I'm able.
Thanks!
Version 17.1.31 Addresses the following:
1. Tailhook for Fleet Version: Clicking on Tailhook in Virtual Cockpit of Fleet jet now functional.
2. Tailhook/Probe Issue for Blue Angels Version: Tailhook and Refueling Probe now work correctly in Blue Angels variant. Wing fold still an issue.
3. Updated Textures: All textures have been updated to include air intake and pylon graphic details.
....and NO, I have NO updates or info on the Delta/Two-Seater version, so don't ask...
-
I'll update this post with any NOTAMs or FAQs regarding the FCS gauge too.
-
Still loving this latest version. It gets better and better. Still a few minor things need to be fixed, but other than that...
Jimi, hope you have a great PCS experience. It doesn't seem hardly a month ago you PCS'd to Hawaii! Enjoy your time in Italy. Lots of touristy kinda spots to see there. History up the yin-yang...
Hope you family does well, too.
Looking forward to seeing you back hard at work on this incredible bird. No rest for the weary, is there?
Orion: Good to hear from you. Seems like it's been a while. Hope you and yours are doing well.
Pat☺
-
Gents,
-I've decided to start a new thread so I can have a little more control over posting and updating the tread. All updates for the project will be posted here. Please post inputs and feedback here as well. Thanks.
LATEST NEWS:
-One of the more enjoyable (or painful) aspects of being active duty military, is that you have to PCS (Permanent Change of Station) from time to time. I am currently in the process of moving from Hawaii to Italy, and my household goods (gaming/coding computer included) isn't scheduled to make it to Italy until mid-December. That being said, expect slow progress on the jet as I will not be able to make many changes, updates or fixes to the project until then.
-P3Dv4 Version still in progress.
-Don't ask about the Delta (two-seater) version.
2017 FSX BLUE ANGELS F/A-18C HORNET
LATEST VERSION DOWNLOAD LINK:
FSXBA F/A-18C Hornet ver. 17.31 link (as of 5 SEP 2017): https://drive.google.com/open?id=0B3So3WwTLPRZcHVKUVczdm53Z1k
Just a heads up on that link for the new version posted above. The link above points to a manual install not the auto installer. Not sure if Jimi intended to link to the manual install or auto installer. Just FYI.
-
Just a heads up on that link for the new version posted above. The link above points to a manual install not the auto installer. Not sure if Jimi intended to link to the manual install or auto installer. Just FYI.
Should be fixed now. Thanks for the heads up.
Jimi
-
Still loving this latest version. It gets better and better. Still a few minor things need to be fixed, but other than that...
Jimi, hope you have a great PCS experience. It doesn't seem hardly a month ago you PCS'd to Hawaii! Enjoy your time in Italy. Lots of touristy kinda spots to see there. History up the yin-yang...
Hope you family does well, too.
Looking forward to seeing you back hard at work on this incredible bird. No rest for the weary, is there?
Orion: Good to hear from you. Seems like it's been a while. Hope you and yours are doing well.
Pat☺
Thanks for the good words Pat!
-
Wow, tough duty going from Hawaii to Italy, guess I was in the wrong rate/branch or air wing guys just don't have it as good as we thought! Looking forward to more Tacpack testing in the future with this model.
-
Thanks for the good words Pat!
My pleasure!
Wow, tough duty going from Hawaii to Italy, guess I was in the wrong rate/branch or air wing guys just don't have it as good as we thought! Looking forward to more Tacpack testing in the future with this model.
I don't want to hear about it! I was stuck in YUMA, a place I despise, for 7 of my 10 years. And I was on det for 6 months of my last year, which was in beautiful Beaufort by the Sea. My first 2 were in Millington, TN, going to school. And a little time in El Toro, CA, waiting for PCS assignment.
Then I went back to Yuma, after I got out. For another 20 years...
Hated every minute, but I had property by then, and a family to raise, so I stuck it out.
So yeah, I understand "Wrong rate or airwing"!
Jimi's lucky. He's going to see some beautiful places, and already has. My father was a UAL pilot, and we did a lot of traveling as I was growing up. More than the rest of my life :D
Have fun all!
Back to the wonderful aircraft :)
Pat☺
-
Some of the cockpit sounds don't work for me in P3Dv4, for example the high AoA sound, AoA.wav. I definitely had at least some more sounds working in P3Dv3 and years ago in FSX. Also I'm getting a lot of tail wagging with the rudder with this current version (17.1.31). Regardless, great work on this jet!
-
Awesome, Can't wait to test this out. Thanks.... ;D
-
Just install newest ver of FA18C in P3DV4. Attempted to follow all the "fixes" for the 64 bit system but still no DDI's. Is that normal for this stage of development?
-
Just install newest ver of FA18C in P3DV4. Attempted to follow all the "fixes" for the 64 bit system but still no DDI's. Is that normal for this stage of development?
Believe so for now
-
Is there a way for me to change the blackout effect, or raise the G-limit where it occurs in the cfg? Doing a loop at 5 G and everything goes black, stays like that uncomfortably long. Is this supposed to be realistic?
Would also like to change the in-cockpit turbine sound or lack of, there is no change of pitch with throttle changes. Sounds great outside the aircraft.
-
As to whether you can alter the in-built G effect: No, there's no way I ever heard about to change the effect of the values there-of.
As to the cockpit turbine sound: Yes you can. I believe you need to either edit the turbine's .wav file, or the sound.cfg file in the Plane's Sound folder. I'll check up on that some more and let you know more as soon as I can, ok? I'm no sounds expert, but heck, can't hurt to learn new stuff :D
Pat☺
Late Edit: Ok, I figured it out. There are two things you can do. Whichever you prefer. The easy, simple thing to do is to go to Settings>Sound> Cockpit, and run the slider up a ways. See what effect that has. If it's enough, then you're good to go. If not, well, ....
Second way you can do it is to get into the sound.cfg and change some settings. If you want to try that, I can show you what needs to be done, but I suggest the slider method first. MUCH easier and simpler.
Pat☺
-
Turning up the sound isn't the issue. It sounds like a monotone APU in the cockpit, not like I'm strapped onto 2 F404's. I would like to hear the change in engine tone and pitch when modulating the throttles. View outside the aircraft sounds great, it would just have to be less volume in the cockpit. I would like to change the sound.cfg, just can't tell which section or what values to change.
Back to the G effect issue. What is going on here? Is no one else perplexed by this? Has the F-18 been downgraded to a 5G limit, or is this some Blue Angels customized setting because they don't wear G-suits. I black out at the top of my loop, stays that way for 10 seconds until the jet completes the loop and is heading back up the vertical. I've been reading about this F-18 for quite some time, with all the work done and experts contributing to the flight model. But this..its beyond words.. frankly.
-
I don't have time this second to run through the Sound.cfg file settings you need to change, but I'll do a write-up tomorow morning PDT, if that's OK.
As to the G situation: It's not this plane, it's integral (big word for the day :D ) to FSX. You'll get the same G effects whatever plane you're in. Give it a try in one of Dino's plane's if you don't believe me, or a WWII fighter, like the SOH F7F-3. You pull 5 G in any plane, you're going to black out. Nothing to be done about it, as far as I know, since Microsoft no longer supports FSX. You'll just have to keep and eye on the G meter displayed in the HUD, and if it get's much above 4, relax your pull a little.
Realistic? No, not really, especially in planes like the F-16, with it's laid-back seat, and these days of pilots being in much better shape than WWII, when they thought a pilots worth lay in how much he could drink, AND how many he shot down. But it's the way the sim is, live with it or not, it's up to you. I do, because I've learned to just relax a little, or just wait for the black to fade out. It's not a perfect solution, but it's the best I can offer. But it's not just the FSX BA plane.
A small trick with FSX BA F/A-18 you can try is to call up SHFT-8, and try using the info it provides to fly the plane with, until the black fades out. With Dino's planes, you can call up an PFD as a pop-up, and I think it'll stay even if you G-LOC, so you can fly with it. I'll double check tonight to let you know.
Hope this helps a little. I'll put the Sound.cfg up tomorrow if you want.
Pat☺
EDIT: Ok, I checked Dino's F-14, and I was right. You can pop-up a PFD, actually an MFD with a PFD displayed on it, and if/when you G-LOC, or at least simulated G-LOC, you can fly the plane with it. It stays displayed normally, even when the rest blanks with the G effect. I'll wager his T-45 has the same thing. One thing about the PFD, though: It displays the horizon a bit higher than it should. Doesn't match the HUD exactly. You need to put the waterline on it about 1° below the horizon to get a 0 vertical speed.
Thought you might like to know.
If you wanted, you could probably make a similar set-up in the Hornet. Just make an MFD a pop-up in the 2D panel, set it as a HUD repeater or PFD and then pull all the G you want. The plane can take more than you can :D
Just don't fold the wings up. Makes ejection a triffle tough...
Pat☺
-
Thank you for the info, whenever you have time to write up that sound.cfg mod will be fine. When you said the G-effect is integral to FSX..I had a moment! I never experienced this with other jets in my fleet. But, I recently built a high end system and upgraded my SP2 FSX to Acceleration. I have been doing mostly air base design work with some test flying..solely using this F-18. Looked in my FSX settings/realism, and there it was in special effects..G-effects. De-selected it and went out and did some 7.5 G maneuvers..Sweet. Issue solved.
-
Well, I am glad you got the G effect sorted! I never thought about turning it off. I was thinking in terms of changing the values :)
As to the Sound.cfg: I'm afraid real life is getting in the way right at the moment. I'll write it up just as soon as I can. Maybe tonight, or tomorrow AM. My lovely wife and her honey-do's come first :D
Enjoy! I sure do :D
Pat☺
-
jimi08, I'm working closely with Haze Gray Studios (http://www.hazegraystudios.com) in developing Fleet Traffic: US Navy. We're just about ready to release into the world having the modern US Navy fleet in FSX & P3D. OK to please use your Hornet in our promo video?
Joe A. Kunzler
growlernoise@gmail.com
-
jimi08, I'm working closely with Haze Gray Studios (http://www.hazegraystudios.com) in developing Fleet Traffic: US Navy. We're just about ready to release into the world having the modern US Navy fleet in FSX & P3D. OK to please use your Hornet in our promo video?
Joe A. Kunzler
growlernoise@gmail.com
My bet he is not going to have a problem with it. Is it freeware or payware?
-
Joe,
Awesome and permission granted! Good luck with your product!
jimi08, I'm working closely with Haze Gray Studios (http://www.hazegraystudios.com) in developing Fleet Traffic: US Navy. We're just about ready to release into the world having the modern US Navy fleet in FSX & P3D. OK to please use your Hornet in our promo video?
Joe A. Kunzler
growlernoise@gmail.com
My bet he is not going to have a problem with it. Is it freeware or payware?
-
OK. A quick How-to on changing how the sounds "appear" in the cockpit, vice the outside view.
I apologize if anything is over-explained, or stuff you already know, but better too much info than not enough.
First, always, ALWAYS make a back-up of ANY file you're going to edit BEFORE you start. This is vital, in case things go totally south, so you can return things to a starting point. Make another back-up for every time you change something, so you don't have to start over from a point long behind you.
Second, ONLY open .cfg files with NotePad, included with Windows. Other word processors add symbols to the files which make them useless to the sim.
Go to the \sound folder of the plane you want to change. Like D:\steam\steamapps\common\FSX\SimObjects\Airplanes\FA-18C_FSXBA_BA_17.1.31\sound , just for example. Open the sound.cfg file. Here's where it get's complicated, although not too much.
Look down through the file for the kind of sound you want to change. You specified the jet whine, so in this case, look down through the various sections for things like this: [whine_12]
Under that heading, look for a line that reads: viewpoint=1 Note the number 1. This indicates "inside the cockpit" type of view point.
Once you've found a section with those two conditions met, look for the line in that section:
vparams=0.00,0.00,0.21,0.00,0.27,17.00,0.35,18.00,0.40,7.00,0.50,0.00,1.00,0.00,1.00,0.00
This line is made up of 5 pairs of values. The first in each pair is the point in the variable's range and the second is the relative sound volume.
The second value is a percentage. Anything over 1.0, or 100% is read as a 1, again, 100%. Can't go higher than that. Change the second value of each pair up by a certain amount. Say .05 or there-abouts. Only change ONE vparams line at a time, so you can keep track of the changes you've made.
NOTE: you can play the sound the sound.cfg calls out to see if is what you might want. In this case, the file called for in the specified section is filename=x_whine_12 . Just look in the \Sound folder for that file, and double click on it. Windows will play the sound file with that name for you, so you can hear it. Handy to preview a sound file to see if it's the one you want.
Save the file off, reload the plane, and test to see how it sounds to you. You can close the file, or leave it open for editing, as long as you make certain it gets saved off.
A good way to reload the plane is to assign a key to "Reload User Aircraft".
NOTE: If you are going to use this key assignment, you need to make sure ALL AI traffic sliders are full left, or zero percent. If there are AI craft present in the world, whether aircraft, boats, cars, whatever, it can have haphazard, unpredictable effects on the reloading of your aircraft.
Another way is to select another aircraft from the normal pull-down menu. Not just another paint of the same plane, but a totally different aircraft. Like go from the F/A-18 to a Cessna 175, and then back again.
Finally, you can also select End Flight, let it exit out to the Free Flight screen, and then back in again.
This takes a little time to accomplish, but it will achieve the desired results.
Sorry I took so long to get it posted. Real life interferes...
Good luck, and enjoy!
Pat☺
-
Thanks for the time to explain this sound cfg issue, its very much appreciated. So, spent some time looking all the entries over and then listening to the various sound files. Rather than make endless changes and testing them out I decide to try a different approach. Noticed there were only 8 combustion and whine entries for viewpoint 1 versus 20 for viewpoint 2. Added first 5 lines of combustion and whine entries and made new viewpoint 1 entries, renumbering them. Excellent results!! Now I have all the changes in throttle position audible in the cockpit, with just a minor reduction in sound volume. Worked out great. This how it should sound. Thanks again.
-
Glad I could help. Hope you enjoy!
I have never been a Hornet, especially never been in one with the engine(s) running, so I can't speak to what you should and shouldn't be able to hear through a helmet and ear plugs. F-4's, yes, Hornets, no. It may have been 100% accurate, for all I know. But hey, if you're happy, THAT's what counts, no?
By the way, remind to tell you sometime about the really funny, but somewhat rotten, trick you can pull on a brake rider at high-power, with the Phantom's engines. ONCE.
It's actually really funny, if it doesn't happen to you :D
Enjoy!
Pat☺
-
I second that.
Incidentally, on the VRS forums there was a discussion on pilot's noise perception. It's very short because of this answer of an active SuperHornet pilot:
The engines are almost silent once the canopy is closed compared to the sound of the Avionics cooling fans and the ECS. On the ground you'll hear the high pitch whine when you increase throttle very quietly in the background (likely because the sound is magnified by bouncing off the deck), and also on final approach as you get within about a hundred feet of the ground you'll start to hear power changes a little more.
During up and away flight though the engines are definitely the most quiet sound in the cockpit. I've had to reset the electrical system on deck a few times (both generators and battery off) and the first thought I had was that both engines had shut down. It's eerie.
-
Well, that answers that, doesn't it?
Thank you very much Paddles! Now we know, as the saying goes. :D
But hey, it's a sim, after all. If Mr. Armenius is happy with hearing the engine whine in the cockpit, more power to him. If it's realism he wants, maybe a way to kick up the ECS and Avionics cooling fans a little would be the key, as the article Mr. Paddles posted so kindly points out. But the default download is pretty quiet in the cockpit, which started this discussion in the first place. :)
Anyway, as long a one enjoys the plane, and I sure do, that's what counts.
Pat☺
-
Yes indeedy! ;D
-
Hi all.
It's been a while but I've recently been chipping away at doing a minor aesthetic upgrade to the Delta. It's essentially the same as the old 15.6 but it now has the most recent C modifications incorporated (weapons and avionics). Some points to note:
1. This is a single-cockpit "Fleet" version. It doesn't replace the BA version - however I have included the BA D interior mdl in case anyone prefers to fly with two pits, despite the front office being covered in BA junk. I recommend keeping the old BA version separate.
2. For some reason, the speed brake doesn't fully retract in-flight, and will only fully close when you've completely stopped. I don't know how to fix that.
3. Weapons are the same as the C, and viewable from inside the cockpit. The wingtip AIM-9s will disappear and re-appear on wing-fold, just not instantly.
4. There doesn't seem to be any other HUD mode except NAV (so no CDIP or other weapon modes come up when selecting weapons). I don't know why this is, and it seems to happen on my C model too.
5. The centerline tank is fixed. You will always have to fly with it. I've tried many things but cannot correct this without a full decompile of the model, which I am not inclined to attempt.
I've also included a few more paints - the four VMFA(AW) units still operating the D, along with all my old ones.
Here's the link: https://drive.google.com/open?id=1_dQUpko7LxFgNMCE5V-2qypY4HIxVLv8
THERE IS ZERO SUPPORT FOR THIS. If I knew how to fix any bugs you find, I would have already.
Also, if anyone is interested, I've made some very basic conversions to AI for both the C and D but as tankers. Each carries five external tanks and by default come with a fixed drogue out the back of the center tank (you can remove the drogue by changing the models in the model.cfg). I've added them to my TacPack Tankers list and they seem to work alright. You should be able to add whatever paints you want by the usual methods, and be aware, these will probably show up on your Aircraft list because technically they are still flyable.
If you want the AI tankers, they are here: https://drive.google.com/open?id=1UpXqhQoVJNJLD04CmG91Vs75ZVEw3o_E
[EDIT: put the wrong one up before - here is the correct one. The other one used the FSXBA .air file, which will make the model wobble crazily in the turn - this one uses the default FSX:A Hornet .air file which seems to be more stable]
Just dump them into your AI folder (if you have a separate one), or Misc, or Airplanes.
-
Thanks Kea for the Delta model. I know this question is about to show by a few in here because it happened to me and again the fix for the blue glowing cockpit will remain the same only for those who have it.
Blue Cockpit fix:
In your texture folder create a new folder, you don't have to rename it if you don't want to. Find a file named CP_F18_4_N and move it to the new folder and you will have corrected the problem.
-
Thanks Kea for the Delta model. I know this question is about to show by a few in here because it happened to me and again the fix for the blue glowing cockpit will remain the same only for those who have it.
Blue Cockpit fix:
In your texture folder create a new folder, you don't have to rename it if you don't want to. Find a file named CP_F18_4_N and move it to the new folder and you will have corrected the problem.
I tried putting the CP_F18_4_N into a new folder but it didn't work. Maybe I missed a step?
-
I had that issue, try putting it in a new folder inside the texture folder
-
Thanks Kea for the Delta model. I know this question is about to show by a few in here because it happened to me and again the fix for the blue glowing cockpit will remain the same only for those who have it.
Blue Cockpit fix:
In your texture folder create a new folder, you don't have to rename it if you don't want to. Find a file named CP_F18_4_N and move it to the new folder and you will have corrected the problem.
I tried putting the CP_F18_4_N into a new folder but it didn't work. Maybe I missed a step?
Make sure you are not copying the file to the new folder make sure it is a move, click drag and drop to the new folder.
Edit = This is a system issue, video to be more precise and is why I chose to create the new folder inside the texture folder. If I get a better system I can move it back to normal texture folder and try it again on the new system.
-
Got it. Thanks.
-
Hey guys.. quick question.. I'm thinking of going for P3Dv4.. does the hornet work? aside from copying the fsx hornet.dll.. it's there anything else that needs to be done?
-
P3Dv4 is 64 bit the FSX hornet.dll nor any 32 bit dll file will work.
-
So that's a NoGo for v4?
-
At the moment, yes. BUT, they are working on making it functional in v4.
Just gonna take a little time is all. Patience is a virtue. :D
That's why I gave up med school:No patients :D :D
Happy new year, all!
Pat☺
-
Any update on the DDI for ver 17.1.31 regarding black screens ?
Currently using P3D V4.1 and tried the F-18.dll suggested for P3D V3.4
Hoping to have DDI's like seen in this link:
http://www.fsdreamteam.com/forum/index.php/topic,15196.15.html
saw the reference starting at almost bottom of the page to this issue:
http://www.fsdreamteam.com/forum/index.php/topic,6944.1365.html
-
The avionics don't in v4 and higher. They're 32 bit, and don't function at all in the 64 bit environment.
They (the amazing, famous "They") are working on updating it to work in 64 bit, but it's not there yet...
Pat☺
-
Gents,
Still working the issue. Been in an on and off conversation with Microsoft Gaming Studios, Microsoft Legal, and FS DreamTeam for the past 6 months to see what we can do to get this needed file converted over to 64-bit, working in P3D v4 and making it available for everyone to use. As of last Thursday, Microsoft Legal had to check with their team to make sure no contract breaches would occur between them and McDonnell Douglas.
Well, that's where we are at with things....
Keep your fingers crossed...
Jimi
-
Ahhh, lawyers. ::) :P
Well then, they should have your answers in a year or two. Remember, lawyers are paid by the hour, and they know it. >:(
Good luck on it, Jimi! I sure hope I'm wrong...
Pat☺
-
Hi! Here is a "fix" for P3D v4.1 and FSXBA 17.1.31 that many may know about, but as some here are asking for black MFDs fix...
So here it is as a provisory fix (mostly aesthetic fix but some of it indeed also work) - (Thanks to creepy847 and his youtube video about this fix)
1) of course think to copy FCS files from "For P3d v4" folder (in Panel.Fleet) to Panel.BA/Panel.Fleet folder so the HUD don't display the red FCS error.
2) download this free fsx F/A-18E model :
https://flyawaysimulation.com/downloads/files/23768/fsx-fa-18e-super-hornet-updated/
3) unzip it and copy the superh.CAB file from this plane's gauges folder to your FSXBA panel folder (Panel.BA/Panel.Fleet)
4) than edit your panel.CFG (in Panel.BA/Panel.Fleet, make a copy first for saving original) and go under [Vcockpit01], there you have to replace the 3 lines under //DEFAULT AVIONICS by :
gauge00=superh!rader, 450,4,440,440, 1
gauge01=superh!eng.mfd, 4,452,440,440, 2
gauge02=superh!hsi, 4,4,440,440, 3
(you can change "rader" (yes rader) by "Primary Flight Display", and "hsi" by "ufcd ap" to have other pages displayed that are more fps friendly than hsi GPS map and Air-Air radar)
You can see result on creepy847's video :
Big up to jimi08 and FSXBA team !
-
Awesome! Thanks for the info!
-
Great help "toutenglisse" it worked perfectly, BIG thanks.
-
:)
If, on left or right MFD, you click the lowest button of right column buttons, you get the working FCS page.
-
Gents,
Just a quick update on things.... Been making some good progress over the last few weeks with P3D compatible Avionics for the Hornet. List of accomplishments to date:
-All Top-level DDI pages that were working before are working now with the exception of the ACL page
-UFC is complete and functional so you can tune COMS & NAV radios and operate the autopilot
-Various inop indicators have been fixed such as the flaps and AOA Indexer lights
Good progress, but still a ways to go. Still have a lot to figure out with RADARs and all of the map functionality of the HSI.
-
Thank you for the update. I appreciate your efforts, and look forward to flying in P3Dv4.
-
Excellent, looking forward to update release.
-
p3d looking
let's work hard
(https://i.imgur.com/XTPv36s.png)
(https://i.imgur.com/mwu2ykl.png)
(https://i.imgur.com/f6z09ni.png)
-
Nice update and look at that A2G radar sweep!
-
p3d looking
let's work hard
I'm working it man. I've made some pretty good progress over the last few weeks.
Still got work to do on the RADAR and HSI pages and some bugs to work out with a few of the pages such as the HUD and ADI though. Then comes the TACPACK re-integration stuff!
(https://i.imgur.com/f9zeIFy.jpg?1)
-
Gents,
I figured I'd drop off what I have now before heading out of town for the week. Good or bad, I figured it's still a lot better version of the jet than what's available on P3Dv4 currently. Please keep in mind that THIS IS STILL A WORK IN PROGRESS... but as usual, I'm always open for comments, discoveries, recommendations and feedback.
The download link can be found at: http://www.fsdreamteam.com/forum/index.php/topic,16514.0.html under LATEST P3Dv4 WORK IN PROGRESS (WIP) DOWNLOAD LINK:
Make sure to take a gander at the notes I've left on that post before you take her out.
-
Just wanted to drop in and say hello and thank you for developing this ac. I think this might be my personal favorite. If you need any help please let me know. I am not a coder or developer just another simmer who has a passion for this study and plenty of time to help out.
Looking forward to more updates.
R/S
Creeps.
-
Thanks Creeps and welcome to the forums here. Also wanted to say thanks again for your help and contributions.
-
Thanks for the update, Jimi!
I don't have P3D, of any flavor, but for those that do, it's looking great!
This new, improved, P3Dv4 version isn't backwards compatible, is it? Even if I have a 64-bit OS? I wouldn't think so, but hey, doesn't hurt to ask :D
Pat☺
-
Hi. I've been doing some work with the guys at the Royale French Navy (http://royalefrenchnavy.restauravia.fr) for the next version of their P3Dv4 compatible RFN Carrier gauge (http://royalefrenchnavy.restauravia.fr/RFN-Creations.htm#Gau). One of the guys has been using the FSXBA F/A-18C Hornet (Version 18.1.00) for testing after getting FCS FAIL at trap asked me to pass along a couple comments. I'm not sure how much they effect things but here they are.
In the aircraft.cfg file he thinks the top section with all of the names (down to line 91 (archi)) should begin with // to comment them out.
And also that the "atc_id=Hobo 000" should have no space => Hobo000 in the [fltsim.0] and [fltsim.1] sections.
Thanks.
-
Hi. I've been doing some work with the guys at the Royale French Navy (http://royalefrenchnavy.restauravia.fr) for the next version of their P3Dv4 compatible RFN Carrier gauge (http://royalefrenchnavy.restauravia.fr/RFN-Creations.htm#Gau). One of the guys has been using the FSXBA F/A-18C Hornet (Version 18.1.00) for testing after getting FCS FAIL at trap asked me to pass along a couple comments. I'm not sure how much they effect things but here they are.
In the aircraft.cfg file he thinks the top section with all of the names (down to line 91 (archi)) should begin with // to comment them out.
And also that the "atc_id=Hobo 000" should have no space => Hobo000 in the [fltsim.0] and [fltsim.1] sections.
Thanks.
For the FCS fail, he needs to take the files located in the folder called "For P3D" or "for 64 bit" or something like that. It's located in the panel.fleet folder. Take the two files and place them in the main Gauges folder located in the main P3D folder.
As for the Hobo deal, your friend is correct. P3D doesn't like spaces for ATC IDs.
Hope this helps
-
Hi Jimi, and fellow F18 fans, first of all I'd like to say outstanding work on this project, and I also follow creepy847 on you tube for his F18 series videos (Keyser Soze in the comments of his video's)
A couple of questions pertaining to the 18.1 build if I may?
1. How can I add other liveries from the previous builds, other than the current 3 red and white prototype skins ( I love the fleet, and aggressor ones)
2. My virtual view doesn't show the pylons like the pictures, when I rotate around to see, all I see is a small portion of the leading edge and end portion of the wing, before the seat blocks my view, pretty sure I should be able to see the inner pylons.
Thanks guys.
-
Hi Jimi, and fellow F18 fans, first of all I'd like to say outstanding work on this project, and I also follow creepy847 on you tube for his F18 series videos (Keyser Soze in the comments of his video's)
A couple of questions pertaining to the 18.1 build if I may?
1. How can I add other liveries from the previous builds, other than the current 3 red and white prototype skins ( I love the fleet, and aggressor ones)
2. My virtual view doesn't show the pylons like the pictures, when I rotate around to see, all I see is a small portion of the leading edge and end portion of the wing, before the seat blocks my view, pretty sure I should be able to see the inner pylons.
Thanks guys.
Keeno,
For the the liveries, you can add the ones from the 17.1 model. There are a few how to videos on YouTube/Google on how to do this.
For the views, I used TrackIR while taking the shots which allows for for shots outside of the static head position. You can change the default view point in the aircraft.cfg under "eyepoint". You will need to move it forward.
-
Thanks Jimi, got it working.
-
Glad you got it working!
-
Thanks for the update, Jimi!
I don't have P3D, of any flavor, but for those that do, it's looking great!
This new, improved, P3Dv4 version isn't backwards compatible, is it? Even if I have a 64-bit OS? I wouldn't think so, but hey, doesn't hurt to ask :D
Pat☺
Hey Pat, apologies for the late response, but I think MOST of it should be... You will have to use the FCS.dll file that you are currently using and a few things such as the terrain mapping radar might not work. I have yet to test it in FSX.
-
Thanks for the reply, Jimi!
I'll try it out asap and let you know what works and what doesn't.
Amazing bird, and every update makes it amazing-er. Not a word, but who cares :D
Pat☺
-
Update: Still mostly working on HSI Displays and Radar Modes/Submodes. Progress.....
Color Moving Map!
(https://i.imgur.com/XLVN4Al.jpg?1)
-
Hi Jimi, hi all;
Since I installed Prepar3Dv3 I haven't worked with my favored F-18; very occasionally using it on FSX.
Instead I spent a year and more on F-22 and F-35; just because I did not trust myself of doing a flawless F-18 install.
Listening to our Forum members about their problems, different opinions and solutions scared me off even more. I did not like to take a chance in an unknown field.
I know a little about flying but for computer experiments with files and folder movements, I rather have somebody in the backseat.
Is there a safe way to success? What F-18 version goes with what Prepar3Dxx??
Your help will be highly appreciated.
Best regards, Amigo
-
Is there a safe way to success? What F-18 version goes with what Prepar3Dxx??
IMHO, for whatever that's worth, the v17.1.31 is the one you want. The link to download it is https://drive.google.com/file/d/0B3So3WwTLPRZcHVKUVczdm53Z1k/view (https://drive.google.com/file/d/0B3So3WwTLPRZcHVKUVczdm53Z1k/view) .
It comes in an auto-installer, which does the work for you. Just tell it where your P3D root folder is, and let it go.
It will also install the required files the FCS needs to function. I'm not certain, but you may need to install the file Hornet_FCS.dll from FSX manually, but I think, think I say, that it installs the correct .dll for you. If not, the newer, correct, version is available here on this thread someplace. It's .zip file comes with complete instructions on how-to, where-to, etc etc. It's actually a very simple process. If you get an FCS FAILURE notification, a green bar across the top of the screen with red letters, when you go to try and fly it, and blank MFD displays, then you need it. If you do, I will dig up the link for you if you want.
It will install the necessary .NET Framework as well, but a note on that: It may appear, during that install, to be frozen, or locked up. It is not. Just let it run, and it will finish in it's own good time. I've seen it take up to 15-20 minutes to finish. Just go get some coffee, or take a walk or something.
Hope this helps out a little bit. It's really a great plane. Flies like a dream.
Now, on another note, Mr. Jimi, sir: I'm doing some work learning to code in XML. I'm trying to start simple. I want to see how the Anti-Skid switch coding looks, ie: How YOU all coded it, but I can't seem to find it. I have a bad feeling that it's in the .dll the plane uses. If it is, I will work on finding code like it someplace else. I just want to, not copy, but look and see, so I can learn to do the same sort of thing. Maybe with light switches, or other type circuits. I am just curious.
Like I say, if it's not available to look at, I'll find something else to work with.
Thanks in advance!
Good luck, and I'm glad the v18.something is progressing so nicely :D
Pat☺
-
Pat;
Thanks a lot for your instant reply and your kind attempt to boost up my confidence in an installation process.
However, I did download version 17.1.31 already a year ago or so; but did not install it for the mentioned reasons.
Thank you for your confirmation that 17.1.31 is the correct version for an auto install on Prepar3Dv3.
I might go ahead and give it a shot while hoping Murphy stays out of reach.
Best regards, Amigo
-
I forgot to mention: When you run the autoinstaller, make sure you select RUN AS ADMINISTRATOR.
Extract it from the zip file, right-click on it, and select the Run As Admin choice. About the 3rd or so choice down the menu that opens when you rclick the .exe file.
Good luck to you, and here's hoping Murphy stays far away from you :D
Pat☺
-
Now, on another note, Mr. Jimi, sir: I'm doing some work learning to code in XML. I'm trying to start simple. I want to see how the Anti-Skid switch coding looks, ie: How YOU all coded it, but I can't seem to find it. I have a bad feeling that it's in the .dll the plane uses. If it is, I will work on finding code like it someplace else. I just want to, not copy, but look and see, so I can learn to do the same sort of thing. Maybe with light switches, or other type circuits. I am just curious.
Like I say, if it's not available to look at, I'll find something else to work with.
Hey Pat,
First off, copy all you want. This project has definitely taught me a lot and hopefully it will teach you and others as well. Not all of it is my code so just make sure to give credit where it's due.
To monitor a gauge...
That being said, there are a few references/sources you will need to code in FSX. The first is the list of Simulation Variables or SIMVARs for short. You can find them in the SDK, or by simply doing a Google search for "FSX SIMVARs" or "P3D SIMVARs". Here's the link: https://msdn.microsoft.com/en-us/library/cc526981.aspx . From there, a spreadsheet of the variables should show up. These are all of the variables that are being actively monitored within the sim.
In the FSX XML, the standard format for writing a SIMVAR is as follows:
(VAR Type, Actual Variable being monitored, Unit of measurement)
Take the Simvar for Pressure Altitude for example, it would look like this:
(A:PRESSURE ALTITUDE, feet)A = Indicates SIM Var from the AIRCRAFT. E: is for ENVIRONMENTAL data such as computer, server or sim time etc. P: is for PROGRAM data such as Sim Rate. Most of the time, you will be dealing with "A" Variables.
PRESSURE ALTITUDE = The actual condition that you want to monitor. This is listed in the "Simulation Variable" column of the SIMVAR chart as described above.
feet = The unit of measurement of the variable you are monitoring. For the above, it will display numerical results in feet. The standard unit used for each variable is usually listed next to the listed variable in the "Unit" column of the SIMVAR chart. If you wanted it in meters, simply replace "feet" with "meters". If it's a digital function (on or off), "Bool" (short for Boolean) will work. Your Anti-Skid switch would fall in this category.
So to wrap it all together to monitor your Anti-Skid switch, the code would look like this:
(A:ANTISKID BRAKES ACTIVE, Bool)Since we're monitoring the variable from the Airplane, "A:" was used, ANTISKID BRAKES ACTIVE and Bool were pulled from the SIMVAR list.
I usually use my "DATA GAUGE" (Shift+8) to monitor the states of certain Simulation Variables while working on certain gauge/functions. The DataGuage.xml can be found in the Panel.Fleet/Gauges folder. There is a lot going on in there if you open it, but basically all of the entries in there are the display parameters for the info on the screen and are paired. The first entry shows the info to display the title of the variable (i.e. <Gaugestring>Altitude</Gaugestring> ) , and the second grouping shows, the display parameters for the actual data from the simulation variable <Gaugestring>%((i.e. (A:PRESSURE ALTITUDE, feet))3.1%</Gaugestring>). To use the gauge, simply find a variable listed that you want to replace with yours, replace it with the variable you want to use, and also replace the title of that variable in the grouping above so you can easily find it. Once you are done, save the file, reload the aircraft in the sim, press Shift+8 and look for your data. For your Antiskid entry, and because it is a Boolean variable, it will return either a "1", indicating that the Antiskid brakes are active, or a "0" showing that they are inactive.
Now, that allows you to MONITOR something..... To get the sim to DO something is a little different....
Action items are known as "Key Events" in the sim, and there is a finite list of "doable" things in the sim. That list is contained in another reference, and can be found through Google as well by searching "FSX Event IDs" or "P3D Event IDs". Linked at: https://msdn.microsoft.com/en-us/library/cc526980.aspx .
The standard for writing an Event ID is as follows:
(Trigger, Event Type, Event ID)
In practicality, it looks like this:
(>K:ANTISKID_BRAKES_TOGGLE)or
(>K:ANTISKID_BRAKES_TOGGLE)
">" and ">" are the triggers and mean the same thing. They basically tell the gauge to execute/assign what comes after it.
For the sim, "K" will always be used to indicate a key event and you can find the list of Event IDs at the last link provided above.
Tying it all together......
Now that you know how to MONITOR something and also to DO something, you can now create basic "IF/THEN" statements in XML. This basically states that "IF all of these things are true, THEN do this action".
Basic structure for an XML IF/THEN Statement is as follows:
(A:Variable 1, unit) parameter
(Variable 2, unit) parameter and
(Variable 3 & so on, unit) parameter and
if{ (>K:Event_ID) } els { (>K:Other Event_ID) }
Few things to note here....
-I put parameter in the example above. This is to define the specifics of your statement. In the case of the previously used Altitude Variable, I might use one of the following to better define parameters for the gauge:
(A:PRESSURE ALTITUDE, feet) 10000 < => This means that this IF statement rings "true" if the aircraft's pressure altitude is at 10000 feet and below. "<" translates to "and less than" so literally "10000 feet and less than"
(A:PRESSURE ALTITUDE, feet) 10000 > => This means that this IF statement rings "true" if the aircraft's pressure altitude is at 10000 feet and above. ">" translates to "and greater than" so literally "10000 feet and greater than"
(A:PRESSURE ALTITUDE, feet) 10000 ==; => This means that this IF statement rings "true" if the aircraft's pressure altitude is equal 10000 feet exactly. "==" translates to "equal to" so literally "10000 feet exactly"
-For Boolean variables, no entry behind the variable indicates that the variable rings "true" if the variable is active, while an exclamation point "!" indicates that the Boolean rings true if the variable is not active. For example, the variable (A:SIM ON GROUND, bool). Simply stating (A:SIM ON GROUND, bool) indicates that this variable rings true if the aircraft is on the ground. (A:SIM ON GROUND, bool) ! indicates that this variable rings true if the aircraft is airborne.
-If you are using more than one variable together to define your if statement, the word "and" or "&&" needs to be included at the end of the second stated variable and every subsequent variable to be included. If it's an "either/or", then the word "or" or "||" needs to be included.
-"Els" or Else statements, are used to indicate something to do be done until all of your "if statements" ring true. An example might be that you want a certain switch to only be activated under certain circumstances, but off under all other circumstances.
So as a final example I will do a basic if/then statement that instructs the sim to TOGGLE THE ANTISKID BRAKES if the sim detects the aircraft to be ON THE GROUND, BELOW 50 KNOTS, and only to toggle the Antiskid Brakes if they aren't already activated.
<Gauge:Example Antiskid Gauge>
<Element>
<Selection>
<Value>
(A:SIM ON GROUND, bool) <!-- Monitors whether the aircraft is on the ground or in the air. Statement is true if the aircraft is on the ground. -->
(A:AIRSPEED INDICATED, knots) 50 < and <!-- Monitors the indicated airspeed of the aircraft. Statement is true if the aircraft is below 50 KIAS. -->
(A:ANTISKID BRAKES ACTIVE, Bool) ! and <!-- Monitors the status of the Antiskid Brakes. Statement is true if Antiskid brakes are OFF/INACTIVE. -->
if{ (>K:ANTISKID_BRAKES_TOGGLE) } <!-- Tells the sim to toggle the antiskid brakes if all of the above statements are all true simultaneously. -->
</Value>
</Selection>
</Element>
</Gauge>
The last reference worth mentioning is the aircraft's "Modeldef". From my understanding, it basically displays all of the variables and event that are "baked" into the 3D model of the jet. Changing them would mean decompiling and recompiling the jet. None the less, very useful reference, especially when trying to tie certain buttons or switches within the cockpit to your gauges for functionality. Here you can see all of the great work that FSDreamTeam put into modeling the F/A-18 Cockpit.
Kinda a lengthy explanation, but that's all I got for now (lunch break is over). That's the basics. Let me know if you have more questions (as I'm sure you do) and I'll try my best to answer them. My best advice is to open an existing gauge, make small changes to them and reload the aircraft to see how things work/change. Once you get used to that, move on to bigger/better things....
-Jimi
-
Pat;
I enjoyed Jimi's last, very interesting reply to you. I don't want to further clutter up his page with my stupid problems. Can I talk to you on a new page named; Murphy's Law?
Amigo
-
Amigo,
No stupid problems here bud. This is what the thread is for! I've sent you a response on your new thread. Good luck and let me know if it fixes anything.
-
***UPDATE***
Hey Gents,
Just uploaded the latest of the progress in reference to the P3Dv4 bird.
FSXBA F/A-18C Hornet 18.2 (P3Dv4)
link: https://drive.google.com/open?id=1cKFVqr_yBHzlTwlKEvq5Z2hEmanTk99t
(https://i.imgur.com/qtH4eAh.jpg?2)
(https://i.imgur.com/RYeSyrP.jpg?1)
(https://i.imgur.com/rzqcQYQ.jpg?1)
Bottom Line Up Front (BLUF): Avionics on this new jet still not to the same level of functionality as the Acceleration F/A-18, but getting there quickly. Big thanks again to Dino Cattaneo from IndiaFoxtrotEcho, Dave Brice from IRIS Simulations and Kea from the FSDT forums here for their help and guidance!
Updates include:
1. RADAR:
-Working on 3 Air To Air (Range While Search (RWS), Track While Scan (TWS), Single Track (ST)) and 3 Air To Ground (MAP, GMT (Ground Moving Target (GMT), SEA) RADAR modes. They are in "place" but filters still need to be turned, so as of now, they are not working as intended. They do however detect and tract targets.
-Range and Sweep settings work.
-For more information on the contacts, press the "DATA" button, located on the bottom right of the screen.
2. ADI & HUD
-ADI and HUD pages are now fixed and added.
3. HSI Data Pages
-HSI GPS and TCN Information Pages have been added
4. FPAS Page
-FPAS Page has been updated.
5. Re-added Textures
-By demand, all textures (80 of them!) have been added back to the pack.
6. TACPACK
-TacPack is functional once again.
To Note....
-As I've said before, this is still a work in progress. There are plenty of "kinks" in the system. Call'em out as you see them.
-I have yet to "link" the avionics from one DDI to the next, meaning that they currently DO NOT share settings (with the exception of the SMS Page)
FSX Users....
This version should be FSX Compatible, the following changes are made:
1. The FCS.dll from the 17.3.1 (located in the Panel.Fleet folder) needs to be placed in the Panel.Fleet and Panel.BA folders of the 18.2 version
2. Doug Dawson's sound file, dsd_p3d_xml_sound_x64, needs to be replaced with the dsd_fsx_xml_sound file which is also located in the 17.3.1's Panel.Fleet folder
3. Line 20 of the Panel.cfg needs to be updated to reflect the change in Doug Dawson's sound file. Save and close.
Change:
gauge20=dsd_p3d_xml_sound_x64!Sound, 2,2,2,2, \Sound\Sound.iniTo:
gauge20=dsd_fsx_xml_sound!Sound, 2,2,2,2, \Sound\Sound.ini
That should do it. As usual, always welcome to suggestions and feedback.
-Jimi
-
Just downloaded and took it for a spin in P3Dv4 .... I'm speechless ... absolutely floored.
She's bloody awesome.
Tacpack is working a treat and all seems functional.
She flies like a dream.
Don't forget to copy the "HornetFCS" files to the root "panel" folder if you're using her in P3Dv4.
Even took her for a spin in VR ... just incredible.
Thank you all, finally a working F-18 for P3Dv4 ....
Gary
-
Holy cats, Jimi, I wasn't expecting all that! :o
All I was thinking was a basic "Sure, go ahead! It's in..." or " No, that switch is part of the Hornet_FCS.dll file...". I wasn't thinking a full XML lesson, but I most deeply and sincerely appreciate it!
That will be a huge help as I really embark on this little adventure. I just hope my little pea-brain can take it ??? :D
I have cut-n-pasted that off to a document on my HD for quick reference. I've also got the XML lessons and reference stuff Orion linked for me last year some time. I just didn't have time then to dig too deeply into it. Now I do, and I'm gonna :)
Maybe someday I will be helping code switches and gauges for the FSDTeam. Who knows?
Thanks again!
Gary, glad you got it going in P3D. The gauges and so on are very, very impressive, no question, but to me it's the FDE that is just staggeringly good. No other plane in the sim-world can match it!
Have fun all!
Pat☺
-
Thank you for this 18.2 version.
Can you have a look at the payload station because some of them exceed maximum name length of 15
station_name.0 to station_name.n :
This field is the string name that is used in the Payload dialog (15 character limit). Omission of this will result in a generic station name being used.
http://www.prepar3d.com/SDKv4/LearningCenter.php
It is possible to have kd_FX_seatRocket effect because it seems missing.
Best regards and good continuation for this beautifull work.
Michel
-
Hi thanks for the Update to 8.2..
I noticed that for the FSX modifaction u state about moving files from panel 7.1.31 inot both panels in 8.2 ..but i'm only seening the one panel.fleet in that aircraft ..is this correct?
Gr8 work thanks you
Morti
-
Thanks Jimi
Looking forward to checking it out.
I haven’t flown in two months.
Fell and fractured my arm in two places and fractured my hip.
I’m now the proud owner of three titanium pins.
Les “cobrales “ Pearson
-
I’m now the proud owner of three titanium pins.
I know the feeling. I have a Titanium plate and screws in my right arm. Little old lady pulled out right in front of my bike. I got it layed down, but it was too late. Bike hit the car, and flipped me up-n-over. My thoughts were "I can FLY!", and when I saw the ground coming up "This is gonna HURT!". Boy was I right. Apparently I put my hands out to break my fall, but it broke my arm instead. Shattered the forearm, broke the head off the elbow, etc.
Now I get to set off metal detectors in airports. I can also tell when a radar is on within a certain range. Kinda handy, but painful...
Have fun! Great plane, no question.
Pat☺
-
Thanks everyone for the good words, I'll be sure to pass them along!
Micpni/Morti,
Thanks for the feedback and I'll take a look at the coding when I get the chance.
Thanks again everyone.
Jimi
-
Great job on the upgrade! Thanks for all the hard work !
I did notice a lot of my key assignments were not correct any more, namely wingfold, tailhook . IIn P3D shows shift w for wings and shift q for tailhook. shift q folded my wings on final and never found the hook. Luckily I unfolded quickly and my carrier landing became a touch and go . LOL
Is there a new controls map/list?
Please help.
-
...and never found the hook.
Did you try using the HOOK lever in the cockpit? Right side vertical panel, above the Cautions/Warnings panel? Hard to miss. Has a rectangular, red light above it to indicate it's down.
If it lowers the hook, go into you key assignments menu, and see if anything has changed it. Another add-on plane, an add-on gauge, or whatever, that you may not have noticed. Same for FSUIPC. If you have the payware version it can have this effect. Won't show in your key assignments menu, but it is in the FSUIPC information.
I don't have P3D, nor the payware version of FSUIPC, so I can't be more specific. Sorry about that.
Also, make sure you don't have any add-on program running alongside P3D that could capture that key assignment. A screen-cap program, a FBW add-on program, auto-trim, etc etc. Worth taking a look, anyway.
Hope something in all my babbling helps a little...
Pat☺
-
Don't know why but,
water rudder is eject,
wing fold is refueling probe, and
tail hook is wing fold on my system .
I guess I have problems some where . I'll keep digging around.
The D ported over works perfect, so I'll keep looking.
And the hook handle folds the wings, although it says the hook went down. FYI the previous version also still works perfectly, just no MFD
-
Don't know why but,
water rudder is eject,
wing fold is refueling probe, and
tail hook is wing fold on my system .
I guess I have problems some where . I'll keep digging around.
The D ported over works perfect, so I'll keep looking.
And the hook handle folds the wings, although it says the hook went down. FYI the previous version also still works perfectly, just no MFD
Wow didn't know about ejection modelled!
-
Don't know why but,
water rudder is eject,
wing fold is refueling probe, and
tail hook is wing fold on my system .
I guess I have problems some where . I'll keep digging around.
The D ported over works perfect, so I'll keep looking.
And the hook handle folds the wings, although it says the hook went down. FYI the previous version also still works perfectly, just no MFD
Wow didn't know about ejection modelled!
Great animation too. First canopy then the seat ! Looked great except I was downwind for the boat ! LOL
-
Hi Jim thx for the update. I noticed a visual model issue if you pan around and look directly at your 6 oclock in the vc you will see that air-brake is not properly seated along the fuselage of the ac. It extends and retracts but does not seat fully in its stored position.
Other than that I have another issue but I need to look at the closer and see if its my side only.
Thank for your hard work.
-
Hi Guys,
I'm old and grey, going on 80, and my greatest pleasure is flying beautiful aircraft in (now) P3Dv4.2. I have been following your development of the Hornet very closely; not only do I love this bird - I managed to get several hours on her in my previous life as an RAAF fighter pilot - but I greatly admire the time and effort your team has put into this freeware development. It is a great credit to you all!
You do such a good job that normally I would not raise a small issue, but this one is somewhat obscure and a lot of fltsim pilots might not pick it up quickly enough.
The aileron trim in the FA-18C_FSXBA_BA_18.2.22 version is reversed. After checking my CH controls for the correct key assignments, I tested this against a number of other aircraft and confirmed it. I checked the Air and CFG files for an easy fix but couldn't find one so I must leave that to your expertise.
You have my greatest admiration,
Roger Lowery
-
All,
Thanks for the good words and the feedback! Here is some feedback on your feedback. I'll be out of town for the next couple of weeks, so it might take a little bit of time to get some of these fixes done.
Great job on the upgrade! Thanks for all the hard work !
I did notice a lot of my key assignments were not correct any more, namely wingfold, tailhook . IIn P3D shows shift w for wings and shift q for tailhook. shift q folded my wings on final and never found the hook. Luckily I unfolded quickly and my carrier landing became a touch and go . LOL
Is there a new controls map/list?
Corvette,
No, no new assignments Sir.. I did a quick run-through of cycling the hook, wingsfold, launchbar and refueling probe. All worked as designed with both mouse clicking the switch/levers in the VC and through key commands. I might be your setup. Let me know if you figure out what the issue is.
I noticed a visual model issue if you pan around and look directly at your 6 oclock in the vc you will see that air-brake is not properly seated along the fuselage of the ac. It extends and retracts but does not seat fully in its stored position.
Hey Creeps,
Keen eye! Pretty sure that has to do with the way the payload drag effect is coded and implemented. Since it was built into the 3D model, not sure if I'll be able to fix that anytime soon. I'll ask Corrado if he can do me a solid and check it out.
The aileron trim in the FA-18C_FSXBA_BA_18.2.22 version is reversed. After checking my CH controls for the correct key assignments, I tested this against a number of other aircraft and confirmed it. I checked the Air and CFG files for an easy fix but couldn't find one so I must leave that to your expertise.
Mr. Lowery,
Thanks for taking the time to provide feedback and thanks for the compliments. You're right, this probably would have gone unnoticed for a while. Good catch. Pretty sure this fix is an easy one and can be done in the .air file. If not, I'll talk to Orion when I get the chance.
Thanks again and thanks for your service.
Thanks again everyone,
Jimi
-
Great job on the upgrade! Thanks for all the hard work !
I did notice a lot of my key assignments were not correct any more, namely wingfold, tailhook . IIn P3D shows shift w for wings and shift q for tailhook. shift q folded my wings on final and never found the hook. Luckily I unfolded quickly and my carrier landing became a touch and go . LOL
Is there a new controls map/list?
Corvette,
No, no new assignments Sir.. I did a quick run-through of cycling the hook, wingsfold, launchbar and refueling probe. All worked as designed with both mouse clicking the switch/levers in the VC and through key commands. I might be your setup. Let me know if you figure out what the issue is.
Thanks anyway Jimi.
Great plane though ! Hope to get the keys assigned soon
-
Have you ever thought about integrating SSW ACMI, that it is a complete and free weapons system, able also to simulate SAMs, AAA, control ships, etc ( http://www.sim-outhouse.com/sohforums/showthread.php/109523-vACMI-almost-for-all) in the hornet?
Thank you!
-
Have you ever thought about integrating SSW ACMI, that it is a complete and free weapons system, able also to simulate SAMs, AAA, control ships, etc ( http://www.sim-outhouse.com/sohforums/showthread.php/109523-vACMI-almost-for-all) in the hornet?
Thank you!
No I haven't, first time hearing about this program. I'll take a look at it once I get back home. Thanks!
-
I just installed in P3Dv4.2. The DDI's are working fine, but still getting the red FCS warning in the HUD. Do I need to meove the new FCS Dll's somewhere other than the panel folder?
Thanks,
Reggie
-
Hi Reggie,
yes move that file HornetFCS.dll over into your panel folder and that will stop the FCS warning in the hud.
-
Good morning everybody,
I'm new in this forum and at first I want to say thank you for this wonderful plane.
I'm living in Switzerland and the F/A 18 is something special.
I fly FSX and I have the same problem with the red "FCS FAIL" on the HUD .
I noticed a warning signal "FCS HOT" on the right side of the panel and when I open the FCS window I see "FCS initialized-0".
The HornetFCS.dll file is in the Panel Fleet folder.
I 'm speaking about the version 18. but I had the same problem with the version 17.
Can someone help me to fix this issue?
Many thanks !
-
Got the FCS warning gone from the HUD, but now getting this warning (see screenshot). Where do I need to place this "sound" gauge?
Reggie
-
Got the FCS warning gone from the HUD, but now getting this warning (see screenshot). Where do I need to place this "sound" gauge?
Reggie
Reggie,
What you need to do is replace the 64 bit version of the sound.dll with the 32 bit version.
Please follow the following steps:
1. If you still have your previous version of the FSXBA Hornet, got to its folder in SimObjects/Airplanes and locate the "Panel.Fleet" folder.
2. Within that folder, you should see a file titled "dsd_fsx_xml_sound.dll". Copy it.
3. Navigate to the new FSXBA Hornet 18.2/Panel.Fleet folder that you just installed and paste it within there. You also see another sound file in there called "dsd_p3d_xml_sound_x64". No need to delete it.
4. In that same folder, you should see another file called "Panel.cfg", open it.
5. Locate the following line:
gauge20=dsd_p3d_xml_sound_x64!Sound, 2,2,2,2, \Sound\Sound.inireplace if with the follwing:
gauge20=dsd_fsx_xml_sound!Sound, 2,2,2,2, \Sound\Sound.iniSave the Panel.cfg file.
6. Restart FSX/P3D and see if that fixes your problem.
Let me know if it fixes the issue, or if you run into any problems.
Jimi
-
Good morning everybody,
I'm new in this forum and at first I want to say thank you for this wonderful plane.
I'm living in Switzerland and the F/A 18 is something special.
I fly FSX and I have the same problem with the red "FCS FAIL" on the HUD .
I noticed a warning signal "FCS HOT" on the right side of the panel and when I open the FCS window I see "FCS initialized-0".
The HornetFCS.dll file is in the Panel Fleet folder.
I 'm speaking about the version 18. but I had the same problem with the version 17.
Can someone help me to fix this issue?
Many thanks !
Lucame,
Welcome to the forums and thanks for the kind words!
Have a few questions for you:
1. Do you have a previous version of the FSXBA F/A-18 installed already?
2. If so, did you use the auto-installer to have it installed or did you do a manual installation?
Your problem could be one of two things (or both):
Try this first...
1. The HornetFCS.dll file that comes with the 18.2 jet is made for the 64-bit version of P3D. You will need the correct version (32-bit) of the FCS.dll for FSX. You can get that downloading the latest FSX version of the jet and looking in the Panel.Fleet folder. Simply copy and paste the dll from that version into the Panel.Fleet folder of the 18.2 jet. Click yes to replace if prompted.
If the above doesn't work, do this as well....
2. You need to install the "Visual C++ Redistributable for Visual Studio 2015". It can be found at https://www.microsoft.com/en-us/download/details.aspx?id=48145. Make sure you download the x86 variant.
Hope this helps. Let me know if you run into problems or have further questions.
-
The aileron trim in the FA-18C_FSXBA_BA_18.2.22 version is reversed. After checking my CH controls for the correct key assignments, I tested this against a number of other aircraft and confirmed it.
Roger Lowery
Mr. Lowery,
Please find included below the link to download an updated version of the FA-18_18.2.air file that is located in your FA-18C_FSXBA_BA_18.2.22 Folder, which is located in SimObjects/Airplanes. Simply download the file from the link below, and place it in your FA-18C_FSXBA_BA_18.2.22 folder. Click yes to replace the existing file if prompted.
Let me know if this fixes your issue please. If so, I'll include it in the next release of the jet.
Thanks again,
Jimi
Link: https://drive.google.com/open?id=1ua_9WQkHErUOWNX28fSB5bQrBi8epL0-
-
Thank you Jimi, all is perfect working now without problems on the HUD.
I think that The Visual C++ program was not correctly installed or was not the latest version.
I spent a lot of time trying to fix my F/A18 and the solution was so easy....
Best wishes :D
-
Got it Sir, thank you!
Reggie
-
Mr Hendrix,
The new .air file works fine now with all trims working in the correct sense.
One very minor issue for consideration when the really important work is finished: The stabilizer movement in response to trim input is excessive (I think; this should be checked with a Hornet specialist.) For example, at 300KIAS apply full aileron and note the tailplane deflection angles. At the same speed, feed in aileron trim only and note the deflection angles.
For now, the Hornet flies beautifully and all controls work in the correct sense. I'd leave the tailplane deflection issue for the final tidying up phase.
Beautiful work, Sir! Please keep it up
Roger Lowery
-
The aileron trim in the FA-18C_FSXBA_BA_18.2.22 version is reversed. After checking my CH controls for the correct key assignments, I tested this against a number of other aircraft and confirmed it.
Roger Lowery
Mr. Lowery,
Please find included below the link to download an updated version of the FA-18_18.2.air file that is located in your FA-18C_FSXBA_BA_18.2.22 Folder, which is located in SimObjects/Airplanes. Simply download the file from the link below, and place it in your FA-18C_FSXBA_BA_18.2.22 folder. Click yes to replace the existing file if prompted.
Let me know if this fixes your issue please. If so, I'll include it in the next release of the jet.
Thanks again,
Jimi
Link: https://drive.google.com/open?id=1ua_9WQkHErUOWNX28fSB5bQrBi8epL0-
Is this fix for just the P3Dv4.2 or Both P3Dv4.2 & FSX
-
Just an .air file shouldn't matter, P3D, any version, or FSX.
Hope this helps a little...
Pat☺
-
Hi Everyone,
First, a sincere thank you for the hard work put into this beauty! Very impressive and immersive too.
I have just one small issue if you can help.
When starting a flight I receive a 'Config File Not Found:' error every time. Any ideas?
Other than this she works and flies superbly.
I'm running P3Dv4.1 with Windows 7.
Best regards, Dave.
(https://s5.postimg.cc/3ol0wfpaf/Error.jpg)
-
Are there any other repaints other than what is on the FSX Blue Angels website? I've checked the usual places with negative results.
Thanks,
Reggie
-
Dave,
I'd first recommend going to the FSXBA FA-18C BA 18.2... and opening the panel.fleet folder.
Do you see the file in question in there?
If yes, open you panel.cfg file and verify that it is pointed to the correct location. The entry i is titled: gauge20=dsd_p3d_xml_sound_x64!Sound, 2,2,2,2, \Sound\Sound.ini
If the file is not in the panel.fleet folder, I'd recommend downloading and reinstalling, then verify that that file is in there.
Hope this helps.
Jimi
-
Are there any other repaints other than what is on the FSX Blue Angels website? I've checked the usual places with negative results.
Thanks,
Reggie
Other than the 70± that were available on the latest release? I don't think so. If you are looking for a certain texture, I'd recommend taking to the guys over at Groom Lake Simulations. They have a Facebook page under the same name and are pretty responsive.
-
Thank you Sir. Would like to see a VFA-106 repaint.
Regards,
Reggie
-
Dave,
I'd first recommend going to the FSXBA FA-18C BA 18.2... and opening the panel.fleet folder.
Do you see the file in question in there?
If yes, open you panel.cfg file and verify that it is pointed to the correct location. The entry i is titled: gauge20=dsd_p3d_xml_sound_x64!Sound, 2,2,2,2, \Sound\Sound.ini
If the file is not in the panel.fleet folder, I'd recommend downloading and reinstalling, then verify that that file is in there.
Hope this helps.
Jimi
Hi Jimi,
Thanks very much for the quick reply!
With your comment the problem's solved.... kind of.
Yes, the file is there but it turns out I had another copy of the dsd_p3d_xml_sound_x64.dll file in my P3Dv4\Gauges folder that was being picked up by the panel.cfg entry. So, obviously the Sound\Sound.ini wasn't found in the Gauges folder and thus I got the error message every time.
The dsd_p3d_xml_sound_x64.dll I already had in the Gauges folder was used for the Manfred Jahn C-47 but I can move it to the C-47 panel and edit the panel.cfg entry.
Hope this makes sense.
Thank you and best regards,
Dave.
-
Just an .air file shouldn't matter, P3D, any version, or FSX.
Hope this helps a little...
Pat☺
Thanks Pat
Regards
Morti
-
Dave,
I think your situation arises from the fact that P3D v4, and maybe earlier, reversed the search order involving gauges and so on from FSX and FS9. The earlier sims looked in FSX\SimObjects\Airplanes\whatever_plane\Panel\X (folder), then \Panel\X.cab then FSX\Gauges\X (folder) and finally \Gauges\X.cab/X.gau .
In P3D that's reversed, so if you had a folder or .cab file in your \Gauges folder with something that would conflict with what you WANT to work in your \Panel folder, you'll see this problem.
Hope this helps explain...
Pat☺
-
Using the latest 18.2.22 with a fresh install of Prepar3D V4 and applied all the fixes FCS issue resolved and DDI's working but not able to have the colour map, will appreciate the guidance to have it show up.
-
Mirza001,
Color map only available on the center DDI. To get to it, go to MENU, the HSI and then click the soft button next to MAP.
Hope this helps.
Jimi
-
Hi Jimi08,
I'm new to your thread. I have to say WOW! What a great aircraft....thank you for this great rendition of the F/A-18C.
I added your 18.2.2 version to my P3D v4 file and it flies great. I might have missed it in the thread but when I add a store from the configurator load, sometimes the canopy pops and the pilot ejects from the aircraft. I'll try to get a picture of it the next time it happens.
I think you've set a new bar! Thank you for the great Hornet!
Skelator
-
Hi Jimi08,
I'm new to your thread. I have to say WOW! What a great aircraft....thank you for this great rendition of the F/A-18C.
I added your 18.2.2 version to my P3D v4 file and it flies great. I might have missed it in the thread but when I add a store from the configurator load, sometimes the canopy pops and the pilot ejects from the aircraft. I'll try to get a picture of it the next time it happens.
I think you've set a new bar! Thank you for the great Hornet!
Skelator
Skelator,
First, Thanks for the good words! I'll be sure to pass them along to those assisting in the project.
Second, thanks for the feedback. As for the ejection issue, this will be a first. As far as I know, the ejection animation is only tied to Cntl+W (water rudder) I believe. Do you have any other functions tied to Cntl+W? Does it only happen when certain stores are added?
Thanks.
Jimi
-
Hi Jimi,
I tried to duplicate the situation tonight. When I was in the Cockpit view I selected "Shift-7", selected "Guns on;y" and then center line tank. When I went to the outside view the canopy was suspended behind the aircraft. I took off from Eglin and went direct to P-Cola. Landed with out the canopy and started taking off the runway. Went to the outside view and behold...the canopy was on the aircraft with the pilot in the seat. Haven't done anything with the Shift-W "Water Rudder" function but I'll check that when I get back from work tomorrow. I'll try to get a picture to attach to the thread tomorrow. Again, Thanks for the great Baby Hornet....I friend of mine in the fleet says that's what they call A's through D's sometimes. He flies Superhornets.
Talk to you soon!
Skelator
-
Hi all
Just whipped up a couple more repaints (so they might have a few errors!) for something I was doing recently, and thought they may as well be shared with everyone!
https://drive.google.com/open?id=1YipuZg6dBjFz8gYv-I-s-vm6fzxlBlSl
2x NAWDC (ex NSAWC) paints - plain grey "33" and recent blue Flanker "24" schemes
4x VMFA-323 Death Rattlers - 401 (hi-viz but not all done up); 404, 405 and 412 (all lo-viz). These are the embarked (NH) schemes.
-
Thanks Kea!
I'll give them a whirl as soon as my internet troubles are cured.
Sooner rather than later, I really hope. It's getting really frustrating having it work, occaisionally.
Pat☺
-
Awesome Kea! Thanks!
I just uploaded a new version (version 18.3) of the jet for both FSX and P3Dv4 last night. Download Links available on the first page of the thread. I'll type a write-up of changes when I get the chance.
I missed it this time Kea, but will it be OK to include your textures in the next release?
-
Yes of course Jimi. These ones were a bit rushed so if you spot any mistakes let me know and I'll fix them up.
-
Gents,
FSXBA F/A-18C HORNET (FSX & P3Dv4) VERSION 18.3
(https://i.imgur.com/QotGaR8.png?1)
Ver. 18.3
(https://i.imgur.com/i28HAd4.png?1)
18.3 Avionics
(https://i.imgur.com/hnH3S0x.png?1)
New Situational Awareness Page!
(https://i.imgur.com/WRNrpQR.png?1)
A/A Tanker Navigation Mode
(https://i.imgur.com/I7Knkeq.png?1)
6 New Liveries (86 total)!
Now that I have a little time, wanted to make the official announcement that the 18.3 version is out for both the FSX and P3Dv4 jet. Please note that both versions are now using the new avionics that we've been working on. If you wish to retain the FSX:Acceleration/Steam avionics, please stick with the 17.3 jet.
As with the other, more recent releases, this upgrade deals mainly with avionics; the 18.3 release has a few new features, which I will cover in a minute, but addresses coding bugs and code cleanup in large.
New features include:
-S/A Page: This is a "best I could do" based on information available and my coding abilities. The new Situational Page or "S/A" page, for short, combines data from sensors such as radar info and link info (information feed from other aircraft sensors and map info to provide a combined operational picture to the operator. For the FSXBA jet, this translates to a 360 degree view of Air-to-Air and Air-to-Ground radar contacts, along with a limited display of ground info, such as nearby airports, navaids, and geopolitical boarders. To reach the SA page, simply got to the MENU option, then select the soft key next to "S/A". To toggle the map info, click on the soft button under "MAP". To toggle the AA and AG radar contact info, click on the soft buttons next to either the "SNSR" or "C2" options. To show your flight plan/waypoints (if you have them), press the soft button next to "SEQ". To see details, press the soft button next to "DATA".
-TACAN A/A Mode: We've integrated the A/A option on the Up Front Controller (UFC), with the Aerial Refueling Gauge and the HUD display so that a heading marker (bug) and distance will be displayed on the HUD once you've selected an aircraft to be the refueler from the Refueling Gauge (Shift + 5, or extending the refueling probe). Once you have an aircraft selected, press the "TCN" button on the UFC and press the #3 Option Button on the UFC next to the lettering "A/A". If everything is done correctly, you should get a heading bug, indicating the bearing of the selected aircraft along with the distance to the contact in the lower right of the HUD (i.e. "10.9 A/A). As of now, it only works with Multiplayer Air to Air contacts, and not AI Traffic, so I don't think it will work with TACPACK Tankers yet. Still working to resolve this.
-Next Liveries: Thanks to the guys over at Groom Lake Simulations, 6 new textures have been added to the lineup, making the total liveries included 86! A day late and a dollar short Kea. Will get your new ones in there on the next release!
Fixes include:
-Fix HSI Primary/Data Screen Conflict
-BCN info shows up in center DDI on CHK screen
-BALT engagement during TCN A/A ops
-CKL Display: NU/ND text spacing
-AA Radar Beam Sweep bar sweeps too far to the right
-Radar screen dissappears when entering AA or AG Master Mode prior to pressing RDR option
-Map display issues
-Refueling gauge auto-on/off when probe extended/retracted
-HUD Display not working on center DDI
-De-conflict WPT,TCN modes with map display modes
-Fix color of flight plan lines from purple to green
-HUD Diamond showing inaccurate data
-Fix to make compatible in STEAM
-TACAN Box not showing up on HUD
-"ON" indicator on scratchpad for TACAN data
-Install UFC background screen images/textures
-Waypoint into and ILS bars on HUD synced to DDI selection
-Map Scale not working on HSI
-Fix waypoint icon on HSI
-HSI display bleeding into Scratchpad
What's Next:
-Radar Contact Cycle/Selection: STILL WORKING THIS. Has proven a challenge for me to implement coding wise. But once it works, user will be able to cycle through radar contacts on their AA and AG radar displays, and target weapons appropriately.
-FLIR Camera: Still looking into this one. We'll see...
-ACL Page: Still digging into how the Automatic Carrier Landing display is going to work/function on the jet within FSX/P3D. Expect some type of operation that will allow the user to select some form of autopilot that will allow automated traps aboard the ship though...
-Fixing Bugs: Of course, this is always an on-going thing. Many thanks to those that have been reporting them! Might not have fixed all of the reported ones in this release, but we've going it recorded and slowly resolving them.
As usual, thanks everyone for the support and standing by for gripes, recommendations and feedback!
and....and....and as usual, I have done nothing with the 2 seater....
-
Great job as usual Jimi, looks great.
Thank you Sir. Would like to see a VFA-106 repaint.
Regards,
Reggie
Hey Reggie, if you are looking for the one they used during their demo season last year it is in the pack, but as VFA-15 since that's the markings on the jet... If you are looking for a combat one though, you'll have to talk to the GLS guys.
-
Thank you for this new version 18.3 !
The only problem is about the course (CSEL) that doesn't work, with the ILS it's impossible to set the desired course in the HSI, I mean : the digital readout changes in a strange way and also
during turns it change value (never seen this behaviour).
-
Thank you for this new version 18.3 !
The only problem is about the course (CSEL) that doesn't work, with the ILS it's impossible to set the desired course in the HSI, I mean : the digital readout changes in a strange way and also
during turns it change value (never seen this behaviour).
Good feedback! I'll take a look once I get back home. Thanks again.
-
Well, I seem to have done SOMEthing wrong.
I DL'd and installed the v18.3, and I have the red FCS FAIL across my HUD.
No matter what I try.
I DID copy the FSX Specific files into the Panel.Fleet folder, as I presume one must. I tried copying the Hornet_FCS.dll from the 17.1.31 into the Panel.Fleet folder. I even got wild and crazy, and copied the FCS and Gauges folder from the 17.1.31. No luck.
Do I need to make an entry in my DLL.XML for the Hornet_FCS.dll, maybe?
I'm doing something wrong. Any help would be HUGELY appreciated. I know, I jumped a few versions. The v18.3 SEEMS to fly like a dream, but I'd feel a lot better if that derned FCS FAIL message would be gone!
Derned thing, dag nabbit! :D
Pat☺
-
Well, I seem to have done SOMEthing wrong.
I DL'd and installed the v18.3, and I have the red FCS FAIL across my HUD.
No matter what I try.
I DID copy the FSX Specific files into the Panel.Fleet folder, as I presume one must. I tried copying the Hornet_FCS.dll from the 17.1.31 into the Panel.Fleet folder. I even got wild and crazy, and copied the FCS and Gauges folder from the 17.1.31. No luck.
Do I need to make an entry in my DLL.XML for the Hornet_FCS.dll, maybe?
I'm doing something wrong. Any help would be HUGELY appreciated. I know, I jumped a few versions. The v18.3 SEEMS to fly like a dream, but I'd feel a lot better if that derned FCS FAIL message would be gone!
Derned thing, dag nabbit! :D
Pat☺
As far as I remember, I didn't change a thing in the panel or anywhere else for this version. No FCS FAIL msg in P3Dv4.
-
Thank you for this new version 18.3 !
The only problem is about the course (CSEL) that doesn't work, with the ILS it's impossible to set the desired course in the HSI, I mean : the digital readout changes in a strange way and also
during turns it change value (never seen this behaviour).
Good feedback! I'll take a look once I get back home. Thanks again.
Ok, I've forgot to mention that my platform is FSX-Gold / Windows 7
64 bit THANK you
-
Well, I seem to have done SOMEthing wrong.
I DL'd and installed the v18.3, and I have the red FCS FAIL across my HUD.
No matter what I try.
I DID copy the FSX Specific files into the Panel.Fleet folder, as I presume one must. I tried copying the Hornet_FCS.dll from the 17.1.31 into the Panel.Fleet folder. I even got wild and crazy, and copied the FCS and Gauges folder from the 17.1.31. No luck.
Do I need to make an entry in my DLL.XML for the Hornet_FCS.dll, maybe?
I'm doing something wrong. Any help would be HUGELY appreciated. I know, I jumped a few versions. The v18.3 SEEMS to fly like a dream, but I'd feel a lot better if that derned FCS FAIL message would be gone!
Derned thing, dag nabbit! :D
Pat☺
As far as I remember, I didn't change a thing in the panel or anywhere else for this version. No FCS FAIL msg in P3Dv4.
Thanks Raz, but I have FSX:SE. That's why I copied the files from the FSX Specific folder over to the Panel.Fleet folder. I presumed they were necessary. I will try again with the unchanged Panel folder, though, and see what happens.
Thanks very much for the response, though!
Pat☺
-
Pat,
Have you tried selecting different jets? Are you getting the same thing for each one?
No special steps should be required. Especially if you've had any of the 18 series or the 17.3 jet working before. Check to make sure that the door file names jive between the actual file name and what's listed in the panel.config.
-
Great job as usual Jimi, looks great.
Thanks Razor!
-
Check to make sure that the door file names jive between the actual file name and what's listed in the panel.config.
I've never heard the term "door file" before, but I believe that it refers to the names before the ! in a gaugeXX= line.
I checked, and yes, they match. Even to the .xml files involved. The file name following the ! .
I don't have TacPac. Could that be the trouble?
I removed the v17.1.31 from the ...\Airplanes folder. I just cut-n-pasted it over to my C:\ drive. I'm going to put it back and ensure IT still works right now. Not a problem if there are duplicate airplane neames. THAT I can fix.
Have you tried selecting different jets? Are you getting the same thing for each one?
IE: different jets in the 18.3? Strangely, no, I keep using the VF-25 CAG bird. I will try selecting several others at random, and see what happens.
Thanks for the quick response, Jimi. More to come asap. I will also verify the correct .NET is still installed and running, as required.
Pat☺
Late update:
Boy, now I've done it!
I copied my v17.1.31 back over, and now IT'S got the FCS FAIL message. It was working perfectly before I installed the v18.3 . I have NO idea where I went wrong.
I plan next to re-download both versions from page one of this thread, and re-install them one at a time.
I thought the v17.1.3 had an auto-installer, but the one I have doesn't. My memory doth sucketh...
As I said before, I'll also re-download and install the .NET Framework. I have a sick feeling it may have gotten corrupted, and may be my problem.
I WILL overcome!! You just wait and see :D
Pat☺
-
Hi Pat,
I don't know if it can help but I had the same problem with the 18.2 version.
As Jimi told me I reinstalled the Visual C++ (×86) and everything started to work fine.
Even the new 18.3 flies like a juwel, without red messages.
Greetings from Switzerland. Lucame
-
Hi, lucame, and thanks for the answer!
Just so you know, the C++ Redist is the file I meant I was going to re-install. I get the C++ Redist and the .NET Framework mixed up every time. My brain adamantly refuses to remember that the C++ is for the F/A-18's FCS, and the .NET Framework is for AICarriers.
I did DL and tried to re-install the C++, but it won't let me because a "newer version is installed and operating". I really don't want to uninstall all the other versions I have running, but we'll see what happens.
I also re-downloaded and re-installed the v17.1.31, and I will get in and test it as soon as I am able. About an hour from now :D
Pat☺
-
As Jimi told me I reinstalled the Visual C++ (×86) and everything started to work fine
Well, I uninstalled, and reinstalled, the C++ Redist.
No help. I only have the v17.1.31 installed so far, and I still get the FCS FAIL message on the HUD.
However: Did you need to reboot after you reinstalled?
I didn't reboot after either step. Hmm...
Mayhap that's needed... ???
Pat☺
-
I just downloaded the 18.2 and the C++, let the autoinstaller run, copied and pasted the Hornet FCS.dll file (32bit) in the Panel.fleet folder, started FSX and the plane was there without messages on the HUD.
Best wishes Lucame
-
Ok, well, I've un-installed and then re-installed the C++ Redistributable 2015, and every version of the Hornet back to the v17.1.31.
No good.
Still have the friggen FCS FAIL on the HUD. I am going nuts. On every version I've re-installed I have the failure message.
A side note: I noticed on the v18.3 when I set the Course on the HUD Control Panel, Nav1, the readout on the left MPD HSI lower right corner, where it says CSEL, it doesn't match the HUD Control Panel's display. IE: I set 136 on the HCP, but the HSI reads 189. The ILS indication, IE Which way it points, the long ILS bar in the HSI with the middle line up bar, matches the HUD Control Panel's setting.
Have fun, gang. I'll get this yet, you wait and see!
Pat☺
-
Thanks for the heads up Pat. Have you tried installing the C++ as administrator?
-
That's the only way I run software, as Admin. Installation programs, 7Zip extractions ( well, 7Zip program, anyway :D ), FSX:SE, you name it. If I "run" it, I run it as admin. Invariably. :)
I did run into one interesting thing, though, that I don't recall when I first installed C++ Redist. 2015. It wouldn't run, at all, unless I ran it as Windows 7 compatible. I seem to recall being able to just run the installer before. This time I had to select Win7 Compatible before the installers would even try to run. When I set the compatibility, I also selected Run As Admin. Was that insufficient?
I can try uninstalling and re-installing it again, but this time rclicking the installer and selecting the Run as Admin choice.
I'm up for trying anything, now. I miss my Hornet!! :'(
It is SO much fun to fly, and all this messing around is really getting annoying. :P
Thanks for any and all help, I really appreciate it.
Pat☺
-
v 18.3
win10
FSX ok
FSX Steam ok
winXP
FSX FCS FAIL
FSX Steam FCS FAIL
-
Thanks Cobra.
I have Win7, if it matters, and am getting the FCS FAIL message too.
I only have FSX:SE, so I can't say if FSX (not SE) has the same problem, but I'm going to presume...
Thanks for the info, Cobra. At least I'm not the only one :P
Pat☺
-
In P3D V4.2 also getting a FCS Fail in HUD. Weird. . . Great plane though!
-
I hate to say it, but given the variety of platforms, and OS's, that seem to be having the same problems, I have to wonder if it's not something with the newer version of the HornetFCS.dll?
I can't think of what I'm missing. Could the F-18.dll have gotten corrupted somehow?
I even went through the FSX.cfg file, and got rid of all the old HornetFCS.dll entries under the [trusted] heading. I made it re-accept the HornetFCS.dll. Just in case it was trying to use an older version that no longer existed. No help.
I went into the gauges folder, and deleted the HornetFCS.dll there, no help.
My next step is go back to the previous, lengthy, thread, and downloading the "updated" HornetFSC file and trying that, just in case. Maybe it'll work, at least for the FSX versions...
We'll get it, you all wait and see! Now, I'm really wishing I were a .dll programmer :D
Pat☺
-
Since I put the older one in, the problem went away . .
-
Maybe it wasn't such a bad idea then!
I can't get to it right this minute. Today I get to get the weed-whacker going for the summer. Weeee-HA!
It died last fall. Won't start. So I'm going to strip it, clean the carb, readjust the mixture, since we're up at 5,000' MSL.
Not supposed to, but I aint gonna pay someone to do something that simple.
Heck, just move the mixture lever, set the prop to the right RPM...
Oh, wait, this isn't an airplane, is it? Darn... ::)
Have fun all!
Pat☺
-
Pat,
Orion brought up an idea, maybe reset your FSX.cfg by deleting it in AppData/Roaming etc, fire up FSX and let it create a new one, and see if it asks you to run the gauges. Make sure to click yes.
Other than that make sure that you are using the 32 bit FCS file and not 64 bit. Pretty sure you've done this already, but doesn't hurt to check again.
Jimi
-
Jimi,
first off congrats and thank you very much to you and the team for the outstanding effort you are putting into this aircraft and
for making at available for free!
I've encountered one issue (maybe or probably its just me acting dumb ;) using the new version 18.3 in FSX SE.
So far I've been unable to bring up the ILS / TCN for Javier's Nimitz carrier which I added into FSX via the aicarriers.net software.
Somehow I can't get the "OF" in front of the freq on the UFC to turn into "ON".
I did the following steps on the UFC, press TCN, press 11200 , press ENT and additionally on the HSI MFD I selected the TCN softkey.
But the frequency stays "OF" and no needles are displayed.
I also tried entering 57X instead of 11200, same result, "OF" and also tried ILS instead of TCN selection.
Probably I'm missing something obvious, but could someone kindly provide a short step by step walkthrough on how to get this going?
Selecting a landbased VOR by using the above method works fine, OF is replaced by ON and the HSI shows bearing and HUD pointer
appears along with DME info.
Thanks a lot in advance,
Kind regards,
Oliver
-
Hi, Oliver :D
Just so you know, the various carriers TACAN channel never show "ON" on the UFC. They work, they just don't show the "ON" you're looking for.
Did you turn the ILS needles on on the HUD Control Panel? They're off by default in this version. You can have them ON by default if you want to edit the correct .ini file. I can tell you how, if you desire. But as it stands, you have to call up the HCP, SHFT+2, and click the ILS button so the upper half of the button is illuminated.
They also only show if you are within 15° of the "runway", horizontally and vertically, and inside 15 NMi. range.
A great way to tell if the plane is picking up the carrier is to look on the HUD for the TCN range indication to appear on the HUD, lower right side. Also, the NAV1 needle on the HCP will be "hunting", or jumping very rapidly back and forth without you touching the knob. Of course, you must have NAV1 selected as your source. The toggle switch above the NAV select knobs on the HCP. It should have NAV1 as it's default, but if you're not sure, click it though it's cycle a couple times, making sure it lands on NAV1.
Hope this helps a little...
Pat☺
PS: Jimi, thanks for the advice. I will try it ASAP. Although I am NOT looking forward to adding back in all the changes I've made to it over the years :o
Cut-n-paste is my friend :D
I have been having a small problem with the Social Security admin, so I've been spending time focused on that. Once I get that squared away, I'll be able to focus better on this great plane.
Thanks again!
Pat☺
-
PAT,
Copy all. Good luck.
OLIVER,
Thanks for the good words, I'll be sure to pass them along! In regards to your observations, thanks! I'll put in on my "Fix List". Hopefully it will get fix and incorporated in the next release.
Thanks again!
Jimi
-
Pat before you delete your config change .cfg to .txt. same as deleting but saves your config to .txt in case it does not work. You can delete new config and go back to the old.
-
That's what I did, Az.
Well, similar, with the same effect. Changed the name to FSX_HORNET_TEST.cfg.
Now, this is where things got weird.
The sim made the new fsx.cfg, as expected. All default settings. No problems so far.
I got in, changed the display resolution to match my desktop's resolution. Got all the other settings where I like them. Called up the FSXBA Hornet, as usual. It loaded up, no trouble.
AND no asking if I want to permit the HornetFCS.dll, or the dsd_sound gauge.
I opened the newly made fsx.cfg file, and lo! The [trusted] section was just chock full of existent gauges, including the HornetFCS.dll, and a number of others. None of which were I queried about. The sim apparently "assumed" I would approve all these gauge files, and just went ahead and added them to the fsx.cfg file all on it's own!
Ok, well, this is weird. I am now running the file verification Steam provides. We will see what happens. I checked though, and while it approved the HornetFCS.dll all on it's own, I STILL have the FCS FAIL message.
More to come on this little adventure as soon as I can.
I sure appreciate all the help and advice I am receiving, by the way.
Pat☺
-
Pat,
In this case, delete all of the entries that contain the Hornet.dll, SAVE and re-open FSX...
-
Ok, here we go with today's interesting trouble shooting :P
I deleted anything in the fsx.cfg that had "HornetFCS.dll" in it. Double checked it with the Find feature, all using NotePad. Opened as Admin, as usual. Saved it off, and closed it. I deleted all versions of any form of F-18, except the default.
Opened FSX. Loaded the default F-18, no problems. Rechecked the fsx.cfg file, no HornetFCS entry of any sort. So far, so good. Closed FSX, and loaded the v17.1.31. Started FSX, and selected the v17.1.31 from the menu, as usual. Before selecting Fly Now, I checked the fsx.cfg, the 2 entries for the v17.1.31 were there, as I expected.
Not what I'm used to from FSX, as it never popped up the little windows asking if I wanted to trust etc etc., but it seems Steam changed FSX somehow so that it doesn't any longer.
Selected Fly Now, and once it loaded, got the FAIL message on the HUD. As I expected. Including to two warning lights on the Warning Light panel. FCS HOT and Bus Tie Failure. As expected.
Ok, as a test, I copied the entire Panel.Fleet from the v16.1 into the v17 folder, as Panel.Fleet1, and assigned an entry in the aircraft.cfg to it. Shut down FSX. Restarted FSX, and selected the plane I'd chosen for the v16 panel. So, now I'm checking the v17 plane, with the v16 Panel.Fleet folder, including it's own, older version of the Hornet.FCS.dll file. A panel I KNOW worked previously. Flashing FCS FAIL on the HUD.
Selected a plane with the v17 panel, the FCS Fail wasn't flashing, but still there.
Double checked the C++ Redist 2015. The X86 version is still properly installed. I even uninstalled the X64 version of it, to be certain. No help.
Something on my system is keeping any plane with any HornetFCS.dll version from functioning. No idea what/why/where/how, yet, but I'll get it figured out. Sooner or later. The .dll file is making a call to SOMEthing on my system that is missing. I'll get it yet. I'm closing in, and I think I've eliminated the actual HornetFCS.dll file as the problem...
I'll keep working when I can on this.
Pat☺
-
interesting.... you got anti virus? Try disabling it and giving it a go.
-
Yes, I do have AV.
Turned it off, and no luck.
Good idea to try, though, Jimi. Thanks for the idea.
We'll find it eventually, and I'll feel like an idiot for not realizing it was XXXXXXXX all along, if you see what I mean.
Pat☺
-
Ok, well...
I've re-installed Simconnect (all 3), C++ Redist 2015 (X86), FSUIPC v 4.974b, and even .NET Framework v4.6.2 .
Rebooted after each new install, installed all "as Administrator".
No luck yet, but I must be closing in. Not much left to check on :P :D
Pat☺
-
Pat,
If possible, can you post up both your aircraft.cfg and panel.cfg? I would like to take a look. Thanks.
-
Hi jimi08,
First of all, congratulations on this beautiful aircraft
I recorded a short video in which I indicate how I proceeded to get the TACAN / ILS in the HUD and the result for the deck landing.
If you wish, I can send you the ContentErrors.txt which reports many errors, especially in the gauge FA18_HUD_VC_R.xml.
(sorry for my poor english ;))
https://youtu.be/TIcAz8LH908 (https://youtu.be/TIcAz8LH908)
Best regards,
Jean
-
Jean,
Thanks for he good words! I'll be sure to pass them along.
Took a look at your video. Very interesting. Although I've done some work recently to the CRS display and functionality, I'll take another look.
And yes. Please send me the Content Errors.txt if you don't mind. Thanks!
Jimi
-
Here, the ContentErrors.txt file from P3D v4.2.
Jean
-
Glad to, Jimi.
ANYthing that might be of help. They are both from the v17.1.31, and they are both "out of the box". I've made no changes. I was considering adding the 2D HUD in on [Window0], but I've uninstalled and re-installed so many times, I thought I'd just leave it.
Hope something in these is the trouble, that I'm just missing somehow...
Pat☺
-
Here, the ContentErrors.txt file from P3D v4.2.
Jean
Merci
-
Glad to, Jimi.
ANYthing that might be of help. They are both from the v17.1.31, and they are both "out of the box". I've made no changes. I was considering adding the 2D HUD in on [Window0], but I've uninstalled and re-installed so many times, I thought I'd just leave it.
Hope something in these is the trouble, that I'm just missing somehow...
Pat☺
Took a looks, but I don't see anything out of the ordinary. Sorry Pat...
-
I was hoping :D
I have to work on my truck for a few days, so I'm taking a short break. I'll get back at it as soon as I can.
Thanks very much for all the help and ideas I've received so far, everyone! Maybe this break will let my little pea-brain mull things over and come up with something. ;)
I'll get it. I'm persistent :P ::) ;D
Pat☺
-
A fairly infrequent poster here, my two cents . .
I had not flown this one for a few years. Seeing the thread over at SOH http://www.sim-outhouse.com/sohforums/showthread.php/107165-FSXBA-Hornet-(ver-17-30) and having converted exclusively to P3Dv4 I downloaded a couple of weeks ago the v17.1 followed the install instructions somewhere (not sure where these are now?) and either didn't have or managed to get rid of the red "FCS FAIL" in the HUD. All was good.
BUT . . I yesterday went to fly 17.1 and low and behold there was the "FCS FAIL" and I could not get rid of it. Moved 17.1 to the hangar, downloaded 18.3, moved the HornetFCS_Data.CAB into, first, the Panel.Fleet and then within that folder, the Gauges folder. No luck. FCS FAIL here to stay.
A wild theory, as I had done nothing whatsoever to the 17.1 install between it working and not working: would a Microsoft Update (am on W 7 Pro 64 bit) mess this up for me and others?
PS - where do I find definitive installation instructions for 18.3 P3Dv4? Also, the aircraft is awesome and was doing for the first time some acceptable trap scores in vLSO within 10 minutes of downloading - thanks for this!
-
Expat,
If I remember correctly, the 17 series Hornet worked for FSX and the earlier versions of P3D but not P3Dv4.
Based on what you've written, it sounds like you put the HornetFCS.dll into the following folders:
-P3D/SimObjects/Airplanes/FSXBA F........./Panel.Fleet
-P3D/SimObjects/Airplanes/FSXBA F........./Panel.Fleet/Gauges
Try this:
-Take the HornetFCS.dll file and place it in the following folder:
-P3D/Gauges
Restart P3D and try again.
Let me know if this fixes your issue.
As for the definite installation instructions, I do not have any. I guess I can type up a "read-me" and also add the basics to the front page of this tread when I get some time. I'll also bring back the auto-installer (once I get the time)
Lastly, glad to hear about your trapping results! Just wait until you get the FCS working, should be even better!
-Jimi
-
IT'S GONE !!!
OK, did not work my first attempt - a bolter - but then I fished around some more in the P3D folder - moved (not copied) some files found there into main/gauges - and presto change-o no more FCS FAIL.
Re an auto-installer, I actually prefer manual downloads and installs so I know where things are going if I need to backtrack. Down side is if the there are additional manual steps - which I don't mind at all doing (part of the fun of this hobby is that it's like a kit you assemble) the install instructions may need to be 100% precise or unhappy campers. But then precision is our middle name naval aviating . .
Now, question, what exactly is FCS and what does it do?! :)
-
And speaking of precise, I started off with v 18.3 - not 17.1 - just so others troubleshooting this know this. All in P3Dv4.1.
Still a mystery though what caused the problem between flights in 18.3 without doing a thing to the install . .
-
Now, question, what exactly is FCS and what does it do?
Flight Control System
-
question, what exactly is FCS and what does it do?! :)
Azframer is correct, Flight Control System.... More specifically, it's a series of Proportional Integral Derivative (PIDs) that controls the Pitch, Roll, Yaw, Flaps and Trim systems of the aircraft. These PIDs constantly monitors what the aircraft IS doing and what the pilot WANTS to do and works to drive the difference to zero. It is our tool that allows us to mimic as close as possible the control logic of the real jet based on what we know and our math/coding abilities
......................................................Inhales...........................................................
What does it (the gauge in particular) do?.... a few things...
3-AXIS FLIGHT CONTROL
With most FSX aircraft, user input is directly translated to control surfaces (i.e. flight stick controls elevator position). For example, if you pull all the way back on your flight stick or yoke, the elevators on the aircraft will deflect all the way up. This will occur regardless of the aircraft's attitude, airspeed or configuration.
With the Hornet, things are a little different. The FCS basically asks the pilot: "What do you want the aircraft to do, and I'll move the elevators, ailerons, rudders and flaps to give you what you want." With that being said, your flight stick now controls G, Pitch Rate, AOA and Elevator Positions depending on the airspeed and aircraft configuration. For example, at 400 KIAS, you pull back on the flight stick a little. The FCS registers that position of the flight stick to equate to about 2.0 Gs. The FCS then deflects and constantly adjusts the elevators to give you the 2.0 Gs that you've "asked" for. Let's say you accelerate up to 600 KIAS, and pull back on the flight stick the same amount, the FCS again registers that you are still asking for a 2.0 G pull, but also understands that you are traveling through the air much faster and therefore will not require as much elevator deflection to give you the 2.0 Gs that you asked for, so it adjusts elevator output accordingly.
There are two primary modes, Up & Away (UA) and Powered Approach (PA). The modes are controlled by Flap Position. UA mode is entered when the flaps are placed in UP/AUTO, and PA is selected anytime the flaps are placed in HALF or FULL.
UA Mode
UA mode is much like what I described above, and rings true (as close as we can tweak it anyways) for airspeeds above 310 knots, below 310 knots, the system starts blending G command with Pitch Rate command, and eventually your flight stick will control only Pitch Rate at around 250 knots and below.
There is an exception to the logic however.
-If the jet is at 22 degs AOA and above, above 22 degs AOA, your flight stick starts blending control of Pitch Rate with Angle of Attack and after a certain point, your flight control stick will command AOA only (up to about 35 degs AOA).
-Another is when
PA Mode
With PA mode, your flight control stick now tells the FCS to adjust the elevators to maintain a certain Angle of Attack.
Pitch Auto Trim
IN UA Mode, the FCS also works to automatically trim the jet to 1.0 G when no control input is detected from the pilot. Trim has to be set to neutral (0) for for this. Any nose up or nose down trim will bias the system to stabilize with greater that 1.0G (NU), or or less than 1.0G (ND) trim. In PA Mode, the FCS works to use trim to maintain the trimmed AOA.
The FCS also controls the ailerons for roll control and also the rudders to automatically keep the aircraft coordinated during turns.
FLAP CONTROL
The FCS also controls the leading and trailing edge flaps. The FCS controls their scheduling based on flap switch position, airspeed and angle of attack.
AUTO THROTTLE
The FCS.dll for this jet also controls the Powered Approach Auto Throttle logic that attempts to maintain the jet at optimal AOA/Landing Speed when Auto Throttle is engaged while in PA Mode.
NOSEWHEEL STEERING
Lastly, the FCS.dll controls the Low and Hi Nosewheel steering, switching to a higher caster angle when airspeed is below 10 KIAS (i think). This allows for sharper turns while taxiing at lower speeds and more stability during higher speeds.
......................................................................exhales....................................................................
Probably more than you were looking for, but that pretty much sums up what the FCS is and what it does for our jet. All credit goes to ORION and his awesome math and C++ coding abilities for this awesome gauge!
-
Hugely helpful - thanks!
And, I noticed the effects you describe of FCS immediately in flight, the auto trim in particular works well and is useful.
-
I GOT, I GOT IT!!!! I FOUND THE PROBLEM!!!
Somehow, of all things, my FSUIPC got corrupted. I didn't see it in the ADD-ONS menu. I don't even recall why I was looking there. I ran it's installer again, and LO!!, no more FCS FAIL! :P 8)
Oddly, all my other planes, not that I have a ton of them but still, never had a bit of trouble, and I am certain some of them, and their gauges, use FSUIPC also.
I will go on a thorough test flight of the v18.3 tonight, and see how she flies. I am SO HAPPY!! ;D
I can't thank you all enough for your assistance in this little situation, I really can't. My flight sim world is back on an even keel, and the seas and skies look clear, smooth, and ready to accept this incredible bird once again.
In some time, not for a couple weeks, I'll try and figure out my FSUIPC's problem. I'll report on what I dig up, just in case anyone else runs into this odd little piece of trouble. I have a sneaking hunch it has to do with an update I may have done, but I'm not going to say anything until I know for certain.
I'm going flying!!
Pat☺
-
Outstanding! Glad you found the culprit.
-
Outstanding! Glad you found the culprit.
Heh! You think you are? :D
Thanks again for all the help, Jimi.
AND all the rest of you that had such great ideas.
I do sincerely appreciate it.
Pat☺
-
Lol, wish I can I helped, but that was all you bud. Definitely learned something new with this one. Thanks again for keeping us updated.
-
@jimi08
"AUTO THROTTLE
The FCS.dll for this jet also controls the Powered Approach Auto Throttle logic that attempts to maintain the jet at optimal AOA/Landing Speed when Auto Throttle is engaged while in PA Mode."
How can I "engaged" the Auto Throttle ?
Jean
-
Cntl + R. Should get a "ATC" indication on the lower right side in you HUD.
-
Hey Gents,
Long time no talk to. I'm really enjoying the new jet like the rest of you guys and this question is for Jimi. Hey bro, is there a ETA on the release for the fix for the Blues airbrake fix? I think it's in the Blues cockpit model. reason being, is when you deploy the airbrake you don't get the indication light on the left of the UFC and it doesn't seat completely down but the tactical models do. I've tried the Charlie and Delta pits. I was just wondering if you've fixed it yet, because I mainly fly Blue #7. O, and I also wanna know can you increase the sound files? They're waaay lower than the Acceleration Hornet. Thanks again for this great jet you've given us bro!!
-
Cntl + R. Should get a "ATC" indication on the lower right side in you HUD.
Thank you jimi08. I will try this ;)
P.S. :
It did not work. Maybe I'm not in the right flight settings? (Not in PA mode ?)
-
It did not work. Maybe I'm not in the right flight settings? (Not in PA mode ?)
Try SHIFT + R instead...
-
I use SHFT+R and it works for me.
Assuming you're in PA mode. Full flaps, gear down, speed correct for the plane's current gross weight, trim at 8.1°, which it SHOULD do automatically for you. AOA somewhere close to optimum. I usually don't switch on the ATC until I'm on downwind, and everything else is already set.
Remember, in ATC mode, you adjust the glide slope with the pitch angle, using the stick, rather than the throttle, like usual. It can be hard to get used to, if you're used to the usual approach method of pretty much leaving the pitch angle set, and adjusting your sink rate with the throttle.
Good luck!
Pat☺
-
Thanks jimi08 and Pat.
Shift + R works.
But, although I'm in the parameters (flaps, speed, angle of attack, gear and hook down) the PA mode does not seem to be activated.
For me, it is easier to make corrections with pitch and throttle.
Jean
-
Hi Jean,
May I ask, how do you KNOW you're not in PA mode?
There's no indication of it anywhere I'm aware of. It's just the way the FCS flies the plane that changes. Jimi gave some good info about HOW the FCS changes way it flies the plane above.
When you start into the approach are you below 33,000 Lbs gross weight? Does the pitch trim change to 8.1° as it's supposed to? YOU don't change it, the FCS does it for you, all other parameters being correct. That's one indicator the FCS is in PA mode.
When you first start to go into approach mode, is your pitch trim zero? IE: When you first start to slow to begin your approach, do you ensure your manual pitch trim is zero NU/ND? You can see an indication of your manual pitch trim on the Checklist page of any MFD.
When you select Flaps during the mode change, do you go to Flaps FULL, or 1/2? They should be in FULL.
Once you've activated the ATC, do you change the throttle beyond 90%/20% manually? That will deactivate it, and you would then need to reactivate it with SHFT+R again. Do you ensure your throttle is between 90 and 20% before you try to activate the ATC mode?
Ok, ok, shutting up now...
Pat☺
-
When you first start to go into approach mode, is your pitch trim zero? IE: When you first start to slow to begin your approach, do you ensure your manual pitch trim is zero NU/ND? You can see an indication of your manual pitch trim on the Checklist page of any MFD.
Hi Pat,
Thanks for your answer.
It's my mistake, I had set the trim to 8.1 ° manually.
After test, everything is ok now.
(and don't shut up) :D
-
I GOT, I GOT IT!!!! I FOUND THE PROBLEM!!!
Somehow, of all things, my FSUIPC got corrupted. I didn't see it in the ADD-ONS menu. I don't even recall why I was looking there. I ran it's installer again, and LO!!, no more FCS FAIL! :P 8)
Oddly, all my other planes, not that I have a ton of them but still, never had a bit of trouble, and I am certain some of them, and their gauges, use FSUIPC also.
I will go on a thorough test flight of the v18.3 tonight, and see how she flies. I am SO HAPPY!! ;D
I can't thank you all enough for your assistance in this little situation, I really can't. My flight sim world is back on an even keel, and the seas and skies look clear, smooth, and ready to accept this incredible bird once again.
In some time, not for a couple weeks, I'll try and figure out my FSUIPC's problem. I'll report on what I dig up, just in case anyone else runs into this odd little piece of trouble. I have a sneaking hunch it has to do with an update I may have done, but I'm not going to say anything until I know for certain.
I'm going flying!!
Pat☺
Great catch PhantomTweak! Just getting back in the cockpit of my gaming FSX machine after a couple of months away and I had the same after the install. Pretty sure I moved files correctly, but I assumed along with the other updates on my machine I also needed to check FSUIPC. Holy 80+ repaints, Batman!
-
Here is a different texture set for the cockpit of this marvelous aircraft for anyone who wants a more "worn" look. They are by no means perfect, and may even still be a WIP (if I can find time to keep refining them).
Full disclosure - I have borrowed some elements from the default F18 pit, as well as adding some of my own tweaks, but kept the majority of the original button and switch panels. Some of the textures are stretched simply by the model itself so may look a bit low-res.
I have also included the original texture set again in case someone installs this, doesn't like it, but then realises they've overwritten their originals.
https://drive.google.com/open?id=1jfdtcXHvVkruuSUE7weJURMPjwXFgRoX
Before and after shots in the zip file.
-
Awesome! Can't wait to check them out once I get the chance. Thanks!
-
Thanks Kea, about to work the model into my recent P3D install. It's a legacy Hornet, it should have a worn out, "been on the boat too long" look to it.
-
Thoroughly agree Victory.
-
Can you guys post pics of the cockpit when able? Thanks.
-
https://i.imgur.com/vz3JkGG.jpg
https://i.imgur.com/FhyoPeM.jpg
Regards ;D
-
Outstanding. Thanks!
-
Beautiful job on these! Everything seems pretty straight forward and they fly great. I downloaded FA-18C_FSXBA_BA_18.3.00.P3D.zip and installed it. The only thing I have been unable to do is to get the hook to engage the arrestor cables. I'm using AICarriers (non java) All my carrier landings are touch and go. When the FA-18 loads in P3d V4 it complains it is unable to find a config file and says it uses E:\Prepar3d\guages\dsd_p3d_xml_sound_x64.ini. When I open it in P3d V3 it gives no error. In either of the Lockheed sims the arrestor cables don't engage. I have not tried it in FSX. Any idea what my problem is?
-
Hey Jring,
Glad you are enjoying the jet and thanks for the good words!
As for the sounds file, should be an easy fix.
1. Simply go to the Lockheed Martin/P3Dv4/Sim Objects/Airplanes/FSXBA FA-18..... and look for a folder that says something like "For P3Dv4". I'm away from my gaming computer at the moment, but it should be in either the main FSXBA FA-18 folder or in the Panel.Fleet folder.
2. In there, you should see the dsd_p3d_xml_sound_x64.ini file that is missing. Simply copy and paste that file into the Panel.Fleet folder (one level up).
3. In the same Panel.Fleet folder, you should see a file called "Panel.cfg". Open it with Notepad and locate the " [Vcockpit01] section.
Change this:
gauge20=dsd_fsx_xml_sound!Sound, 2,2,2,2, \Sound\Sound.ini
To this:
gauge20=dsd_p3d_xml_sound_64!Sound, 2,2,2,2, \Sound\Sound.ini
4. Save the file, close it, and restart FSX/P3D if you currently have it open.
As for the hook issue, I'll have to dig into that once I get home. Until then, I'll start with the basics....
-How are you lowering the hook? (i.e. clicking switch in cockpit or using an assigned key or switch)
-Have you visually verified that it is down? (i.e. the hook lever shows down, the shows down from external view) Is it remaining down once place in the down position or does it quickly retract to the up position on its own?
For the sake of testing, try clicking on the hook lever in your virtual cockpit to lower it, verify that the hook is down and attempt a landing.
If it still doesn't work, try assigning a button or key to toggle the hook up or down, lower the hook, verify visually and attempt a landing.
If it still doesn't work, report back here with your findings and we'll look at some other variables.
Hope this helps...
Jimi
-
Just to help a little, there is a dandy add-on, that uses AICarriers.NET to add an FLOLS trailer and functional arresting gear to the airport of your choice. Might be a handy way to do the landing tests Jimi recommended.
After all, shore based airports don't move around, or have Angle Decks like the carriers do. ;D
Anyway, you can find it here: https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=131878 (https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=131878).
It's for FSX Acceleration, but it might work in P3D. I don't have P3D, so I can't test it myself.
It seems like the landable AI carriers made for FSX, as well as AICarriers.NET, work just fine in P3D, so I suspect this might as well.
By the way, do you use the default key combo for lowering the hook, or do you have it assigned to a joystick button? If you use the default key-combo (SHFT+Q in FSX) ignore everything that follows.
If you assigned the hook to a joystick button, have you checked to make certain there's no other action assigned to that key? There might be a conflict with another assignment.
Do you have the Repeat slider in the center, full left, or full right? I think, if you have the Repeat slider in the Key Assignments window full right, it might be lowering, then immediately raising the hook again.
Worth a look, anyway.
As I said, though, if you simply use the default key-combo, or the lever in your VC, ignore everything I just said :D
Hope this is of some help...
Pat☺
-
Thanks for the input. I have been using the assigned shift/Q as the trigger and it shows the hook descend. I am not able to do any testing atm but should be able to tomorrow. I will use the VC lever and give it a try. I am also installing another aircraft carrier aircraft when I get a chance to see if the issue is unique to the FA-18. I will test and let you know the results. Again thanks both for the input. I am pretty used to the pitching decks, though they do pitch way more in P3d V4 if you stir up the weather a little. :)
-
I am pretty used to the pitching decks, though they do pitch way more in P3d V4 if you stir up the weather a little. :)
Heck, those AI LSO's hate me enough as it is. I make the ship any "pitchier" my score's will go right out the porthole :D
Come the day I get good enough to get a decent trap every time (I may live that long, who knows? :P ), I'll use the software Pitching Deck to make things get more interesting. Add in a little weather, like rain and low ceilings, and two things will happen:
1) My scores will go to heck...again ;D ::)
And 2) I wager I'll have a lot more bolters.
Of course, maybe I'll come to appreciate the AI LSO's a bit more, under those conditions....
NAAAAhHHH!
:D :D
Have fun! I sure do!
Pat☺
-
PROBLEM FOUND AND SOLVED!!! :)
I installed a T45C from yesteryear into my P3d V3 and found the arrestor cables didn't work for that aircraft either, so knew the issue was the aircraft carrier. Found and downloaded an updated version of uss_nimitz_uss_eisenhower_v2. (I had been using an older version from my backup hard drive.) And again my complements on this aircraft! Drifts in like a dream and settles nicely on the deck. It definitely gives a nice feel in flying. Thanks for all the help on the error message. Landing FA-18's on the USS Nimitz used to be my favorite pastime. It will be again. :)
-
Bear in mind, and it may have just been the turn of phrase you used, but carrier-borne aircraft shouldn't "settle" onto the deck. They come DOWN. Hard.
Once you set up AOA, Pitch, and Power, keep it all the same, well maybe vary power a bit to control you vertical flight path, down to impact. Navy pilots NEVER flare. They PUT the plane on the deck, ship or shore.
It's called a "controlled crash" for a reason, after all :D
Javier's Nimitz and Ike V2 is the base carrier many use. I do. I use it the most often. It's certainly old, but one of the best. You would be amazed, however, at the number of other, more recent, carriers out there. The HUD only recognizes certain of them, however. Javier's Nimitz is the primary carrier for most, that's for sure. Glad you got everything working right, though :)
By the bye, if I may be so bold, I strongly recommend NOT adding any add-on ship formations of any sort to the base AICarriers.cfg file. Use the conf.d folder, and have the various add-on's .cfg files in a sub-folder under it. That way, you can swap them in and out, and you don't wind up with a SHFT+J menu with 10 pages you need to search through for the ship you want to use at the moment. Just a thought.
Also, remember to keep the plane's Gross Weight under 33K lbs to land on the boat.
You need 35 kts Wind Over the Deck (WOD), as well.
I get the boat set and moving with AICarriers, then add the 10 Kts wind down the angle deck's heading to make the 35 Kts required. The carriers travel at 25 Kts by default, and there's a way to edit the boat's .cfg file to make the ship go the right speed to make the correct WOD, but I'm lazy, and just use the weather settings built into the sim to accomplish it. That way, I don't have to remember which ships I've modified and which not.
Enjoy! The v18.3 certainly is a real joy to fly, isn't it??
Pat☺
-
Yup! Real joy to fly. And agree on 'no flare'. To better define 'settle" the aircraft holds its descent rate nicely.
-
Javier's Nimitz and Ike V2 is the base carrier many use. I do. I use it the most often. It's certainly old, but one of the best. You would be amazed, however, at the number of other, more recent, carriers out there. The HUD only recognizes certain of them, however. Javier's Nimitz is the primary carrier for most, that's for sure. Glad you got everything working right, though :)
Do you have some recommended links to other aircraft carriers that work with P3d V4?
-
Why, yes, yes I do! ;D
Look through this section of the SimOuthouse Library: http://www.sim-outhouse.com/sohforums/local_links.php?catid=114 (http://www.sim-outhouse.com/sohforums/local_links.php?catid=114)
Those are for FSX, but like I said, most if not all the carriers that work in FSX also work in P3D. You'll need to register on SOH to download anything, but it's free, and easy.
FS Shipyards is another. You can see the carriers here: http://www.fs-shipyards.org/index.php?ind=downloads&op=section_view&idev=1 (http://www.fs-shipyards.org/index.php?ind=downloads&op=section_view&idev=1)
You don't even need to register to download these ships.
There's a start. Or you can Google "Aircraft Carrier FSX" (no quotes). I've found that if you just search for "Carriers FSX", you wind up with a few million entries for various Air Carrier companies, which can conceal what you really want to find :D
Also, ensure they are capable of functioning as AI, and can be used by, or in, AICarriers. The ones that are AIC-capable usually have an AICarriers .cfg file included for you, so you can easily verify it.
Anyway, there's a good start. Remember what I said about not adding formations directly into the AICarriers.cfg file!
Once you get to really searching, you will be surprised how many there are. Both WWII, and modern types.
Have fun!
Pat☺
-
Do you have some recommended links to other aircraft carriers that work with P3d V4?
You have the French carriers "Charles de Gaulle", "Foch" and "Clémenceau" and some others here :
http://royalefrenchnavy.restauravia.fr/RFN-Creations.htm
Jean
-
Thanks Pat and Jean! A plethora of options!
-
Getting the dreaded FCS FAIL on the HUD. Read through the discussion with Phantom but those solutions don't seem to fix it on my end. Use P3D v4.3 and have a new FSUIPC. Tried moving HornetFCS.dll to P3D/Gauges folder as well but didn't work. Tried all 3 P3D versions.
Any install suggestions? I just dropped the whole folder into SimObjects.
Thanks! Love this bird!
-
Jason,
Just to clarify, did you drop it into SimObjects, or SimObjects/Airplanes?
-
Jason,
Just to clarify, did you drop it into SimObjects, or SimObjects/Airplanes?
SimObjects/Airplanes
-
Do you have the correct .NET Framework , Visual C++ Redistributable, Simconnect, and FSUIPC, versions installed?
Especially the last 3 I just mentioned?
Those can bite you if you'e not careful.
Versions you should have installed:
Visual C++ Redistributable v14.9.23026,
Simconnect v16.0.62615,
and the FSUIPC should be the latest from Mr. Dowson. I'm not sure what the latest version is for the P3D 64 bit.
Also, are you using the correct Hornet_FCS.dll version?
There is a folder included in the download .zip file called P3D Specific Files. The Hornet_FCS.dll included in the Panel.Fleet folder is for the 32 bit systems. FSX and the older P3D versions. You need to copy the files included in the P3D Specific folder to the correct places. I would rename the Hornet_FCS.DLL in the Panel.Fleet folder to something else, then place the one specific to the P3D 64 bit setup into the Panel.Fleet folder.
Not sure if all this will help or not. Just a possibility.
Pat☺
-
Getting the dreaded FCS FAIL on the HUD. Read through the discussion with Phantom but those solutions don't seem to fix it on my end. Use P3D v4.3 and have a new FSUIPC. Tried moving HornetFCS.dll to P3D/Gauges folder as well but didn't work. Tried all 3 P3D versions.
Any install suggestions? I just dropped the whole folder into SimObjects.
Thanks! Love this bird!
Hello,
I had the same problem after installing P3D v4.3.
All I tried was not successful, I still had the FCS Fail on the HUD.
The only solution was to replace the whole file of the Hornet in SimObject \ Airplanes, by that received from a friend who had not been concerned by this issue.
Jean
-
Do you have the correct .NET Framework , Visual C++ Redistributable, Simconnect, and FSUIPC, versions installed?
Especially the last 3 I just mentioned?
Those can bite you if you'e not careful.
Versions you should have installed:
Visual C++ Redistributable v14.9.23026,
Simconnect v16.0.62615,
and the FSUIPC should be the latest from Mr. Dowson. I'm not sure what the latest version is for the P3D 64 bit.
Also, are you using the correct Hornet_FCS.dll version?
There is a folder included in the download .zip file called P3D Specific Files. The Hornet_FCS.dll included in the Panel.Fleet folder is for the 32 bit systems. FSX and the older P3D versions. You need to copy the files included in the P3D Specific folder to the correct places. I would rename the Hornet_FCS.DLL in the Panel.Fleet folder to something else, then place the one specific to the P3D 64 bit setup into the Panel.Fleet folder.
Not sure if all this will help or not. Just a possibility.
Pat☺
Yeah i read through all your back and forth with Jimi and tried the C++ fix. I will double check the version number so thanks for that. And tried the Hornet_FCS.dll swap, even with the previous version marked Hornet_FCS64.dll. But I'll try the swap again.
Thanks Pat! By the way love your DCS posts. You got me hooked. I assume you're that same Pat "Phantom88" lol.
-
Thanks Pat! By the way love your DCS posts. You got me hooked. I assume you're that same Pat "Phantom88" lol.
Nope, that's not me. I use the PhantomTweak name everywhere.
It indicates what I did most of my time in the Corps. I was an Intermediate Level technician for the F-4 N/J/S Phantom II.
Component level repair and replacement on the Radar system sitting in that big, Jimi Durante style, nose they had.
We also fine tuned, or "tweaked" the system parts before we sent them to Supply for the Squadron's use. I spent a lot of time with a jeweler's screwdriver in my hand, adjusting potentiometers on circuit boards. Known as tweakin-n-peakin the system.
Hence, PhantomTweak. I "tweaked" Phantom radar systems :D
But I'm glad you enjoyed them anyway :D
Pat☺
-
Hi, Oliver :D
Just so you know, the various carriers TACAN channel never show "ON" on the UFC. They work, they just don't show the "ON" you're looking for.
Did you turn the ILS needles on on the HUD Control Panel? They're off by default in this version. You can have them ON by default if you want to edit the correct .ini file. I can tell you how, if you desire. But as it stands, you have to call up the HCP, SHFT+2, and click the ILS button so the upper half of the button is illuminated.
They also only show if you are within 15° of the "runway", horizontally and vertically, and inside 15 NMi. range.
A great way to tell if the plane is picking up the carrier is to look on the HUD for the TCN range indication to appear on the HUD, lower right side. Also, the NAV1 needle on the HCP will be "hunting", or jumping very rapidly back and forth without you touching the knob. Of course, you must have NAV1 selected as your source. The toggle switch above the NAV select knobs on the HCP. It should have NAV1 as it's default, but if you're not sure, click it though it's cycle a couple times, making sure it lands on NAV1.
Hope this helps a little...
Pat☺
Hi Pat,
I just installed the new 18.3 version (from the previous 17.3). Great improvements, thanking you, Jimi, and the entire team.
I am reading this thread about TACAN, and I encounter the same problem as Oliver, i.e., you can't enter directly a TACAN frequency (unless I am missing something), you can only enter the equivalent ILS. Version 17.3 allowed to punch the TACAN directly.
Hope that this can be corrected in the future.
But anyway, not a huge deal compared to all the new updates and immense work.
Thank you guys,
Johan
-
Yeah, that's a problem I noticed as well. In the v17.3, you could punch in 57X for the Nimitz, for example, and it would have the correct frequency in the NAV1 radio. Now, you have to actually enter the correct frequency, not just the TACAN number.
A small detail. No big, once I figured it out.
Is this setup true-to-life? I have no idea. More research is needed, at least on my part.
If it is, I am sure they will just leave things as-is. If not, they'll correct it :D
Enjoy!
Pat☺
-
Gents,
I'll give it a look/ once I return home and get the chance.
-
Hi, Jimi!
Good to see ya, as always :D
Take your time on this. Like I said, it's a small detail.
Another small detail: The CSEL line on the HSI, and the NAV line on the HUD (the little arrow line that points at the NAV1 source), go totally nuts when the NAV is set to a carrier, and you're within range of it. 99 miles I think is max range, isn't it?
The ILS system, the two line-up bars, works fine. The CSEL and NAV line work fine with airports. It's just with carriers they are all over the compass. It almost looks like they are going around in a circle, but if you watch them, they are randomly scanning through all headings.
I've looked at the HUD's xml files but I can't seem to see the trouble. What a surprise, huh? ??? :D
One last thing: I've been getting a lot of requests for at least the install instructions in a Readme file included in the download files. I know, they're pretty self explanatory, but still...
Could you either add a Readme file, or make the whole thing into an auto-installer, like it used to be? Including the download/install of the C++ Redist file it needs? It would be a big help. Also, where to get the FA_18.dll. A lot of folks only have P3D, and have never had FSX.
Just a thought :)
Have fun! We'll see ya when you get back. No rush, though...
Pat☺
-
Hey Pat!
Same here man. Greetings from Norway lol.
I'll take a look at the instrumentation when i get back and will start including the autoinstaller.
Thanks again.
-
Hello again!
Update to CSEL arrow difficulty. If you select NAV2 on the HUD Control Panel, the CSEL and TACAN direction arrow on the HUD stop their wavering, but nothing points at the boat. And yes, I did have 112.00 entered in both the ILS and TACAN windows, and ILS selected on the HSI.
Also, after numerous attempts, if BCN is selected on the UFC buttons, no numbers appear on the scratchpad display, and no key-presses show up on the scratchpad. Thus, no way to select the beacon to use.
I don't know if I'm doing something wrong, which as we all know is a very distinct possibility. :D
Good luck, and enjoy Norway! I'm still looking through the HUD and UFC xml's but so far, no luck.
A question real quick if I may: is there a difference between the paren symbol ( or ), and the bracket symbol { or }, in XML programming? I see some IF...ELSE statements have one symbol, some the other. Just curiosity, is all :)
Pat☺
-
The CSEL issue might be a little more complicated to fix. I'll take a look at it and the BCN once I get back.
As for the parentheses and squiggly brackets, yes there is a difference. Squiggly brackets "{ }" are used to define "if" or "els" statements, while parentheses "( )" are sure for Vars (A: or E: ), LVars (L:) and Key events (K:)
Hope this helps
Jimi
-
The CSEL issue might be a little more complicated to fix. I'll take a look at it and the BCN once I get back.
No hurry ;)
This is so much fun to fly, I'm in no hurry for anything. Of course, I'm too old and fat to hurry any way ;D
As for the parentheses and squiggly brackets, yes there is a difference. Squiggly brackets "{ }" are used to define "if" or "els" statements, while parentheses "( )" are sure for Vars (A: or E: ), LVars (L:) and Key events (K:)
Hope this helps
Yup! That was exactly what I needed to know. Thank you!
If I not extremely careful, I learn something new every day. It's simply amazing to me...
:o ;D
Thanks again Jimi! I appreciate all your hard work greatly. Just don't over-do and burn out! :P
Pat☺
-
Hi Pat,
I have 2 different systems in 2 different locations. One is running WIN10, and the F/A-18 is working great on it (thank you team!), and the other one is running WIN7 and the plane cannot be controlled: the stick is vibrating, the flaps are shaking, no rolling possible....etc. Did anybody encounter this problem? I updated FSUICP today (like you did a few weeks ago), and it doesn’t solve the problem.
My other planes (like the Sludge) are working fine with WIN7.
Thanks for you help if you can.
Johan
PS: my sim is FSX Acceleration on both systems
-
Hi,
can anyone help please?
I have installed the wonderful FSXBA F/A-18C and it flies great.
However I have tacpack, and while all the weapons show ok , I can't release any. Everything that is selected with the tacpack manager appears on the model and on the display. The only thing that works is the arming switch in the cockpit. None of the tacpack keyboard or stick commands have any effect.
Maybe I made a mistake with the install or I am missing some step. I couldn't find any details about this in the documents.
Could anyone advise, please?
jc ??? ??? ???
-
Sorry, I don't have TacPac.
Wish I could be more help on this. You do have all the requisite Simconnects, .NET Framework, C++ redistributable, and the latest FSUIPC, all installed?
I don't know if those will be any use here but heck, ya never know!
Another thought, do you possibly have the key mappings TacPac requires in use by something else? Like the release trigger is used for flaps extension or something?
You are arming up with the Master Arm on, correct weapon station selected, and A-A or A-G selected over on the left side of the main instrument panel? I am not sure it's necessary, but do you also select the same mode and arming on the HUD Control panel? Do you have a target locked in of the correct version, like another airplane or a ground target?
I'm just guessing. Throwing out possibilities I think of...
Hopefully something in my babbling can be of use.
Pat☺
-
JP1,
Did you select the particular weapon to be used in the DDI prior to trying to release the ordnance. If not, follow this procedure:
1. Click on AA or AG Master Mode button
2. In the DDI, go to MENU > SMS
3. From there, click on the softbutton (grey button) next to the weapon to be used. Once clicked, a box should appear around the selection indicating that it's now selected.
4. Arm the jet, by clicking on the MASTER ARM switch
5. Press the Pickle Button (for AG ordnance) or pull the trigger (for AA ordnance) to deploy selected weapon.
I'll have to recheck the coding, but I don't believe there are a lot of keyboard commands configured to the jet yet. I'll have to check when I get a chance.
Johan,
My initial thoughts are one of three things:
1. Controller confliction. Do you have more than one stick/yoke or other controller connected to that computer?
2. Incorrect FCS version. Are you getting the infamous "FCS FAIL" in your HUD? Make sure you do not have the 64-bit P3D FCS.dll installed. For FSX you should have the 32 Bit version.
3. As Pat indicated, check to make sure you have the latest C++ redistributable installed.
Hope this helps gents...
Jimi
-
[Johan,
My initial thoughts are one of three things:
1. Controller confliction. Do you have more than one stick/yoke or other controller connected to that computer?
2. Incorrect FCS version. Are you getting the infamous "FCS FAIL" in your HUD? Make sure you do not have the 64-bit P3D FCS.dll installed. For FSX you should have the 32 Bit version.
3. As Pat indicated, check to make sure you have the latest C++ redistributable installed.
Hope this helps gents...
Jimi
[/quote]
Thanks for your response
1- I have the Thrustmaster Warthog attached, no other controller.
2- The HornetFCS.dll is the 75KB one that I took from the Folder "FSX Specific Files". I don't have the "FCS FAIL" in my hud.
3- I will check on my C++ install
I noticed 2 "FCS" folders in the "FA-18C_FSXBA_BA_18.3.00" download. One is in "FA-18C_FSXBA_BA_18.3.00\Panel.Fleet" folder and the second one is in "FA-18C_FSXBA_BA_18.3.00\Panel.Fleet\Avionics" folder. They seem to have both the same content. Is this on purpose?
Thanks again for your help. Again, the plane works great on WIN10 but is "temperamental" on WIN7.
Johan
-
I noticed 2 "FCS" folders in the "FA-18C_FSXBA_BA_18.3.00" download. One is in "FA-18C_FSXBA_BA_18.3.00\Panel.Fleet" folder and the second one is in "FA-18C_FSXBA_BA_18.3.00\Panel.Fleet\Avionics" folder. They seem to have both the same content. Is this on purpose?
Looking at the Panel.cfg entries, the one that's used is the one in Panel.Fleet folder. The one in the Avionics folder isn't called at all that I can see. It may be a back-up, or a place to keep the .xml files that are being edited, before transferring them into the \Panel.Fleet\FCS folder. Or maybe the other way 'round. The ones being changed maybe are in the \Panel.Fleet\FCS folder, and the ones in the \Panel.Fleet\Avionics\FCS are an emergency back-up sort of thing.
I can take a look in my older version archives and see if the \Avionics\FCS folder is used in an older version, if you desire. I don't think it's a big deal though. Just ignore the one in the \Avionics\FCS folder. Forget it's even there ;)
I don't have the "FCS FAIL" in my hud.
Then you are using the correct HornetFCS.dll file. Takes THAT possibility off the table :)
I'll be installing TacPac later today, and I can start testing to see if I can figure out your trouble. I have the same controller as you do, Johan, so I'll be able to test and see what's going on.
Did you download and install the proper driver for that controller off their website?
And once again, do you have the correct FSUIPC file in use? You need v4.974, unless Mr. Dowson has invented a new one lately. NOT the ones he has created for P3D.
The C++ version you need is the 2005 one, X86. The 32 bit version, although I have both installed. The 32 bit and the 64 bit.
Are you running both FSX and TacPac as Administrator?
Good luck! Let us know how it goes :D
Pat☺
-
Thanks Pat, I will definitely let you know when I find out.
-
Johan,
Can you check in your FSX (Win7) settings, in the Controls/Axis tab and confirm that you do not have multiple things assigned to the X and Y axis?
With the Warthog, I'd imagine that you have separate entries for both stick and throttle. Use the pull down tab and select the flight stick and make sure that the aforementioned axis' are properly assigned. Then use the pull down tab and select the throttle, go back to the axis tab, and confirm that there are no assignments to the X and Y axis.
I'd do the same for flaps as well. Make sure the flaps are not assigned to any axis, but to switches, buttons or keys instead.
Hope this helps.
-Jimi
-
Johan,
Can you check in your FSX (Win7) settings, in the Controls/Axis tab and confirm that you do not have multiple things assigned to the X and Y axis?
With the Warthog, I'd imagine that you have separate entries for both stick and throttle. Use the pull down tab and select the flight stick and make sure that the aforementioned axis' are properly assigned. Then use the pull down tab and select the throttle, go back to the axis tab, and confirm that there are no assignments to the X and Y axis.
I'd do the same for flaps as well. Make sure the flaps are not assigned to any axis, but to switches, buttons or keys instead.
Hope this helps.
-Jimi
Hi Jimi,
Thanks for your response and yes, you make an excellent point. The TM Warthog is driven by FSUIPC coding, so I need to make sure in the FSX settings that the check box for the stick is unchecked. I might have inadvertently checked it back on with a Ctrl + K (joystick on/off). That would explain the erratic behavior of the plane. I am going back home next weekend and will let you know if this was the problem.
Thank you again,
Johan
-
The first i want to say thanks for your work. I love this plane is so beauty and i am enjoying fly it. I'm new here so i want to take advantage to say HI and great job!
I have a little problem, i cannot use ILS to land and right now i have to do it 100% visual. Most of the times in the UFCP i cannot swicht the ILS frequency to ON. Even if the display says ON, the ILS HUD bars doesn't work.
I am trying to land in USS Nimitz by Javier Fernandez. I think it works fine because Dino Cattaneo's T45 and F14 can catch the carrier ILS.
To see if it's my problem i tried to land in my local airport but i have same problem.
I give you a couple of screenshots if you want to check everything is right.
https://cdn.discordapp.com/attachments/453512420267261952/480854294963290122/unknown.png
https://cdn.discordapp.com/attachments/453512420267261952/479291906036203533/unknown.png
For the record: I press ILS UFPC button -> then i press 112000 and ENTER button. IILS in right DDI is enabled. Also in the shift+2 HUD panel instrument the ILS and CAGE are ON.
Am i forgetting anything???
Thanks in advance and excuse my basic english. I hope is understable.
Edit: P3Dv4 (4.2) and FSXBA 18.3 for P3D
-
Helice,
Firstly, welcome to the forums here, and secondly, thanks for the good words, I'll be sure to pass them along.
As for the ILS, it's not you, it's me lol. It's a know issue that currently being worked on. Should have a update coming out soon that will fix it in about a week or two.
-
Thanks for the welcome :D
Nice to know everythink is OK. I feel less idiot now XD
No problem for the fix, take the time you need. While i wait the update i can enjoy fly the plane anyway because the F18 is lovely. For me is an big icon of modern aviation. My little project is land on carrier at night with closed storm. I loved years ago that missison in FSX Acceleration and i would like to reproduce it.
Thanks again for such a good bird.
... it's not you, it's me lol...
Dang i hate this phrase. It remembers me a girlfriend ending a relationship XD
-
Does installing the current version still require the FA_18_dll or is it included in the package?
-
Which sim?
P3Dv3, yes. P3Dv4 and higher, no.
Remember, the Hornet for FSX, and P3Dv3, are the same, and the P3Dv4 bird is a separate plane.
Does that help?
Pat☺
-
Edit:
For some reason in P3D 4.2 i only need copy FSXBA\P3D Specific Files\Gauges\HornetFCS.dll to \Prepar3D v4\gauges\ to avoid the "FCS FAIL". (109KB size)
But in P3D 4.3 i overwrite also the FSXBA\panel.fleet\HornetFCS.dll (75KB) with the 109KB version.
If i don't replace the panel.fleet one i cannot fix the FCS FAIL.
Am i doing right?
-
Well, if it gets rid of the FCS FAIL mesage, it must be the right thing to do :D
I was under the impression that the P3D sims only needed it to be in the ...P3D\Gauges folder. I have the funny feeling it was the mere presence of the 76kb version in the Panel.Fleet folder that was making things messed up, but heck, I might be wrong on that.
As an experiment, you can try moving both the 76kb AND the 109kb versions out of the Panel.Fleet folder. Just make yourself some folder under the main plane's folder, like ...\BAX, or whatever you want to call it, and cut-n-paste ANY .dll file in the Panel.fleet folder to that. Not copy-n-paste, but cut-n-paste. In other words, remove any HornetFCS.dll file at all from the Panel.Fleet folder, and place it, gently, of course ( ;D ), into your just created folder so you can find it (them) again quickly and easily. Then see if you get the FCS FAIL message.
If you do, just put the 109kb file back into the panel.fleet folder, and enjoy the plane :D
If you don't get the FAIL message, well, you know that the HornetFCS.dll (109kb) only needs to be in the \P3D\Gauges folder to function properly.
Remember to either have the sim totally shut down while you're moving files around. Is it NECESSARY? Probably not. You could probably get away with just being in the Free Flight menu area while doing it, but I think it might be safer to have the sim closed completely.
I would try this for you if I could, but I don't have P3D. Sorry about that.
If you would, please let us, or me, anyway, know how this all falls out. That we, or at least I, can pass this on to someone else who has the same, or a similar, problem. Thanks!
Good luck!
Pat☺
-
Hey Pat! Test done and works fine with no FCS FAIL.
Right now there is not HornetFCS.dll in FSXBA\panel.fleet (neither 79kb nor 109kb)
My guess is the priority of load dll's folder has changed from 4.2 to 4.3. Maybe in 4.2 loads first the main gauges folder and this is why works fine.
Looks like P3D_4.3 loads first the plane\panel.fleet folder and the 79KB is not the right one (which is there when you download the plane).
I hope this helps.
(oc we are talking about the download of the FSXBA 18.3 for P3D)
-
Thanks for the update, H!
I appreciate the info. Now, if it comes up for others, or on other forums, maybe I can help them a little.
I AM glad you got it working.
Who knows what Lockheed is doing to the poor sim. I'll not comment further on Lockheed. I used to work for them, so I know how they work. It wouldn't surprise me to know they changed the gauge search/load order. They did it once, why not again?
ANYWAY...
Now, I insist you go up flying in the v18.3 and enjoy it. This is a requirement for using the airplane ;D
And don't forget AICarriers, vLSO, and so on. They only add on to the greatness that this plane is, and is becoming as they go.
If you have TacPack, by the way, it works well in the Hornet v18.3, but will work so much better in the next update, which is coming soon. I just got TP, and I'm really enjoying it. I just shot down an AI Dash 8 over MCAS Yuma. Not a fair fight, but it was a blast, gunning his tail off.
Have fun, and thanks again for the testing. It will help others ;)
Pat☺
-
Hello Gents,
I know it's been a little while since we've put out an update on the Hornet so I'll quickly fill you in on what we've been up to:
1. RADIOS: Lot's of work on revamping both the COM and NAV radios that they have better functionality. The new radios allow both VORTAC Freqs as well as TACAN channels to be entered and tuned. ILS needles and CRS arrows have been fixed as well. This includes both land and carrier ops.
2. AUTOPILOT: Autopilot functionality has been fixed.
3. TACPACK Ordnance Fire Control: Has been redone and adjusted. (TACPACK ONLY)
4. DDI Menu Layout: The new DDI Menus have both TAC and SUPT menu pages to more accurately reflect that of the F/A-18C Hornet
(https://i.imgur.com/T2yrYL0.png)
5. RWR: New RADAR Warning Receiver (RWR) has been implemented below the right DDI to warn of incoming threats (FSX TACPACK ONLY)
6. EW: New Electronic Warfare (EW) Page which shows same info as RWR but on DDI along with Chaff/Flare status and option to arm Jammer (FSX TACPACK ONLY)
(https://i.imgur.com/zaFyRdG.png)
7. FLIR: New basic Forward Looking Infrared (FLIR) capability added to the jet that is synced with the RADAR (TACPACK ONLY)
(https://i.imgur.com/7oKQJoy.png)
8. HMD: New, very basic Helmet Mounted Display (HMD) added to the jet. Just shows basic HUD info currently (FSX TACPACK ONLY)
(https://i.imgur.com/td9Bgt7.png)
9. FUEL SYSTEM: New fuel system actually takes into account whether or not external stores are hung onto the jet and adds fuel accordingly
10. RADAR: New TMAP Radar installed on the aircraft that brings better capability for TACPACK operations (TACPACK ONLY)
(https://i.imgur.com/dgVtyE1.png)
11. FCS RESET BUTTON: Resets the FCS PIDs if the FCS starts to go crazy.
12. TEXTURES: Updated cockpit textures.
Well those are the biggies. Bunch of other smaller fixes and adds. More details on each will be put out once the update is actually released. Big thanks goes to Corrado, PhantomTweak, and Kea for all the updates, textures help and testing!
Hoping to get this wrapped up and pushed out either just before or sometime in September.
-Jimi
-
KREYGASM These are very good news @jimi08. Cannot wait the update to try ILS on USS Nimitz.
@PhantomTweak : YOur welcome. A pleasure help a bit. The Tacpack sounds good but i don't own it. For the price maybe i preffer a plane in DCS. Not sure.
-
While waiting for this future update, I managed to modify the HUD to obtain the correct display of the ILS:
attached image.
Jean
-
New version out on page 1 of this thread.
-
Hello Jimi08
Should the file "panel.cfg" in the "Panel.fleet" folder be replaced with the one contained in "P3D specific files"?
Jean
-
Not if you used the autoinstaller.
-
OK, thank you jimi08 :)
-
Anytime
-
Thank you very much for this new update.
1) Can you have a look on F18_AoA_Indexer.xml lines 24, 34, 44 and 54?
Error: Missing gauge image file: Avionics\BlackBox\AoA_background.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_onspeed.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_fast.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_slow.bmp
2) In the aircraft.cfg file, all lines before the [General] section must begin with //
Regards and good continuation.
-
Thank you very much for this new update.
1) Can you have a look on F18_AoA_Indexer.xml lines 24, 34, 44 and 54?
Error: Missing gauge image file: Avionics\BlackBox\AoA_background.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_onspeed.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_fast.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_slow.bmp
2) In the aircraft.cfg file, all lines before the [General] section must begin with //
Regards and good continuation.
Currently out of town at the moment. Will take a look once I get back to home. Thanks for the feedback.
-
OK Jimi
Have also a look on the panel.cfg line 59
gauge02=Avionics\BlackBox!F18_UFCD, 0, 400, 180, 210
and line 60
gauge03=Avionics\BlackBox!F18_FMC, 0, 0, 0, 0
because these two xml files (F18_UFCD and F18_FMC) are missing in Avionics\BlackBox
error=Gauge file not found: Avionics\BlackBox!F18_UFCD
error=Gauge file not found: Avionics\BlackBox!F18_FMC
And the last :
This effect is called and is missing
error=Failed to load visual effect "kd_FX_seatRocket"
Regards
-
No worries. I'll probably just delete all of those since they are no longer being used.
-
1) Can you have a look on F18_AoA_Indexer.xml lines 24, 34, 44 and 54?
Error: Missing gauge image file: Avionics\BlackBox\AoA_background.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_onspeed.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_fast.bmp
Error: Missing gauge image file: Avionics\BlackBox\AOA_slow.bmp
2) In the aircraft.cfg file, all lines before the [General] section must begin with //
As to #1: Yes, they're missing, but my AOA gauge works fine. A little off compared to the pitch the plane takes for level flight with the gear and flaps down (PA Mode), but I have the funny feeling that was the fault of my stick on this test pass. I'll check it again tomorrow when I fly. This is in FSX:SE, not P3D, but I thought I'd check on it anyway, if that helps at all.
#2: They seem to be fine in mine. No, each and every line doesn't have the "comments" marks (//) but the aircraft.cfg seems to ignore all the lines with the main headings commented out. IE: like this
// HUD/Avionics/Gauges:
Jivko Rusev
Scott Printz
Dino Cattaneo
Orion Lyau
Justin "Jimi" Hendrix
Corrado La Posta
D Dawson
All the names entries are ignored. Maybe FSX is less touchy about this sort of thing?
Hope this is some small help...
Pat☺
-
Hello,
I confirm what micpni writes, In the aircraft.cfg file, all lines before the [General] section must begin with //
otherwise, P3D reports them as an error.
Also, to keep only the errors affecting the FA-18, I delete all these lines in the aircraft.cfg, which is faster than adding // to each line concerned.
2 other questions:
1 / Is it possible to simultaneously display the Tacan AND ILS informations on the HUD.
It seems to be Tacan or ILS depending on whether we click on the HSI Tacan or ILS buttons, but not both.
2 / How to activate the glide / slope in the HSI and modify the HSEL and CSEL parameters?
Regards
Jean
-
Copy all on deleting the files.
As for tcn and I'll info display, yes there are currently set up to display one or the other. I will need to re-reference the NATOPS to see how they are both displayed.
Needle adjustment is done in the HUD coding, found in Panel.xxx/Avionics/HUD
-
Thank you jimi08.
Regarding the adjustment of the needle on the HSI, it can be done through "Vehicle / Instrument Panel / Flir"
About these instrument panels, the call of the test, radar and HUD panels displays black windows. (P3D v4.3)
Regards
Jean
-
Hi Guys,
I'm a bit disappointed with the new release. It seems to be "one step forward and two steps back"! The absence of detailed instructions - or the carry over of old instructions, does not help. For example; I cannot find a means of entering either the ILS or Tacan for RAAF Base Williamtown (YWLM) - the RAAF's primary Hornet base. The trims have reverted to some months back when right aileron trim rolled the aircraft left, etc. Reading the list of improvements that have been included leads me to think that a disproportionate amount of effort has been put into its weapons capability. Might it not be prudent to get the aircraft and its primary flight systems working before plunging too far into TacPack?
While it is still very nice to fly, there is little incentive to spend simulator time on it when other similar aircraft (e.g. Dino's F-14) can do all the basic sim stuff properly.
Sorry, Roger
-
Hi lowery
I managed to enter the TACAN and ILS frequencies.
I made a short video explaining the procedure. I send you the video by email.
Then I did the same thing to enter the Nice LFMN ILS and the result in 3 screenshots.
Regards
Jean
-
In addition to my previous post, I placed the F18 at YWLM and did several tests with the TCN 80X and ILS 110.50 frequencies of this base.
To have the correct ILS on both the HSI and the HUD, you must enter the frequency 110.50 in both radios.
But then, the choice of the TCN with the HSI button points to the IWM tacan and not WLM.
If we enter the correct frequencies 80X and 110.50, then the HSI ILS needle no longer indicates the deviations.
Moreover, there is no directional needle for Tacan in the HUD.
-
Greetings,
Thank you for the new update. I'm using P3dv4.3 and I am having a problem with rudder and elevator flutter. Anyone else having this issue?
Appreciate you getting the course selection arrow to work as well, but the course selection toggle switch on the lower left panel shows "Oil Temperature" instead of "Course" when you move over it with the cursor.
Cheers,
Reggie
-
Ok, first time posting, I think I find out a way to display the TACAN Neddle, alone or with the ILS LOC/GS, in the HSI page CSEL need to be HIGHLIGHTED, will be the bottom between DATA and SCL on the top part.
Now I have a problem, the radar is not working for me I don't get any targets and the ground mapping is not working like it did in the prior version, I did check without the selectors just using the soft keys, and using the selectors above the master arm, also I try the Master Arm, safe and armed and noting happened. In the SA page I got the TCAS to work. I am using the FSX boxed version.
any help will be great, thanks
-
In addition to my previous post, I placed the F18 at YWLM and did several tests with the TCN 80X and ILS 110.50 frequencies of this base.
I went to YWLM, and unless you have an add-on scenery I don't, there's no TCN station at this airport. There's a DME, but it's not a TCN transmitter. There's an ILS, 110.50 as indicated, which works fine.
As to the rest, I went to MCAS Yuma for testing. It has a low-level TCN freq., 84X. I picked it up at 60 nmi. The arrow on the HUD I believe you're talking about is matched in azimuth to the CSEL line on the HSI, NOT the direction of the TCN station. That's indicated by a hash mark up on the compass rose on the top of the HUD. And it indicated correctly, with TCN boxed on the HSI, allowing me to get lined up for a nice straight-in from about 45 nmi out. I lined up the TCN indicator, on the compass rose top of the HUD, with the runway direction (211°), and used the CSEL arrow on the HUD to line me up exactly, left and right, with the runway.
I included some pictures for easy reference.
In the first picture, you can see, on the HSI, I am flying towords the line-up I want, with the statin 24 miles away. I am traveling about 80° relative to the runway, so I am flying towords the the airport, slightly, but mostly across the heading the airport will show up ahead of me.
In the second picture, taken further away from the airport, but using it for illustration, you can see what I described in picture one, but on the HUD. As you can see, the HUD and HSI indications match up. You can see the TCN directional hash mark on the HUD's compass rose, just off 270°. It matches the TCN's directional indication on the HSI: A large triangle on the outside of the HSI Compass rose.
In the third, I have come close to line-up, and am turning directly towords the TCN station. On the HSI, TCN is still boxed, and the large Triangle, indicating the direction to the TCN station chosen, is nearly lined up to the CSEL arrow, indicating runway heading. The smaller triangle on the inside of the HSI's compass rose is the "flight plan" directional indicator, that I plugged into the GPS real quick. On the HUD, you can see the hash mark over on the left of the compass rose, matching the HSI indications, You can also see the course (CSEL) arrow, also matching the HSI, approaching the line-up I've chosen.
In the fourth, getting to final line up on the runway, with ILS for Yuma, 108.30, now boxed on the HSI, and indicating the ILS needles on the HUD. Notice the TCN arrow is off the one side slightly, as the TCN transmitter is not directly ON the runway. But it's still there, and indicating the direction I've dialed into the CSEL line, the runway heading. If you look, you can see the hash mark on the HUD's compass rose, also off center. As it should be, given the location of the transmitter and my proximity to the airport.
In other words, the TCN, ILS, HUD indications, and all the rest appear to be functioning normally. At least at MCAS Yuma, AZ. I'll take a low-pass over my house I lived in for almost 30 years another time ;D
To answer Rivas, I locked on, and shot down, an AI aircraft on my way over to Yuma. A CRJ-700. It showed up on the radar display fine, scan 90°, 4bar scan pattern, starting at 40 mi range, and selecting shorter ranges as I approached the target, and locked up just as it should, with the proper lock indications. I pumped some gun rounds into it, then did a 360 to gain separation, and fired a AIM-9X to finish it. In any event, it showed up on the radar correctly, as well as on the SA screen on the center DDI. The HUD indications all showed up as they should. I also placed a SAM site on the desert, on the way into Yuma, and it showed up as it should on the AG radar display. I'll double check the AG radar SEA functions tomorrow. I tested them yesterday, and they worked fine.
To Jimi: Would it be possible to add the AGM-88C HARM missile to the armament? It's listed as being carried by the F/A-18C, and would keep me from getting nailed by SAMs I've place near as often! :D :D
I've been looking into this, and have modified the tacpack.ini to include it. Everything I added is commented out, but it's there! ;) Working on the rest, but this is all new. Steep learning curve :D...
ALL the above tests performed on FSX:SE, with TacPack running.
Good luck, all!
Pat
-
Thank you all for your help. However, I'm still confused. RAAF Base Williamtowm (YWLM) has ILS 110.50 (IWM), NDB/DME/TAC 365/113.30/80X (WLM). I suspect my scenery of the area in P3Dv4.3 is ORBX. I'm 78 and obviously retired but, having been a RAAF fighter pilot and combat instructor, I flew the Hornet back in the early 90s and don't recall having all this trouble just to get the right frequencies inserted and the navaids to display!
Reference my comment on trims: Today, after starting up P3Dv4 and loading the Hornet the trims are all working in the correct sense now but I'm getting the dreaded FCS FAIL warning (I know how to fix that).
So, I'm not certain what's causing these differing, apparently random problems, P3Dv4 may have some input, left over files from previous F/A-18 versions probably contribute as do yet to be finalised issues and the absence of up to date instructions.
I take my hat off to all you guys who put so much effort into this great FltSim aircraft - I feel that your job now is much more difficult than my old job of just having to fly her!
Please keep up the good work which I follow with great interest.
Cheers, Roger
-
Roger,
Copy all and thanks for the feedback. I'll take a look once I get back home.
Pat,
As usual, appreciate the help.
-
I went to MCAS Yuma for testing. It has a low-level TCN freq., 84X.
I tried to redo your demonstration on YUMA.
I entered the 84X frequencies in the TCN and 108.300 in the ILS.
The HSI does not show the same as your picture # 1 while I am about 25 Nm from NYL. No indication under DATA or left of GPS.
Is it due to P3D v4? Or did I make a mistake?
Regards
Jean
-
I suspect my scenery of the area in P3Dv4.3 is ORBX.
Either one of those may be the difference. I am sorry, but I can't check things out in P3D. I just can't afford to buy it. Same for ORBX.
Did you get the Radio/NAV off the sim's map feature, or did you drag it out of your memory? In the first case, I'd be willing to wager that it's ORBX causing the difference. Maybe the P3D database. Remember that FSX is older than P3D, so there may well be differences in the database of airports and their information.
In the second case, and thank you very much for your service, sir, I would double check on the map included in P3D. Make sure their information is the same as in your cranial vault's database :D
I am not trying to be insulting. I have trouble remembering my friggen name from day to day. Glad I have a driver's license so I can verify it... ???
So, I'm not certain what's causing these differing, apparently random problems, P3Dv4 may have some input, left over files from previous F/A-18 versions probably contribute as do yet to be finalised issues and the absence of up to date instructions.
You might try searching the entire sim for previous versions of the HornetFCS.dll file. A safe thing to do, and I've had to do this in mine a couple times, is go on a search-n-destroy for any HornetFCS.DLL file you can find in P3D, other than the one in the latest installed version of the Hornet. Including the one currently residing in your ...\P3D\Gauges folder. Then copy the HornetFCS.DLL file from the folder P3D Specific Files, if it's still there in the P3D version, to the sim's \Gauges folder. In any event, I am certain there's a copy of the latest HornetFCS.dll file in the latest install. Copy it to your sim's Gauges folder, and see what works better/worse/not at all.
Alternatively, delete every HornetFCS.dll you can find anywhere in the sim, delete the plane, and re-run the installer and see what shows up now. That way, you pretty much get a clean install, no previous .dll's causing problems.
By the bye, did you allow your installer to install the .NET Framework properly, and completely? Even if you already have it installed, let it run again. Removes any possible corrupted files, and installs the latest, or at least the most correct, one. Just to be safe kind of thing.
Is it due to P3D v4? Or did I make a mistake?
Jean, it might well be that P3D doesn't use the same information in it's airport information database as FSX. Check the sim's map feature and see what it says about MCAS Yuma. It should show any TCN/VOR information. I'm sure Yuma has, at the very least, a VOR and ILS, by default.
At the very least, use the BARD VORTAC. It's just a hair NW of MCAS Yuma, just inside the California border. Yuma's weird. Go north to hit Cali, west for Mexico. Weird place. Miserable, too.
If not, check other bases, until you find one that meets our requirements. Edwards AFB in California, North Island NAS, Vandenburg AFB, Moffet Field, Whidbey Island NAS, Pensacola, Oceana NAS, SOMEplace, I am sure, has what we need to verify what's going on. Use the sim's map to see what each has. If using the TCN number, like 84X in the UFC's input doesn't give the desired result, try punching in the actual frequency , like 110.50 or whatever, instead. Not the ILS freq, the VOR or TACAN frequency.
By the way, in your first picture, you don't have TCN boxed on the HSI. Try it, and see if it gives any different indications. Maybe not at Yuma, but someplace must have a TCN station at it. And it's pretty much restricted to military bases, so just check those. Civilian airports probably, probably I say, have VOR's, but not TCN. The plane will treat them the same, though. If you need, just plug a VOR's freq into the UFC, and treat it as a TCN station, as a last resort. The plane should, SHOULD treat them the same.
I'm sorry I can't be of more help, but without P3D, I obviously have to go with what I have available to me. I wish I could be of more help to you guys.
Jimi, I'm glad to be what help I can :)
Obviously, not a lot without P3Dv4, but I do what I can. Somebody has to test things in FSX after all :D
Have fun, all! I know it can be frustrating, but it's well worth it once it's going as i should, believe me!
Pat☺
PS: Jean, here's a scenery add-on for MCAS Yuma: https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=181855 (https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=181855).
Maybe it has a TCN station? It is specifically for P3D. I don't know if V4 is going to be a problem for it, though. Just a thought...
-
OK All,
Back home from Marrakesh, Morocco! Highly recommend the place if you have the change to go.
First, thanks for all the feedback! All has been constructive. I'll dig into what I can in the next few days and push an update if I can before heading out to the next trip.
As warned on page #1, there has been both a lot of new work and a lot of rework on this new release. That being said, I did expect a higher than average amount of bugs on this one. Never the less, we'll continue to hammer on and will eventually will get them knocked out.
A few things to note:
1. NAV RADIOS: The day before the release, I did a short X-country from KNPA to KMSY via VOR to VOR. During that flight I tuned up the needed NAVAID using both their VOR/VORTAC Frequencies as well as using the listed/converted TACAN Freq. I ran into no issues. I then proceeded to do an ILS once at New Orleans International with no issues.
A couple of quick notes about the NAV RADIOs and Displays:
*** Unlike the previous version of the radios, the radios for this jet MUST BE TURNED ON FIRST before it will dial and tune in the selected freq. You can turn the radio on and off by using the ON/OFF button, located on the right side of the UFC. The letters "ON" will be displayed indicating that the radio is on. This needs to be done for both the TCN radio (NAV Radio 1) and ILS radio (NAV Radio 2).
*** Only the ILS radio can be used to tune in ILS frequencies. The ILS needles are tied to NAV Radio 2 and only 2. The needles will not reflected AZ/GL info from freqs tuned in on TCN Radio (NAV Radio 1).
*** Use the TCN, WPT, ILS, and CSEL soft buttons on the HSI display to display the nav information you want. If you want to display TACAN/VOR info, select the TCN option. If you want GPS info displayed, select the WPT option. Same goes for the ILS option and the needle displays for the HUD.
2. TACPACK WEAPONRY: Have received some feedback in regards to weapon functionality in the new version. A few things to note here as well:
*** This version is the first in which the user has the option to cycle through which air-to-air target he/she would like to fire upon. All previous version consisted of "Boresight", in which the radar would just lock onto whatever was directly in front of the jet at the time of weapon configuration/activation. Although the new version gives the user a little more flexibility, it still new (for me anyways lol) and with that, bugs will be discovered and ironed out. What I'll probably do for now is release a "hybrid" version for the next release. This will revert air-to-air functionality back to boresight mode for ACM while keeping the new features for the air-to-ground stuff.
*** I've also had requests to add new/additional weapons to the jet such as the HARM as well as dumb bombs such as cluster bombs. While these are great requests, the immediate answer to this question is "we'll see". Adding new weapons require changes to the 3D model, which takes cooperation, coordination and time from busy volunteers. Add to that all the work/rework that has to be done for avionics/systems integration. PLUS with all of the other things on the fix list/hornet-do-list (...and it's a long list...) adding the new weapons falls pretty far down on the project tasker. We might get to them in the future, but don't expect them in the NEAR future.
3. TRIM: Thought I had the aileron trim issue fixed. Didn't realize it reared its ugly head again. Good catch and I'll fix that soonest.
That's about it for now. I know with this new version, things can be frustrating with some of the bugs. I ask for a little patience. We'll get things right (eventually lol). Just give us a little time.....and patience.
P.S. For whatever reason, you want to revert back to any of the previous versions of the late 17 series and 18 series jets, the links to them are all posted on the 1st page of this tread.
Jimi
-
;D The plot thickens! After turning on my computer and P3Dv4 this morning I selected a previously saved F-18 flight (previously saved as in 'before this new release'). The aircraft appeared WITHOUT the FCS Fail, FCS Hot, etc; but with the reversed aileron trims! and, for love or money, I cannot get a frequency to activate a navaid. The freq. appears, but no result.
When I set up a flight from basic selections, I now get the same result.
The YWLM freqs that I quoted are from AIP Australia and are correctly entered into Navigraph and ORBEX. They work in all other aircraft I use at that location.
Boy! am I glad I was just a fighter pilot and not into IT!
Cheers, Roger
-
Be carefull with a previous saved flight.
In the previous flight files, some particular technical situations of the aircraft are saved.
If the plane is not the same after an update, so P3Dv4 may not start.
It is the same with a scenery. Don't save a situation with a specific scenery before an update in this scenery.
So, it is always better to begin a flight with a basic aircraft in a basic scenery.
-
New test today.
When I started P3D, I used the airplane and the default scene.
After that, I went on Cambrai-Epinoy ('LFQI) which has an ILS 109,300 and a VOR / DME 112,600.
By doing so, I have all the functions active and correct in the HUD and the HSI.
Thanks micpni for reminding me, for the hundredth time at least, the right way to launch the simulator.
Also, thanks to Pat for the scène of MCAS Yuma.
Regards
Jean
-
When I started P3D, I used the airplane and the default scene.
I forgot about that little detail, sorry bout that. It's a habit with me. Default flight, default location, default plane. THEN I change it out :D
By doing so, I have all the functions active and correct in the HUD and the HSI.
I see that from the pictures! Great news. I'm glad you got it worked out 8)
Also, thanks to Pat for the scène of MCAS Yuma.
Glad I could help. Wish I had been of more assistance. Not always easy to get things trouble-shot across platforms sometimes.
Have fun!
Pat☺
-
Hello, Jimi! I love this jet! I don't even use my Superbug anymore! My only issue is I can't get the FLIR to work. Followed the description as you outlined on page 1: Loaded the pod in tacpack, I get the air to air and ground radar ok in the right DDI, but when I turn the FLIR on (lower right side), it goes black. P3D V4, using your latest version with the auto installer. Any files I have to move as in the 18.3 version?
Thanks in advance!
Mike
-
Hello, Jimi! I love this jet! I don't even use my Superbug anymore! My only issue is I can't get the FLIR to work. Followed the description as you outlined on page 1: Loaded the pod in tacpack, I get the air to air and ground radar ok in the right DDI, but when I turn the FLIR on (lower right side), it goes black. P3D V4, using your latest version with the auto installer. Any files I have to move as in the 18.3 version?
Hey Mike, thanks for the good words, I'll be sure to pass them along. As for you issue with FLIR, please go to TACPACK Manager (TPM) and ensure that you have "D3D Experimental Features" checked. If not, check it, save TPM and restart FSX. If you've download the correct version for your rig and ran the auto-installer, you shouldn't have to shift any files.
Let me know if this works. Thanks.
Jimi
-
Hi, Jimi. Wow, thanks. I never thought of that. Hope it works. Trying it now, let you know soon!
Thanks!
Mike.
-
That is checked in the Tackpack manager, but it seems to be for FSX not P3DV4. It mentions DX10, DX9? Maybe uncheck it?
Thanks, Jimi.
Mike
-
Hi, Jimi. No luck, Experimental Features checked or unchecked. Am I the only one? If so, I must have some setting wrong.
Thanks,
Mike
-
Just to be certain, which version of TP are you using? They published a new, updated, version fairly recently...v1.5.0.4
When you unistalled and re-installed TP, did you make certain it was ALL gone? The folder in P3D, the TPM folder on your hard drive...all of it?
Are you certain you DL'd the correct version of the Hornet, AND the correct TP version? The ones for P3D v4?
When you uninstalled and re-installed TacPack, did you uninstall the Superbug too? And re-install it if you choose, of course. But you have to install and activate TP first, and only then install the Superbug.
I'm just trying to think of possibilities here. I don't know whether any of them will be of any use for you, though.
Hope you get it going!
Pat☺
-
Hey Mike,
MY APOLOGIES. Just went back over our dialogue to see what I missed. Currently, I don't have FLIR working for P3Dv4 yet. Only FSX as of now. Hoping to have FLIR for P3Dv4 up and running soon though.
Jimi
-
Thanks Pat and Jimi. Now I can stop letting it bug me, and wait for the next update! Great work, I'm actually surprised that it's not payware!
Thanks again!
Mike
-
Much appreciated Mike. Hopefully we'll have the P3D one out soonest.
-
Hi jimi,
Continuing my learning of the F-18, I test the functions of the Air / Air radar.
(I do not have the TackPack).
Are there videos explaining the operation that looks different from the outdated radar of the F-18 FSX?
I do not quite understand the indications in the HUD:
In the first screenshot, I selected a target airplane using the TUP and TDN keys. The radar spot become red.
In the HUD, the selection square does not follow the target.
The second screenshot shows a second square positioned lower than the 1st and a circle that appears to be the collimator of fire.
The third screenshot shows the position where we are allowed to shoot.
To achieve this, I have to stack the two squares in the circle. But I am too low compared to the target and the shot goes under it.
If I try to go up the circle / squares set, the SHOOT indication disappears.
The documentation is wordless, and that of the original F-18 FSX no longer corresponds to this new version.
Thanks in advance.
Jean
New issue :
A crash to desk with screenshot 4 notification. A file not found (or an error in a .xml ?)
-
Right off the bat, and once again, I don't have P3D, but looking at the HUD and two DDI's it looks to me like you locked onto the target past the one that's closest to you. That's why, when you shoot, it LOOKS like the rounds are going under your tgt. They're aimed at the next target, not the closest one to you. Again, this is ALL "it appears to me as though"...
I know it's very difficult to duplicate a situation like this, so you may not be able to re-try this particular scenario.
Try this, if the same situation arises again: When you lock up a tgt, switch the radar to ST mode, upper left corner. Click the soft button twice from RW mode to get ST mode. That way, the radar will only display one target. Only the one you have locked up. Also, lower the radar's range to 5 mi, to get more detail of the close-up targets, so you can be certain you're locked to the target you actually want. You should also only get one TD box on the HUD in ST mode, and all the ranging information, the circle showing range and Vc and so on will be on the one target you want.
Hope this is some help...
Pat☺
-
Hi Pat,
In ST mode, the radar always displays multiple targets, and the choice using the TUP and TDN keys is not retained. The locked target returns to the nearest one.
When the target is near and the range of the radar is set to 5, the target remains locked.
In the HUD, the TD box is not locked to the chosen target. When approaching the target, the circle appears, accompanied by a second TD box locked UNDER the target and, when this second TD box is brought into the circle, the authorization to shoot is displayed in the HUD.
I will take the old version of the F / A-18 to compare.
Jean
-
Looks like a HUD symbology alignment issue. I'll have it fixed in the next release. Thanks.
Jimi
-
OK Jimi,
Another issue when I extend the probe (see screeshot)
And the supply is erratic.
The percentage and amount of fuel vary more, then less and again more.
I do not know if it's related to this problem, but P3D finds an error in the gauge:
error = Gauge / Script Error
Type: Gauge
Name: RefuelingGauge
Error: Invalid script: "@Vehicle_AirSpeed (> L: Vehicle AirSpeed, kts) (A: PLANE LONGITUDE, radians) / - / (C: ITrafficInfo: S: PLANE LONGITUDE, radians) / - / - sin (C: ITrafficInfo: S: PLANE LATITUDE, radians) cos *
I am preparing a short video that I will send you by mail.
Jean
-
Jean,
Good catch on the HUD. Not sure why it would be duplicated. Can you remind me of your setup? FSX? TACPACK?
Either way, I'll add it to my fix list and take a look at it once I return home next week.
As for the fueling amount, I suspect that it is affected by the new fuel gauge that now takes into account external stores. So you will not getting 100% unless you have all three external tanks loaded and filled.
-
Hi Jimi,
My configuration is P3D v4.3 without tackpack.
I am not trying to get 100% fuel, but I point out that the percentage and the total fuel fluctuates during refueling. The percentage varies from 92 to 62% and / or the total fuel passes from 13410 to 10650 before going up.
Jean
-
I recently downloaded the latest edition of the Hornet 18.4, and every time I take off, the frame rates drop to where it is uncontrollable due to the lag of 7fps. Everything else on the aircraft works great, it just will not run smoothly after take off. Can anyone help me with this issue?
Thanks,
Crash
-
I recently downloaded the latest edition of the Hornet 18.4, and every time I take off, the frame rates drop to where it is uncontrollable due to the lag of 7fps. Everything else on the aircraft works great, it just will not run smoothly after take off. Can anyone help me with this issue?
Thanks,
Crash
Can you give me your setup please?
-
Setup is FSX:Acceleration boxed edition.
Computer has:
2gb vram
3.5ghz processor
8gb ram
-
Setup is FSX:Acceleration boxed edition.
Computer has:
2gb vram
3.5ghz processor
8gb ram
TACPACK?
-
Hi guys
I’m back......hips healed after 6 months therapy I’m walking again and flying again.
What is latest version for fsx? Never mind I found it.....
-
Page 1 of this thread. The DL's have a designation for FSX/P3Dv3, and one for P3Dv4 (64 bit version).
Great plane, at least in FSX:SE :D
Enjoy it!
Pat☺
-
Setup is FSX:Acceleration boxed edition.
Computer has:
2gb vram
3.5ghz processor
8gb ram
TACPACK?
No Tackpack, is it a requirement?
-
Only to be able to use certain features.
Pat☺
-
This is a minor thing regarding livery, not a bug report.
The Canadian Air Force is slowly doing minor livery changes to their 18s.
They're removing the 'Canadian Forces' and flag from behind the wings, and adding RCAF - ARC beside the roundel under the cockpit, like how it is on the 150 Display team livery you have already, only in low viability colours.
https://i.imgur.com/vzBZ3vi.png
I have no idea if you're planning on touching up any existing liveries, but I thought I should bring it up anyways.
-
Hey Tuskin,
Welcome to the forums. The guys over at Groom Lake Simulations do most of our textures. I'd recommend sending your request over there.
Link: https://www.facebook.com/GroomLakeSimulations/?fb_dtsg_ag=AdySpQJZjZr__YUdhMo-jB9xZJuZ-OmVRUknpWG38FZn-g%3AAdzVt0A396duGcG-R8OczmJyhOPAYRAukYsPQbtSMk3whQ
-
No Tackpack, is it a requirement?
No not a requirement to fly but it is to fight. Plus there are a number of scripts that run based on whether or not TACPACK is active or not. Just helps me to narrow down where problems might lie.
Thanks.
-
Please disregard my earlier e-mail regarding the rudder and elevator flutter. I seem to be having issues with myX-56.
Regards,
Reggie
-
Roger that, also there is a thread about the HUD refresh rate that seemed to be pretty accurate to my issue, but I tried what the instructions said, but I the GDI button is not there.
- Go to the Top page, by pressing "MENU" from any page
- Select "BIT" (Built-in-Test, it's a key on the top)
- Select "GDI+ (on the low-right) Does not exist on my version.
-
Roger that, also there is a thread about the HUD refresh rate that seemed to be pretty accurate to my issue, but I tried what the instructions said, but I the GDI button is not there.
- Go to the Top page, by pressing "MENU" from any page
- Select "BIT" (Built-in-Test, it's a key on the top)
- Select "GDI+ (on the low-right) Does not exist on my version.
That's for the F/A-18A Hornet that comes default with FSX Acceleration and FSX Steam Edition. Does not apply to the FSXBA F/A-18C Hornet
-
Well, I thought I had fixed the flutter problem but apparently not. If has to do with version 18.4. When I revert back to version 18.3, I don't have the flutter. I wish I could send you a video of the problem. Any advice appreciated.
Thank you,
Reggie
-
Can you provide the conditions of when you observe the flutter?
-
Hi jimi,
Another issue, when, in flight, I clic on the hook toggle:
Regards
Jean
-
Greetings Mr. Hendrix,
The conditions occur anytime I fly this version of the aircraft. My setup is as follows:
AMD 4100FX 3.4 Mhz
8Gb RAM
GTX 1050Ti 4Gb
P3Dv4.3
Active Sky for P3dv4
Orbx Global, Vector, Open LC North America, HD Trees, Lights
Things I have tried:
Flying with and without ActiveSky active
Deleted my .Cfg file and letting P3D build a new one
Using the 18.3 airfile in place of 18.4
Various weapons loads to weigh down and settle the aircraft
Things I have noticed:
Since installing this aircraft, whichever aircraft I choose at the start of my sim session, it steers to the right when I accelerate until I correct with opposite rudder one time. Then all is well. Upon aircraft startup, I notice the aircraft bobbing up and down slightly, but there is no flutter. The flutter starts when the aircraft leaves the ground.
As the pilot's head is connected to the control surfaces, his head twists and turns like a wild man during the flutter.
These issues do not occur with Version 18.3
Thank you Sir,
Reggie
-
Copy that, thanks, I have no idea whats going on then.
-
Since installing this aircraft, whichever aircraft I choose at the start of my sim session, it steers to the right when I accelerate until I correct with opposite rudder one time. Then all is well. Upon aircraft startup, I notice the aircraft bobbing up and down slightly, but there is no flutter. The flutter starts when the aircraft leaves the ground.
A couple possibilities here: First and foremost, is your default flight, and plane, the original FSX default? IE: The trike over Friday Harbour. If not, try making it that and see what happens.
Second: Make sure that, once you get the engines fired up, and both generators on-line, press the FCS Reset switch, left side panel, aft the throttles. Then, just before you take off, when you're on the runway, all systems fired up, BIT checked, and ready to fly, just before you advance the throttles, "wipe" the controls. Move the stick in a full throw fore-n-aft, left-n-right, and waggle the rudders full throw, left-n-right. This is a habit ALL Naval Aviators get drilled into their skull housing groups from day 1 of flight school. It should be YOUR habit as well. In the real-world, wherever that may be, it gives a last check to make sure the controls are free-n-clear, nothings jammed up by a bit of FOD, which can crash a plane with no notice, no systems have failed on you, whatever. In the sim, it can clear previous settings that may have been held over from a previous flight, and so on. Some of the more religiously inclined Aviators say the Trinity to as they wipe the controls, ie: Forward=Father, aft=Son, etc. Most, however, just go with forward=testicles, aft=spectacles, left=watch, right=wallet. Handy little mnemonic :D
For the Flutter, try this: Make a back-up of it, then open the plane's aircraft.cfg file with NotePad. Scan down through it for the heading [HornetFCS] . Under that, find the line that reads AoAScalar=1.500. Change it to 1.35. Save the file, exit NotePad, and reload the plane. I don't know why, and it shouldn't, actually, but that stops the flutter. Give it a try. If it doesn't help, you can always restore the original easily enough. It worked for me, any way.
Hope this helps a little...
Pat☺
-
Hey Tuskin,
Welcome to the forums. The guys over at Groom Lake Simulations do most of our textures. I'd recommend sending your request over there.
Link: https://www.facebook.com/GroomLakeSimulations/?fb_dtsg_ag=AdySpQJZjZr__YUdhMo-jB9xZJuZ-OmVRUknpWG38FZn-g%3AAdzVt0A396duGcG-R8OczmJyhOPAYRAukYsPQbtSMk3whQ
Ah, cool, thanks.
-
Hello Pat,
Appreciate the advice, but it did not work. I don't know what the problem is.
Thanks anyway.
Cheers,
Reggie
-
Hi, Reggie :)
Just curious, what didn't work? Making your default flight the original FSX default flight, wiping the controls, or the flutter fix?
Another thought flitted through my little pea-brain: Could there be an autopilot setting left on in your default flight, which you're not noticing? That happens sometimes, and can have unexpected effects. That's why I always suggest keeping your default flight the FSX default. It "presets" switches, variables, and settings correctly that may have detrimental effects on the plane.
It's easy to return to the FSX default flight, with a simple edit of one line in the FSX.cfg file. If you want detailed instructions on this, just let us know. It only takes a second.
Of course, if you already HAVE the FX default flight set, forget I said anything. :D
Good luck!
Pat☺
-
Okay, read about a similar problem over at the P3D site. When I installed Hornet version 18.4, it some how wiped my controls. I had to reassign everything and I guess I didn’t calibrate my rudder axis correctly. Have recalibrated and all seems well now. There is a slight bobble of the elevator when I apply back stick and release, this may be normal. But rudder and elevator do not flutter and pilot no longer does the “disco duck”.
Thanks for everyone’s help,
Reggie
.
-
Hey Jimi, Sorry I havent been keeping up to date, but is the tacpack for the F-18 not signed correctly?? I still get kicked for TP sessions with anti-cheat enabled w/ 18.4.
Also I was planning on giving a quick bug list at somepoint of stuff i found with it with tp when I get the chance..
-
As I understand it, the TP stuff is still "in development". Jimi's working hard on it.
A bug list, though, is always good. You will find things others miss, I promise. The more eyes the more details found to fix :D
Hope this answers your question, Heater :)
Pat☺
-
Gents,
Here is an "unofficial" update for testing (FSX Only). Should be a little cleaner than the last release..
Link: https://drive.google.com/open?id=129IQvNCg0IhHz1c4J3J6i03UcsF8380t
-
Yeah, it did, thanks Phantom
-
Quick little bug list for the F/A-18C 18.4.120 (unofficial) version:
-RDR screen does not shown any AI on the display (does show aircraft in MP). Tried this by attempting to lock on to the BQM-74 Drone that TP comes with. The HUD locked on fine with AIM-120s (but didnt show the circle where it shows the closure distance and best time to shoot if that makes sense. I dont know the name of that feature.)
-When using TUP and TDN buttons on the RDR screen, and multiple objects are displayed, it seems like it doesnt scroll back to the first object selected, and I have to use the reverse button of whatever I was pressing, in order to scroll back the objects on screen. For example, lets say I was pressing the TUP button scrolling through 5 objects on the display. After the last object is selected in red, and I continue pressing TUP, it never returns back to the first object, and however many times I continue clicking TUP is the amount of times i would have to click TDN in order for it to start selecting the objects being tracked again.
-AIM-9s lock on, but when hud loses track of object that was locked onto, Tone sound will stay high-pitched, and the low-pitch tone will come back on so they are both simultaneously on. the 'LOCK' light in the top right of the cockpit will also stay on, if it is no longer locked.
-Suface Radar, where it paints terrain, sometimes will remain blank. Cant figure out how to temp fix this issue.
-Stores display allows user to choose Guns, while another weapon is still selected on the display. This is reflected on the HUD where it shows functions and symbols overlapping of both Gun Reticle and whatever other weapon is selected.
-(Not sure if its supposed to be like this but...) At night, all panels and buttons will be lit up, and its very hard to distinguish if a button is selected, or if flaps are half/full, if gear is down or up, etc... because they are all lit up like the LT Test switch is flicked on.
This is just the stuff ive noticed recently.. I am also very bad at explaining things. So if any of this needs clarification, please let me know
-Josh
-
Josh,
Thanks for taking the time to test and more importantly, taking the time to type up your observations.
-RDR screen does not shown any AI on the display (does show aircraft in MP). Tried this by attempting to lock on to the BQM-74 Drone that TP comes with. The HUD locked on fine with AIM-120s (but didnt show the circle where it shows the closure distance and best time to shoot if that makes sense. I dont know the name of that feature.)
Just tested and I'm able to get contacts still. What was your configuration during this observation? Did you have the AA or AG MasterMode selected?
-When using TUP and TDN buttons on the RDR screen, and multiple objects are displayed, it seems like it doesnt scroll back to the first object selected, and I have to use the reverse button of whatever I was pressing, in order to scroll back the objects on screen. For example, lets say I was pressing the TUP button scrolling through 5 objects on the display. After the last object is selected in red, and I continue pressing TUP, it never returns back to the first object, and however many times I continue clicking TUP is the amount of times i would have to click TDN in order for it to start selecting the objects being tracked again.
Known and documented issue. The coding is a little funky on this, but I'll figure it out and will fix it (eventually). Meanwhile, the TDN button works, or if you want to immediately start from the beginning, you can use the RST button.
-AIM-9s lock on, but when hud loses track of object that was locked onto, Tone sound will stay high-pitched, and the low-pitch tone will come back on so they are both simultaneously on. the 'LOCK' light in the top right of the cockpit will also stay on, if it is no longer locked.
Copy, will working on getting this fixed.
-Suface Radar, where it paints terrain, sometimes will remain blank. Cant figure out how to temp fix this issue.
This is a new one. Need more specifics on the conditions that created this.
-Stores display allows user to choose Guns, while another weapon is still selected on the display. This is reflected on the HUD where it shows functions and symbols overlapping of both Gun Reticle and whatever other weapon is selected.
Yes, guns are allowed to be used in conjunction with other weapons (as designed). Copy all on the HUD display. I'll fix it. Too easy!
At night, all panels and buttons will be lit up, and its very hard to distinguish if a button is selected, or if flaps are half/full, if gear is down or up, etc... because they are all lit up like the LT Test switch is flicked on.
That's a Texture issue. Seeing that I'm not a texture guru, I will need to find a volunteer to fix this one, so it might be a while.
-Jimi
-
hey fellas,
I give up,I can not pull up any frequencies tacan or ils and I turned the radios on what am I doing wrong?
-
hey fellas,
I give up,I can not pull up any frequencies tacan or ils and I turned the radios on what am I doing wrong?
First, have you downloaded and installed the latest from a few post up? Link: https://drive.google.com/open?id=129IQvNCg0IhHz1c4J3J6i03UcsF8380t
If not, download and give that a go. Please note it's for FSX only, but can be easily converted over to P3D if you are familiar with coding.
If you do have that one already installed and still having problems, i need more info. How did you go about turning it "on", how high were you and what were your indications? Did the scratchpad remain blank? Did you get "error" in the scratchpad? No info on the HUD or HSI?
Thanks man.
-
Jimi,
I start off on runway,I turn on the TCN radio and select TCN on HSI and --OTT appears and stays. I type in frequencies,press enter and it flashes and and nothing changes but if I change into the Blues and change back into the Fleet,the TCN appears! I'm on steam version.
-
By "turn the TACAN radio on" do you mean you select TCN with the button down at the bottom of the UFC? When you do, you see "--OTT", did you mean OFF?
If so, you need to go the button at the bottom of the HSI, far right, that says ON/OFF, and press it. If it the first use since you started the flight, you may need to press that button twice to get the indication on the Scratchpad to change to ON.
You need to do the same with all the radio's buttons on the bottom of the UFC. Like the ILS radio. Select the ILS button, the select the ON/OFF button far right.
Once the scratchpad indicates ON the radio is functional, if it's in-range to receive the chosen ILS or TCN.
Does this help at all?
Pat☺
-
They should do a FSXBA F/A-18C HORNET v.18.3.00.FSX with just the Blue Angels textures alone and not the other textures that come with the current one
-
The new version of the FSXBA F/A-18C HORNET should have contained just the Blue Angels Textures alone and not the ones that comes with the current version on this website when will a current version of the FSXBA F/A-18C HORNET be available for download containing just the Blue Angels Textures alone and not the ones that come with the current one
-
FSXBA F/A-18C HORNET 18.3.00 is really impressive especially with the Blue Angels textures and the other textures from current US Navy and Marine Squadrons and the Carrier Trap sounds are really awesome can't wait to fly it in FSX.
-
The new version of the FSXBA F/A-18C HORNET should have contained just the Blue Angels Textures alone and not the ones that comes with the current version on this website when will a current version of the FSXBA F/A-18C HORNET be available for download containing just the Blue Angels Textures alone and not the ones that come with the current one
Easy enough. Just go into the Hornet's folder and delete the texture folders you do NOT want included. Just make certain not to delete the folder Texture, as they ALL need it. You can also get into the aircraft.cfg file and either delete, or, the long, hard way, comment out, all the [fltsim.XX] entries you don't want to be included. Do either or both of these things, and bingo! Only the textures you want to have.
FSXBA F/A-18C HORNET 18.3.00 is really impressive especially with the Blue Angels textures and the other textures from current US Navy and Marine Squadrons and the Carrier Trap sounds are really awesome can't wait to fly it in FSX.
It flies great in FSX, and/or FSX:SE. Just so you know.
If you haven't flown it in FSX, BTW, how do you KNOW what the carrier trap sound sounds like? Just curious...
Pat☺
-
When will a FSXBA F/A-18C HORNET 18.5.00 be available on this site to download with the current fleet squadron textures and the current blue angels for the 2018-2019 season for FSX.
-
The FA-18C_FSXBA_BA_18.3.00.FSX looks truly awesome with the Blue Angel repaints and the fleet repaints and with the TacPack it will be a fun aircraft to fly in FSX Acceleration. I am truly excited to fly this spectacular airplane and I want to thank the fsdreamteam for making such a spectacular airplane and it will be a true pleasure to fly both the Blue Angels and the Fleet aircraft too and I really don't want to use just the Blue Angels alone but all of the textures that come with this airplane and truly experience the beauty of the FSXBA F/A-18C HORNET and find out why the Blue Angels consider this the best plane that they ever flown
-
How do you fly in the Blue Angel Diamond Formation using the Blue Angel textures for the FA-18C_FSXBA_BA_18.3.00.FSX so you can do an actual Blue Angel show in FSX Acceleration including the solo pilots maneuvers done in the real Blue Angel Airshows. I would really love fly an actual Blue Angel Airshow in FSX Acceleration including the actual radio communications like the real pilots do in the Blue Angels
-
How do you fly in the Blue Angel Diamond Formation using the Blue Angel textures for the FA-18C_FSXBA_BA_18.3.00.FSX so you can do an actual Blue Angel show in FSX Acceleration including the solo pilots maneuvers done in the real Blue Angel Airshows. I would really love fly an actual Blue Angel Airshow in FSX Acceleration including the actual radio communications like the real pilots do in the Blue Angels
[ Invalid YouTube link ]fsx+fleet+week
courtesy of Micro
-
Johan,
Can you check in your FSX (Win7) settings, in the Controls/Axis tab and confirm that you do not have multiple things assigned to the X and Y axis?
With the Warthog, I'd imagine that you have separate entries for both stick and throttle. Use the pull down tab and select the flight stick and make sure that the aforementioned axis' are properly assigned. Then use the pull down tab and select the throttle, go back to the axis tab, and confirm that there are no assignments to the X and Y axis.
I'd do the same for flaps as well. Make sure the flaps are not assigned to any axis, but to switches, buttons or keys instead.
Hope this helps.
-Jimi
Hi Jimi,
Thanks for your response and yes, you make an excellent point. The TM Warthog is driven by FSUIPC coding, so I need to make sure in the FSX settings that the check box for the stick is unchecked. I might have inadvertently checked it back on with a Ctrl + K (joystick on/off). That would explain the erratic behavior of the plane. I am going back home next weekend and will let you know if this was the problem.
Thank you again,
Johan
Hi Jimi,
I still have the same problem, even with the new version you released 2 days ago for FSX (which is my simulator). Elevators and tail are "flapping" once the bird is in the air. They work fine when the plane is on the ground. The stick and throttle are checked off in my Controls menu, as FSUIPC is controlling the plane. All my other planes behave correctly with the same setup. The plane flies well on my other machine (WIN10) but not on my old system (WIN7). I wonder if other simmers have encountered the same issue with WIN7...
Thanks for all the good work though, I will not give up...:)
Johan
-
Johan,
Is it possible that it's related somehow to the way you FSUIPC is running the controls? Have you tried just letting FSUIPC do the minimal changing of the control inputs? Like if it were the non-payware version of FSUIPC?
Just a thought. I get so very few any more...
Pat☺
-
Jimi,
I start off on runway,I turn on the TCN radio and select TCN on HSI and --OTT appears and stays. I type in frequencies,press enter and it flashes and and nothing changes but if I change into the Blues and change back into the Fleet,the TCN appears! I'm on steam version.
Menace, where you able to fix your problems with the radios?
-
Jimi,
Nah bro and I just tried again...
-
Have you tried taking off and getting a little altitude first?
-
FSXBA F/A-18C Hornet v18.4 only has the prototype and the test version does it have the other textures which includes the blue angles and the fleet textures
-
FSXBA F/A-18C Hornet ver. 18.4 (FSX) only has the Proto Type and Test version does it also come with the textures for the Blue Angels and the US Navy and Marine Corps Textures too and where can you find a texture pack for this aircraft
-
It comes with the Navy and Marine Corps squadron textures it had before. It just doesn't have the "foreign" textures included any more.
Do you have the little box down at the bottom of the aircraft select screen that says SHOW ALL VARIATIONS checked?
If you do have that box checked, can't get the different textures to show, and STILL can't get the TACAN to work, can I suggest deleting it entirely, and re-installing it?
Just a thought...
Pat☺
-
The FA/18C Hornet v18.4 only has the two texture the prototype and the test version why are the others not with this version of the F/A18C Hornet v18.4
-
FSXBA_F/A-18C_HORNET_v18.5.6 do you have an image of what the aircraft will look like along with the textures that will come with it
-
The FA/18C Hornet v18.4 only has the two texture the prototype and the test version why are the others not with this version of the F/A18C Hornet v18.4
It comes with the Navy and Marine Corps squadron textures it had before. It just doesn't have the "foreign" textures included any more.
Do you have the little box down at the bottom of the aircraft select screen that says SHOW ALL VARIATIONS checked?
If you do have that box checked, can't get the different textures to show, and STILL can't get the TACAN to work, can I suggest deleting it entirely, and re-installing it?
Just a thought...
Pat☺
-
Jimi,
Hey bro can u email me ur panel folder?
-
Where can you get additional textures for the FSXBA F/A-18C HORNET v18.4.5
-
Jimi,
Hey bro can u email me ur panel folder?
I'll have to zip up what I have and upload. I'll post once I have the chance..
-
Where can you get additional textures for the FSXBA F/A-18C HORNET v18.4.5
By default, all of the textures shown below come with all of the official releases of the 2018 FSX F/A-18C Hornet (v18.4 and below)
(https://i.imgur.com/I7Knkeq.png?1)
Should be close to 90 textures in all. Unless provided in subsequent releases (which, at this point, I don't see us doing) that's all we will be providing. Any additional textures will be through individual contributions of the sim community or through creations by yourself.
-
Nice textures does it have Blue Angels 1-6 and can you do a Blue Angel Show in Flight Simulator X using the FSXBA F/A-18C HORNET v.18.4.5 using the blue angels textures and have the aircraft in the Blue Angel Diamond and doing the maneuver's that the real blue Angel Solo Pilots do at a Blue Angel Airshow
-
Josh,
Thanks for taking the time to test and more importantly, taking the time to type up your observations.
-RDR screen does not shown any AI on the display (does show aircraft in MP). Tried this by attempting to lock on to the BQM-74 Drone that TP comes with. The HUD locked on fine with AIM-120s (but didnt show the circle where it shows the closure distance and best time to shoot if that makes sense. I dont know the name of that feature.)
Just tested and I'm able to get contacts still. What was your configuration during this observation? Did you have the AA or AG MasterMode selected?
-When using TUP and TDN buttons on the RDR screen, and multiple objects are displayed, it seems like it doesnt scroll back to the first object selected, and I have to use the reverse button of whatever I was pressing, in order to scroll back the objects on screen. For example, lets say I was pressing the TUP button scrolling through 5 objects on the display. After the last object is selected in red, and I continue pressing TUP, it never returns back to the first object, and however many times I continue clicking TUP is the amount of times i would have to click TDN in order for it to start selecting the objects being tracked again.
Known and documented issue. The coding is a little funky on this, but I'll figure it out and will fix it (eventually). Meanwhile, the TDN button works, or if you want to immediately start from the beginning, you can use the RST button.
-AIM-9s lock on, but when hud loses track of object that was locked onto, Tone sound will stay high-pitched, and the low-pitch tone will come back on so they are both simultaneously on. the 'LOCK' light in the top right of the cockpit will also stay on, if it is no longer locked.
Copy, will working on getting this fixed.
-Suface Radar, where it paints terrain, sometimes will remain blank. Cant figure out how to temp fix this issue.
This is a new one. Need more specifics on the conditions that created this.
-Stores display allows user to choose Guns, while another weapon is still selected on the display. This is reflected on the HUD where it shows functions and symbols overlapping of both Gun Reticle and whatever other weapon is selected.
Yes, guns are allowed to be used in conjunction with other weapons (as designed). Copy all on the HUD display. I'll fix it. Too easy!
At night, all panels and buttons will be lit up, and its very hard to distinguish if a button is selected, or if flaps are half/full, if gear is down or up, etc... because they are all lit up like the LT Test switch is flicked on.
That's a Texture issue. Seeing that I'm not a texture guru, I will need to find a volunteer to fix this one, so it might be a while.
-Jimi
First of all, thanks for all the great work.
I have the same problem with the Radar to detect AI traffic. Ground and sea traffic sometimes appear, sometimes not. Air traffic does not appear. If I create a tanker with Tacpack, the tanker appears one second in the radar, and then dissapears, with the tanker just in front of me.
LAU 10 and LAU 68 are most of the times I load them unusable: the counter appears as "0" even though I load them on land and they appear in the weapons screen
I suppose that I will need a functional AG radar to send Mavericks to their targats. ¿Is that right?
-
Nice textures does it have Blue Angels 1-6
Again, yes, Blue Angels textures 1-6 are included. Again, when you got to aircraft select to select your aircraft, make sure that the box labeled "Show All Variations" is checked. Provided that you haven't manually removed any of the textures from your FSXBA F/A-18C aircraft folder, you should see all of the variants listed in the previous post.
Can you do a Blue Angel Show in Flight Simulator X using the FSXBA F/A-18C HORNET v.18.4.5 using the blue angels textures and have the aircraft in the Blue Angel Diamond and doing the maneuver's that the real blue Angel Solo Pilots do at a Blue Angel Airshow
Check this website out: http://www.fsxblueangels.com/
-
Jimi,
Hey bro can u email me ur panel folder?
Give this one a go bro:
https://drive.google.com/open?id=1zpdRcmqcju13dB9mbNJT17F2xVWCoTee
-
Does the FSXBA F/A-18C Hornet 18.4.131 come with all of the Fleet and Marine Textures as well as the Blue Angels and how detailed is this one from the previous versions of this same plane and it terms of the gauges and head-up display how detailed are they and how does this plane handle on carrier landings and takeoffs.
-
Josh,
Thanks for taking the time to test and more importantly, taking the time to type up your observations.
-RDR screen does not shown any AI on the display (does show aircraft in MP). Tried this by attempting to lock on to the BQM-74 Drone that TP comes with. The HUD locked on fine with AIM-120s (but didnt show the circle where it shows the closure distance and best time to shoot if that makes sense. I dont know the name of that feature.)
Just tested and I'm able to get contacts still. What was your configuration during this observation? Did you have the AA or AG MasterMode selected?
-When using TUP and TDN buttons on the RDR screen, and multiple objects are displayed, it seems like it doesnt scroll back to the first object selected, and I have to use the reverse button of whatever I was pressing, in order to scroll back the objects on screen. For example, lets say I was pressing the TUP button scrolling through 5 objects on the display. After the last object is selected in red, and I continue pressing TUP, it never returns back to the first object, and however many times I continue clicking TUP is the amount of times i would have to click TDN in order for it to start selecting the objects being tracked again.
Known and documented issue. The coding is a little funky on this, but I'll figure it out and will fix it (eventually). Meanwhile, the TDN button works, or if you want to immediately start from the beginning, you can use the RST button.
-AIM-9s lock on, but when hud loses track of object that was locked onto, Tone sound will stay high-pitched, and the low-pitch tone will come back on so they are both simultaneously on. the 'LOCK' light in the top right of the cockpit will also stay on, if it is no longer locked.
Copy, will working on getting this fixed.
-Suface Radar, where it paints terrain, sometimes will remain blank. Cant figure out how to temp fix this issue.
This is a new one. Need more specifics on the conditions that created this.
-Stores display allows user to choose Guns, while another weapon is still selected on the display. This is reflected on the HUD where it shows functions and symbols overlapping of both Gun Reticle and whatever other weapon is selected.
Yes, guns are allowed to be used in conjunction with other weapons (as designed). Copy all on the HUD display. I'll fix it. Too easy!
At night, all panels and buttons will be lit up, and its very hard to distinguish if a button is selected, or if flaps are half/full, if gear is down or up, etc... because they are all lit up like the LT Test switch is flicked on.
That's a Texture issue. Seeing that I'm not a texture guru, I will need to find a volunteer to fix this one, so it might be a while.
-Jimi
First of all, thanks for all the great work.
I have the same problem with the Radar to detect AI traffic. Ground and sea traffic sometimes appear, sometimes not. Air traffic does not appear. If I create a tanker with Tacpack, the tanker appears one second in the radar, and then dissapears, with the tanker just in front of me.
LAU 10 and LAU 68 are most of the times I load them unusable: the counter appears as "0" even though I load them on land and they appear in the weapons screen
I suppose that I will need a functional AG radar to send Mavericks to their targats. ¿Is that right?
Very interesting. I'll take a look when I have a chance. Meanwhile, I recommend download the version at the link that i've provided a few posts above. Thanks.
-
So when will a FSXBA F/A-18C HORNET v.19 be available for download on FSX Blue Angels.com with the Blue Angels textures alone and also will there also be an FSXBA F/A-18D HORNET for download on FSX Blue Angels.com also with the Blue Angles textures alone
-
Does the FSXBA F/A-18C HORNET v18.4.131 come with an AI so that you can do a Blue Angel Airshow in FSX Acceleration
You mean like an AI Hornet? No.
Having said that, there are a number of recorder software of different kinds so you can record what you do, and then play it back, flying formation with it as it goes. Things like FSRecorder, FormationSetup.zip by Jerry Beckwith, and so on. Just Google AI Formations FSX and you'll get several viable links to different softwares to accomplish what you want.
and does it also come with all of the Marine and Fleet Textures as well as the Blue Angels Textures
Yes, it does. As has been mentioned before, make sure the little box at the bottom of the Aircraft Select screen marked SHOW ALL VARIATIONS is checked, and select FSX Blue Angels as a manufacturer. You will see all the different paints available.
Hope this helps...
Pat☺
-
Jimi,
Hey man I finally fixed it. For some reason I had to switch the Blues UFC Folder with the Fleet one,now I'm good, thanks for trying tho!
Blue Angels
-
Blue Angels,
Hey, your coming off as a suspect of being a past or present real Blues pilot, is this possible? Lol
-
fellas,
Just touching in with ya'll real quick, after a bar night, if u can afford it, build ur own rig, get Oculus Rift,Fly Inside, and @ least FSX Steam Edition and u will never go back to 2D again! I love flying over home! (Va.Beach) "Oceana"! I7 8700K,GTX 1080 TI,and enough to push them! Later!
-
fellas,
Just touching in with ya'll real quick, after a bar night, if u can afford it, build ur own rig, get Oculus Rift,Fly Inside, and @ least FSX Steam Edition and u will never go back to 2D again! I love flying over home! (Va.Beach) "Oceana"! I7 8700K,GTX 1080 TI,and enough to push them! Later!
Agreed. Oculus is a game changer for immersion! Just sucks that you have to feel around for everything lol
-
Agreed. Oculus is a game changer for immersion! Just sucks that you have to feel around for everything lol
Sux worse that some are physically incapable of using VR. You need 2 good eyes to use any VR system. Leaves me out entirely.
Oh well, them's the breaks of NavAir, as we used to say :D
Have fun, all!
Pat☺
-
Hi Pat,
I do not have good eyes, (astigmatic and hyperopic) and I fly without problems in VR with an Oculus Rift. I do not wear the glasses under the helmet. ;)
Jean
-
Ahh, but at least you have the requisite TWO eyes, Jean.
VR doesn't work with just one. It uses the different pictures on the two sides to "fool" your brain into thinking what it's receiving is in 3D. It works much like reality. You get two slightly different views in your two eyes, and your brain interprets it as a 3D world. It's one of the important things your brain learns early on in you existence.
I haven't seen the world in 3D since '92, when a wild mustang ran across in front of my bike. No way to stop at 60 MPH. Scraped me right off the back of the bike, and we all went bouncing down the highway together for a ways. Thank whatever deity you prefer for helmets, though! Apparently my head bounced of the centerline for a while, as it wound up with the neatest, bright yellow stripe down the side of it. Knocked the retina off the back of the eyeball on the left side.
Went through surgery to try and repair it, but to no avail. No retina, eyeball no worky.
Took me a while to learn the new way of seeing. Try closing one eye, and viewing the world. It appears the same at first glance, but try and pick up a pencil off the table, or have someone toss you a ball. You won't catch it, I promise. Made driving a REAL adventure, at first. ;D
So yeah, that's my long winded way of saying that I am sure VR is a wonderful thing, but I'll never be able to use it, for anything. Flying or not.
Just a "thing" one has to deal with, like it or not. I would have loved to toss a football with my kids, or play Ultimate Frisby, like I did in high school, or juggle, as I used to be able to do rather well, but hey, wish in one hand... :D
If you have a VR system, utilize it, and enjoy it! ;)
Pat☺
-
Ahh, but at least you have the requisite TWO eyes, Jean.
VR doesn't work with just one. It uses the different pictures on the two sides to "fool" your brain into thinking what it's receiving is in 3D. It works much like reality. You get two slightly different views in your two eyes, and your brain interprets it as a 3D world. It's one of the important things your brain learns early on in you existence.
I haven't seen the world in 3D since '92, when a wild mustang ran across in front of my bike. No way to stop at 60 MPH. Scraped me right off the back of the bike, and we all went bouncing down the highway together for a ways. Thank whatever deity you prefer for helmets, though! Apparently my head bounced of the centerline for a while, as it wound up with the neatest, bright yellow stripe down the side of it. Knocked the retina off the back of the eyeball on the left side.
Went through surgery to try and repair it, but to no avail. No retina, eyeball no worky.
Took me a while to learn the new way of seeing. Try closing one eye, and viewing the world. It appears the same at first glance, but try and pick up a pencil off the table, or have someone toss you a ball. You won't catch it, I promise. Made driving a REAL adventure, at first. ;D
So yeah, that's my long winded way of saying that I am sure VR is a wonderful thing, but I'll never be able to use it, for anything. Flying or not.
Just a "thing" one has to deal with, like it or not. I would have loved to toss a football with my kids, or play Ultimate Frisby, like I did in high school, or juggle, as I used to be able to do rather well, but hey, wish in one hand... :D
If you have a VR system, utilize it, and enjoy it! ;)
Pat☺
Unfortunate story Pat. Played around with Oculus Rift a little tonight, minus the use of one eye.... Obviously the 3D effects are gone as you've previously mentioned, but even so, the sense of scale and the very accurate head tracking that you get with it is still worth the investment if you can. I'll have to warn you though, it is a costly investment. Especially if your rig isn't already ready to handle it and you have to make upgrades...
my two cents....
-
Hi Pat,
Sorry for your traffic accident and its aftermath.
I was going to test the vision in the oculus by closing an eye, but jimi08 was faster.
For me, the big advantage of the RV is that we are "in" the plane.
You should be able to try one.
Jean
-
Thanks guys. I appreciate to comments. :D
IF, and as you can see, it's a big IF ;D , we can scrape the cash together, I'll get a VR of some sort, if for no other reason than the immersion factor. I may not get true 3D, as y'all noticed, but it may well be worth it. If nothing else, it'll give my lovely wife a new techno-toy to play with when she goes flying ;)
Now, I just have to talk her into it LOL!
Thanks again for the concern, all!
Have fun.
Pat☺
-
Hey Jimi, I'm transitioning slowly across to P3D and I've downloaded the latest prototype version for v4, but every time I install it (yes, I've tried several times), I don't have a HUD or FLIR. Am I missing something obvious? Is anyone else having the same problem?
Cheers
-
I downloaded the AIRound V2.0 for FSX can this be used to create a Blue Angel Airshow using the FSXBA F/A-18C HORNET v.18.4.103 for fsx
-
Hey Jimi, I'm transitioning slowly across to P3D and I've downloaded the latest prototype version for v4, but every time I install it (yes, I've tried several times), I don't have a HUD or FLIR. Am I missing something obvious? Is anyone else having the same problem?
Cheers
The latest unofficial releases that have been released are for FSX and not P3D. Since FSX tends to be more picky about coding format than P3D, I tend to do most of my developments in FSX then adapt to P3D. P3D had a completely different way of implementing the FLIR so I still have to do that as well.
When I get time, I'll post aP3D prototype version.
-
So I am not a suspect of being a past or present Blue Angel Pilot and plus I am not in the Navy or a real Naval Aviator
I'm not a real Naval Aviator, but I play one in the sim world! :D
Sorry, just a little joke, if you recall the commercial with "I'm not a doctor, but I play one on TV..."
Gad, it's been a long time since I saw that commercial...sheesh... :P ::)
Have fun, all!
Pat☺
-
Blue Angels,
Lol, I'm right there with you! When I was 8yrs, and first saw B.A.5 do his dirty roll on take off, I've been infatuated with them ever since. I've got some nice shirts coming soon too.
-
Jimi,
Hey bro, got a question,I can't seen to get the TacPac or Super Hornet to function right in the Rift,have you had any problems like this with your install?
-
Problems with Tacpack in the RIFT is mayor with the Video Features, so basically your FLIR and I think NVGs will not work, I find out last week playing with the Aerosoft Tomcat. I see how busy I am tomorow to post my Tacpack Config for the Rift.
-
Agree with Riva. If you are using Fly Inside FSX, you will have to turn off "experimental features" in the TACPACK Manager. This means no FLIR and NVG.
-
It's ok how do you create a Blue Angels Formation and also Solo demonstration in FSX
-
Solo demo: Get in plane. Fly around. Solo demo complete.
Most use FSRecorder to make formations of planes. You go in, like any regular flight, with FSRecorder running. When you finish, you have it replay the flight you just did, and go in and fly close formation on the plane it shows. Again, with FSRecorder running. Now you have 2 airplanes flying the demo in close formation. Replay the 2 plane flight, and join them, as before. Now, you have 3 planes. Replay the first saved flight again, there will be 4 planes now. If you join them, there will be 5, so you could do the job of #5. IE: Fly the solo demo while the other 4 are doing the regular demo you created. Only maneuver I don't see how to do would be a "bomb-burst". Either vertical or horizontal. Other than that...
Have fun!
Pat☺
-
Jimi,
Hey bro, quick question, is it possible for you guys to give our Hornet this effect in the cockpit?
-
That looks to me like the LEX Vapor effect. It should work fine in the v18.3 or v18.4.
You just have to have the right conditions. >=4.5G, <20, 000' Baro, >210KIAS.
Best way to see it is the tropics, with a realistic weather (high humidity, warm temps), get going about 300KIAS, low down, like around 1000', and do a tight pull. Just watch the G, otherwise you'll get GLOC, and not see a darned thing :D
Does this help at all?
Pat☺
-
Hmmm....been a little quiet around here :) just wondered if Jimi's been working on the p3d 18.4 version? Having fun with the last version, but just wondering.
Thanks!
Mike
-
Hi, Mike!
Yes, the short answer is that he's working on it as best he can.
The long answer is that he's traveling all over Europe for his job, and that takes up a lot of his time and effort. Doesn't leave a whole lot of either for working on the Hornet, but he's doing his best. Mostly working on the Manual for it, as far as I know, and checking out possible coding errors I find as I try my best to integrate the HARM missile into it. So, hopefully, there will be some real steps ahead when the next version is published.
BTW, I can't promise I'll have the whole HARM system 100% going by the next update, but I believe I will have a "fire-n-forget" version going. Maybe no PB or TOO functions, but if you get painted by a SAM or AAA radar you should be able to just point somewhere near the site and turn it loose. It SHOULD fly down the radar beam and nail the transmitter. A kind-of, sort-of, SP mode. It may or may not have the MFD and RWR displays, but I'm trying to get them too. MFDs are not an area I'm very familiar with, though.
I'm pretty sure it'll be able to stay on a transmitter that shuts off, and maybe even moves afterward. Best description of it I heard was from a Phantom Wild Weasel pilot. He said it has a "home on animosity" feature. It hates the radar vans it detects, and flies to them and destroys them with great glee, and accuracy.
Anyway, I'm working on it as fast as I can. Almost to the basic testing phase. More to come!
Far as I know, that's what going on right now :)
Does that help at all?
Pat☺
-
Thanks' Pat. Just wondered, and I understand. It must be a lot of work, especially trying to work around traveling for work! Thanks for the update!
Take care,
Mike
-
I'm not a real Naval Aviator, but I play one in the sim world! :D
Sorry, just a little joke, if you recall the commercial with "I'm not a doctor, but I play one on TV..."
Gad, it's been a long time since I saw that commercial...sheesh... :P ::)
Have fun, all!
Pat☺
Here Pat:
-
I've tried twice to download the 18.3 version and I keep getting a Queued (pending resolution error on parent folder). I extracted on Zip Extractor to get this queued signal and I am thinking I should try another Zip file. My question is what has worked. I feel the error is on my end as all the replies have been positive about the FSXBA F/A -18C Hornet. I'm using FSX Stream, which I just loaded into my computer. Appreciate any help.
-
Try using 7Zip to unzip it. That is, IMHO, the most versatile zipfile manager I've ever found.
It's readily available, and it's freeware. Just Google 7Zip .
I won't promise that's your entire problem, since I don't have Zip Expander, but I'd bet on it. Additionally, Jimi often uses 7Zip to create the zipfiles, so it's an excellent choice for unzipping it :D
Also, if you have Win10, please o please tell me you didn't allow Steam to install it's self or FSX into C:\Program Files(X86). If it did, I strongly suggest un-installing it, at least FSX, and installing someplace else. This is relatively simple and easy with Steam.
Win10, especially, has a severe problem with allowing alterations to ANY programs or files in that folder, as well as C:\Program Files. It will make your life MUCH simpler and easier to keep FSX out of either of those two folders.
Hope this is a little help :)
Pat☺
-
I appreciate your input. I unfortunately sent Steam to program files(x86), Win 10. I did not know I had control as to what file it goes to. Will give it a try. I'm not very computer smart. I flew Phantoms (VF-11) in Nam , so you can figure out my age, F-4B's did not have a computer.
-
Well, hey Killer!
Thank you SO much for your service!
I worked on the F-4N/J/S's (AERO-1A, AWG-10A/B/C, etc), mostly in Yuma, but I did short stints at Clark AB, Iwakuni, etc etc.
They finally did get a computer of sorts into the plane when they finally upgraded to the AWG-10B and C, but if it worked was a daily toss-up ???
Anywho, there are many instructions on How-To uninstall FSX:SE, and install it to another folder, to be had out there. Just google them. They are a lot better instructors for this out there, so I'll let you find the ones that work best for you. I am an absolutely terrible instructor, I fear, or I would.
Have fun, sir, and thanks again for giving me plenty to keep me busy fixing those radar systems :D
Pat☺
-
Pat, Thanks for your service and the help. Still not sure what to do to download FSXBA F-18C 14.3. I created a new folder in the C:// drive and tried to download to the new folder, but only got the instructions on how to operate A/C, probably readme file. Can the FSXBA F/A F-18C file be downloaded to documents and then activated by clicking on that file?
I'm anxious to fly this new version, but I'm totally frustrated with my lack of knowledge on computers. Maybe you could pass this on to someone who would know what to do.
Don
-
I hope that was typo, and you mean the v18.3, not the v14.3!
Go to the first post on page one of this thread. Look down about half-way, until you see the download links. The BLUE text. Left Click on the blue text. Don't right-click it and use Save Link As... Just lclick on it once. I think that that step is where it went south on you.
A new tab will open in your browser, with the file you can download showing in the upper-right corner area. There will be a little box in the center of the page with a folder looking icon that says Download. Lclick it once.
Another new tab will open, with a box top-center telling you it "Can't be checked for viruses, Download Anyway?" Lclick on that. In other words, yes, download it anyway. Depending on your internet connection, it can take a while to download. Just let it run.
Once you have the zipfile on your PC, rclick on it, and unzip it with 7Zip to the folder of your choice. I'm presuming you know how to use 7Zip, or the program of your choice, to extract files from zipfiles. Make sure you extract ALL the files/folders in the zipfile to your chosen folder. I'm not sure, but I'm pretty sure Jimi put it all in an auto-installer. You should now have a file named Install.exe, or something similar, in the folder you unzipped to. Just to double check, I'm downloading it now to make sure this is all correct. I will let you know if there are any corrections I need to make :D
Rclick on the Install.exe file you now have, and select Run As Administrator. That is important. You will get a small window open up. This is the installer that will place the plane and all it's ancillary files for you. You will need to accept the EULA, as most programs require.
It will then ask you what you want to install, the plane, or the plane and the paint kit. I don't think you really need the paint kit right now, so ensure it's little check-box is NOT checked. Click Next.
Next, it will ask you where your FSX installation is. Like C:\MicrosoftGames\FSX, or D:\steam\steamapps\common\FSX. Wherever you may keep it. Use the little Browse button off to the left of the empty box to select your FSX root folder. Once you find it, it will appear in the white box. Makes sure it's correct, then click Next.
Let it run. After it installs the plane's files and folders to your FSX folder, it will begin installing the .Net Framework file. LET THIS RUN! Do NOT cancel it. It can take a while, and even APPEAR to be locked up. It's NOT. Just leave it alone until it finishes. When everything has finished running, it will ask you if you want it to open the Readme file included. Your choice at this point. The installer should now close.
You should now have the plane in your ...\FSX\Simobjects\Airplanes folder. If you want to verify it, look for a folder named FA-18C_FSXBA_BA_18.3.00. That's your plane. IN the sim, using the Aircraft Select screen, just select the "FSX Blue Angels and Groom Lake Productions" from the Manufacturer tab. That makes sure that all you see are the paints for this aircraft.
For now, I suggest you don't use the Blue Angel paints, just the regular squadron paints. It has to do with the cockpit lay-out, to prevent confusion, hopefully :) Once you get used to the Fleet cockpit, the cockpit layout used by 99.9% of Navy/MC pilots, then you can use the Blue Angel paints to see the differences in the cockpit layouts.
I hope this helps a little. If I got too simplistic, I apologize, but you said you don't know computers. I was just trying to make it as understandable for someone like that. I certainly mean no insult whatsoever!
Good luck, and let us know how it goes for you. :)
Pat☺
-
Ok, I just got done downloading the v18.3.
I looks like it's a "manual" install. SO:
Just unzip the zipfile to the folder of your choice. It will have the lane's folder in it, labeled FA-18C_FSXBA_BA_18.3.00 .
Copy the entire folder to your ...\FSX\Simobjects\Airplanes folder.
Open the folder now in the \Airplanes\FA-18C_FSXBA_BA_18.3.00 folder labeled Extras. Copy the Effects folder to your sim's ...FSX\Effects folder. It will ask if you want to merge the Effects folder with the sim's Effects folder. Answer yes, and also answer yes to any overwrites that may occur.
Sorry for the confusion. I honestly thought Jimi had put it all into an auto-installer.
Hope this is a better version of the instructions :D
Pat☺
-
I appreciate your input, and I needed it simple so thanks. I'm downloading it now then wll unzip. I will let you know how it goes, probably tomorrow or Wednesday. Thanks again.
-
Hope things work out well for ya! ;)
Luck!
Pat☺
-
Hello!
First of all, I would thank all the people that have put work onto the Hornet, it is truly an amazing aircraft to fly! Once again, thank you all!
Now the problems that I am facing currently...
I know that the switches do not rotate/switch when clicked (for example the light switch that sits under the throttle quadrant, I think it is the nav or beacon) but I have noticed some abnormal control behavior during cruise or high altitudes (30k ft and up)
Once I get to...let's say, FL360, when I want to turn to the left/right, the controls don't feel like they were before at 10k ft or so. And when I want to do an airelon roll at 30k ft and up, it spins too fast or...should I say, dangerously fast...
Maybe that is the actual behavior of the aircraft at such altitude, but I just wanted to advise you about this problem.
Oh, and BTW, the aircraft feels normal after I descend to 10k and below, even at 20k the controls feel the same as it was at 30k ft.
Kind regards,
-
Wonderful job, as usual. Incredible plane. And the traffic gauge is fantastic. Is it available for other planes?
-
Wonderful job, as usual. Incredible plane. And the traffic gauge is fantastic. Is it available for other planes?
The "traffic gauge"? Do you mean a radar, or the Air-Air refueling gauge or...
If possible, can you post a screenshot of what you mean? I just want to be certain what we're talking about.
Good luck!
Pat☺
-
Thanks for your response, I talk about Shift+5 comination
Trying to insert an image but no luck...
-
Ok, I got it now. That's the Air-to-Air refuel gauge.
It works in any plane. You can mid-air refuel a Piper Cub, if you can make it keep up with the target plane :D
You can either use the one included with the Hornet, and simply place the gauge's CAB in the FSX\Gauges folder. That way, any plane can use it. Then add the gauge to the desired plane's Panel.cfg file, and away you go. There is a good download of the gauge alone located here:https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=145664 (https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=145664), or, as I say just use the Hornet's version.
It also works very nicely as an airborne radar system for finding other aircraft out there. You can filter for airborne only, on the ground only, or both. I usually set the filter for airborne only, since I don't really care if a plane is parked on the ground. Only in the ones in the air are of interest, to me. The ground information IS handy if a plane you are looking for is taxiing for take off, though.
Does this help at all?
Pat☺
-
Thanks!!! that's exatly what I want to do. Look for other planes. Thankyou for your time!!!
-
Glad to help :D
Have fun!
Pat☺
-
Noticed when operating in winter conditions, the snow being kicked up from the main landing gear wheels is offset some 2-3 feet outboard from where the wheels actually are. Is there a setting in the cfg that can change this?
-
It can be changed in the contact points section in the cfg file
-
Figured out its the 3rd entry on gear contact points, changed it..looked better, but unfortunately its very unstable on the Rwy with rudder corrections and wants to tip over. I'm still using ver 17.1.31, so I'll try the 18.3.
-
You'll probably have the same problems with the 18.3 as well.
-
Yes..it is so. I have a few questions, apologies if it should not be posted in this thread, do let me know. On my Saitek X-52, I have a hat button direction programmed for 2d cockpit forward view. On the ver 17.3 this was ; 8 HUD camera view, it always started with a page of script, had to click close window to clear this. Now on ver 18.3, its the same but I have no forward view of HUD or anything, just a black screen. Is there some setting I have to turn on, tried the HUD buttons nothing happened. The other question is when I shut off the engines and power down..why is the sound still on like everything is running.
-
Armenius,
HUD View: If I remember correctly, I removed the HUD only view as I was getting feedback that is it was rarely used, and I had to clear room for other functionalities that required a view.
Engine Sounds: Is there no change in sound when the engines are shut down? I remember I did a sound edit to include electronics fan audio that was connected to the battery switch, but other than than, no changes to engine sounds.
Thanks.
Jimi
-
Hi all, I was wondering any textures of the VMFA-115 for this latest and awesome F-18C?
Let me know, thanks.
-
Check Groom Lake Simulations on the book of Faces. He has recently "CAG" black -115 jet painted up that was not in the latest batch.
-
Hi Jimi,
I am a long time fan of your plane, and I have been trying to play with the new version FA-18C_FSXBA_BA_18.4.120. It's the first version I encounter the problem where none of the buttons are clickable with the mouse in the VC...Did anybody report this issue, and if so, is there a fix?
Thank you very much
Johan
PS: I am using FSX Acceleration on WIN 10
-
Hey Johan,
First I've heard of this issue. My recommendation would be to uninstall and reinstall the aircraft
-
Hey Johan,
First I've heard of this issue. My recommendation would be to uninstall and reinstall the aircraft
I just slightly changed the Point of View in the VC and it all worked out. Maybe next time this question is asked...this will help someone.
Thank you,
Johan
-
Hello. Has anyone been able to connect with vLSO? I've tried frequencies 112.00 and 57xTCN, no luck. The only way I have gotten it to work is to change from Dino's F-35(tuned in and working) to the FSXBA Hornet, then it works! Just wondered if I'm missing something simple maybe?
Thanks,
Mike.
-
Hey Johan,
First I've heard of this issue. My recommendation would be to uninstall and reinstall the aircraft
I just slightly changed the Point of View in the VC and it all worked out. Maybe next time this question is asked...this will help someone.
Thank you,
Johan
Awesome! Glad you got it to work.
-
Hello. Has anyone been able to connect with vLSO? I've tried frequencies 112.00 and 57xTCN, no luck. The only way I have gotten it to work is to change from Dino's F-35(tuned in and working) to the FSXBA Hornet, then it works! Just wondered if I'm missing something simple maybe?
Thanks,
Mike.
No luck with an idea hear. Suggest posting your issue over in the vLSO thread.
-
Ok, thanks Jimi.
-
I can't seem to find the link to the F/A-18D Tactical. Anybody have it marked somewhere ?
Thanks in advance.
Scott
-
Fellas,
I'm just checking in and hope all is well with everyone. Hey Jimi,is there an update coming or anything new for us?
-
Hey Ah-Menace,
No Sir, nothing new as of late or on the close horizon..
-
What's this issue with the standby attitude indicator? It's flipped to the bottom...
-
Looks like a texture issue, I'll have to take a look when I get the time.
-
Hi all!
I am pretty much back... 8)
I am still...again?...working on getting the HARM integration for this wonderful plane done. I've got it to where the missiles show up on the plane, and will fire when parameters are met. A target available, the HARM selected on the Weapons Select screen of the MFD (only the left one so far), and so on. I don't have ALL the HARM modes set up yet, but you can fire them off and nail a SAM RADAR that painting you, within about 85° of your nose, and I can't recall the range. But it's outside the SAM's range ;D
I am pretty sure it works vs ship fire control radars as well including CWIS.
Next, I will be working on getting the HARM integrated to all 3 MFD's, and getting the Pullback mode fully operational. That's where, if you get painted by an enemy SAM radar, the system will immediately switch to HARM mode, whatever else you had selected, and all you need do is pickle a missile off. It's great for surprizes where you're chasing a plane, or setting up a bomb run, and need to make a snap-shot to save yourself from an enemy SAM site you didn't even know was there. I'm working on it... :o
@arwasairl: That's been a known issue for quite a while. Other problems took precedence, though. Never fear, it's on...THE LIST! :D
It's a great feeling to be back, folks.
Great to see you all again, as well. I do love this plane!
Pat☺
-
Welcome back, Pat !! Looks like you have some great things in the works ! I love this jet !!
-
Hi all.
I have a very silly question: I own FSX Acceleration but I don't have it installed anymore. I switched to Prepar3dV4.5 lately. If I donwload the installer from this topic, would it install the whole FA-18 for Prepar3d? Or do I have to install my old FSX again, just to move the plane over before I can upgrade it?
Thanks for your help. It would be cool using your FA-18 again. I liked it very much in the FSX days.
-
Go to the first post in this thread, and down load the v18.3 specifically marked as being for P3Dv4. To be specific, it's the second download listed.
I can post the DL link here if you want.
I believe it should have an auto-installer. If it does, just let it run. I do hope you do NOT have your P3D installed in th C:\Program Files folder. In any event, ensure you run the installer as Administrator. Yes, it will install a whole new plane to P3D.
Make sure that once it starts to install the .NET Framework file, you allow it to finish. It can APPEAR to freeze, or stop functioning. It HAS NOT. Just let it run. It can take upwards of 15-20 minutes to finish completely. Just let it run. Go get some coffee, take a walk outside, whatever.
If no auto-installer, unzip the plane to a Temp folder someplace, and copy it to your P3D installation. Make sure that the HornetFCS.dll in the Panel.Fleet folder is the newer, slightly larger version. 107 or 109kb, iirc.
If not, go to the folder Extras under the plane's main folder. In that, should be a folder named P3D Specific Files . Inside THAT, are two sub-folders, named Panel.Fleet and Gauges, as well as several "loose" files, ie: not contained in any subfolder of the P3D Specific Files folder. Copy the "loose" files to the main aircraft folder, allowing Overwrites where requested. Copy the contents of the two folders to the appropriate locations, again allowing overwrites. IE:, copy the Panel.Fleet folder to the plane's main folder, telling it to Merge with what's already there, and allowing overwrites. Copy the contents of the Gauges to P3D's gauges folder.
Finally, Copy the Effects folder, contained within the Extras folder, to the P3D Effects folder. Ensure you permit it to Merge both the Effects and Texture folders, and allow overwrites, as always.
Does this help?
Pat☺
-
Looking for the 'F-18.dll' gauge from the old FSX Acceleration pack.
Anyone know if this tool, (link below), can provide it ?
https://www.rikoooo.com/downloads/viewdownload/8/256
Anyone know of any other options to get this one gauge besides physically re-purchasing entire FSX sim, which I really do not want to do ?
Thank-you,
M.
-
Hi pat
Thanks worked like a charm. Only problem, I could not sleep afterwards because of my slow computer it ended in more than one coffee!
Great work! Thank you very much!
-
@Beat578: Glad I could help a little. After all, you and your computer did all the heavy lifting. I just kibbitzed :D
@MZ196: That gauge recovery tool is, from what I hear, a very useful item. Big, but useful :)
It may, or may not, recover the F18.dll file, I honestly don't know. I've never used it.
If it were me, which you're not but what the heck, I would look on the Acceleration disk, if you still have it, for the file. You'll need a decent zip file extractor, like 7Zip to get it off the disk alone.
Only alternative I can think of, would be to uninstall and then reinstall Acceleration. Since I use FSX:SE, I can't say how easy, or difficult, that might be.
Are you certain you do NOT have the F18.dll file anywhere anymore? Did you look carefully in the ...FSX\Gauges, ...FSX\Simobjects\Airplanes\FA-18\Panel, ...FSX\Simobjects\Airplanes\FA-18, and the ...FSX folders for the file?
May I ask just how it may have vanished? If you accidentally deleted it, did you maybe check the Recycle Bin, to see if it was still in there?
As an absolute LAST resort, after all, you can purchase FSX:SE. It normally runs a very reasonable $25.00, and is often on sale for roughly $10.00. Sometimes a bit less, sometimes a little more. But they have it on sale pretty often. Once it's fully installed, you should be able to find it in the ...FSX\Gauges folder. Or just install fly in SE. I really like it, personally. Since I got it the day it came on the market, for $5.00 (I'm very cheap...errr FRUGAL. Yeah, frugal...), I've had ONE CTD, and no OOM crashes.
Good luck to you all!
Pat☺
-
Pat,
I discarded FSX-A discs a several years back when I switched to a newer machine and installed P3Dv3.5.
P3D does not have a F-18.dll AFAIK - I checked.
I will be doing another CPU/GPU upgrade later this year and really do not want to buy another 32 bit sim, since everything now is 64bit.
Thanks,
M.
-
I think I'll have to wait and see is FSX Steam Edition goes on sale this summer and hopefully I can get the F-18.dll gauge from it, as I don't know how else to obtain this gauge, now that I've discarded my old FSX Acceleration discs.
-
Looking for the 'F-18.dll' gauge from the old FSX Acceleration pack.
Anyone know if this tool, (link below), can provide it ?
https://www.rikoooo.com/downloads/viewdownload/8/256
Anyone know of any other options to get this one gauge besides physically re-purchasing entire FSX sim, which I really do not want to do ?
Thank-you,
M.
I actually posted a link to that very file. I zipped it and put it on media fire. It was some time ago.
https://www.mediafire.com/file/cirystyypowtrec/FA_18_dll.zip/file
-
Which version is best for P3D V3.4? As of V18.1, I see only a FSX or P3D V4 offered.
Thanks
-
Hi, Butch!
The versions marked for FSX are also for the P3D versions below v4.0. If it works in FSX, it should work as well in your P3D v3.4.
Just click the FSX download link provided, and install according to the directions included.
Note: Make sure you have a copy of F18.dll installed in your P3D\Gauges folder. I can't swear to it (just AT it ;D ), but I don't believe P3D comes with a copy of the file. Look at the link Azframer provided in the post above yours to find the F18.dll file you can download and install.
Alternatively (big word for the day :D ), if you have a copy of FSX, either the boxed version or FSX:SE, you can just copy the F18.dll file over from that. If you have the discs, but it's not installed, you can copy the zipped up file off the disc to use. You just need a good zipfile extractor, like 7Zip, to look on the discs, and extract the file onto your HD.
Finally, you need a copy of both the latest FSUIPC for your simulator version, and a copy of the .NET Framework v3.5, I think it was, although I may be wrong on the version number, installed and operating on your HD. You can download it off the net from Microsoft. You can look in the Control Panel, Programs and Feature function to see if you have operational on you HD. If not, you'll have to DL and install it.
Beware that during installation of the .Net Framework, it can SEEM to freeze, or stop working. IT'S NOT STOPPED. Just let it run. Go get some coffee, or take a walk. It can take 15-20 minutes to completely install.
Hope this is a little help...
Pat☺
-
Hello all, question... How do i enable chaff/flares, just cant remember what keys to dependence countermeasures. Thanks guys....
-
As I recall the Chaff key is the "C" key, and flares are the "F" key.
I am not certain if you need TacPack to use the chaff/flare systems. I do know you need to have the RWR active. I believe, again, I may be wrong, that the system is on by default, but if it's not I think the R key will activate/deactivate it. Or clicking on the RWR screen, lower right area of the main instrument panel, should turn it on/off.
Does this help?
Pat☺
-
Hello,
First of all I want to thank you to everybody involved in the FSXBA Hornet! The model, system simulation and textures are all stunning!
I’m having a few problems with getting it to work properly in P3D V3.4, I would appreciate it very much if it is possible to share some advice!
Short system intro:
• FA-18C_FSXBA_BA_18.4.65 (also tested the other versions, but no change)
• Netframework 4.8
• Tacpack 1.5.0.7
• FSUIPC 4.9.7.4
• FSX gauge set is installed
It load with the following message:
“Config file not found:
Using default:
…..\Prepar3D c3\Gauges\dsd_fsx_xml_sound.ini”
When I push “Ok” the aircraft load. Tacpack loadout menu is not working (I have pushed the “gun only” as instructed). Only centerline tank is loaded and pylon station 2 and 8 shows when pushing “gun only. It is not possible to get the “V” to stick in the menu for any other stores.
When flying the rudders moves suddenly to left right extreme angel. Aircraft is yawing back and forth making flying in any serious way impossible. The rudders moves visually when looking at the model from outside.
Any help would be most welcome! Thanks!
Best regards
Jens-Ole
Norway
-
Ok, here we go!
Do you have the Simconnect files from the SDK installed? 3 come included with FSX, in what little SDK it has. At least the SE version. I had to wind up using the P3D SDK, v 1.4.4747, available on the FSDveloper forum pages.
I thought, and that gets me in trouble every time, that the .NET Framework you need is 4.6.2 but I may well be wrong. It must also be the 32 bit version, not the 64 bit one. The AutoInstall file will install the correct one if you let it.
Did you mean you have the FSX files in the Panel.Tactical folder? NOT the files from the folder labeled "P3D specific files".
Did you calibrate your controls, joystick, yoke, whatever you use, before each flight? Do you have the Sensitivities full right, and the Null Zones full left? Except maybe the rudder Null Zone? That can be slightly up off the full left mark, to account for human errors in use of the rudder. Like MAYBE 10 units, at most. Really, though, the rudder isn't needed for most maneuvers, as the GCS will handle it for you. Also, the design of the airframe ensures that the rudder isn't needed for most flight operations. It's called a "feet on the floor" aircraft. Obviously a pilot wouldn't fly with his feet on the cockpit floor, but you get the idea.
Is your "default flight" the sim's default, "default flight". Not a saved default, the default one?
Do you use the FSUIPC controller configs, not the default ones? If so, set them all to their default settings, for now. You can put them back if that's not part of the trouble.
I'm just throwing out everything I can to see if anything might stick, if you see what I mean. I hope something helps :D
Let us know :)
Pat☺
-
Thank you so much for the help! It turned out that using the default flight cleared out any problems with the exception of the tacpack weapon loadout. At least I got the Hornet flying!
That advice have helped me in the past as well. Kind of stupid to forget it...
Thanks again! Off to Baden Sollingen and some CF flying :-)
-
Glad I could help :)
Glad it's going well now, too.
As to the load-outs: All I can suggest is to ensure that, once the plane is fully loaded into the world, so to speak, call up the loadout manager, select guns only, then select the one you want. Not all may be available without TacPack. All I can suggest is trying the one you want, and look on the external view to see if it shows up. You won't be able to USE any of them without TP, obviously, but you may be able to SEE them. I am not certain if the weight and drag are adjusted properly for a loadout without TP running, either. All I can suggest is, once again, try it and see. Try a loadout, and see if the plane's gross weight changes as you do. It's on the FP page of any of the three MPDs. Also on the fuel&engine display, lower left area. Beside the nozzle percentage display. Where you can set the Bingo fuel. I believe it's also on the Checklist page.
You can look and see though. Good way to explore the displays on the MPDs. :)
This isn't a "load-n-go" aircraft. Takes some learning, which makes it funner, IMO. Is that a word?
You don't need a PHD to figure out how it works, but you do need to do a little research. Run through the displays, try low-n-slow flight, try a zoom climb to see how it acts. Try out the various ACM and BFM's...you know, all the goodies. Make sure you have room to recover from a departure, though! You don't want to ride a plane into a smoking hole, as they say. It's not easy to make the plane depart controlled flight, but it IS possible. Try a few up at 30 kFt. Gives lots room to ecover. And to try out the Spin Recovery switch :D
Have fun with it, that's what matters, no matter how you do it :)
Pat☺
-
Using the default P3D V3 flight with the F-22 out of Eglin before swapping into the Hornet makes it works perfect. No strange flight behaviour. Then I moved to Baden Sollingen in Germany (using a self made scenery of the former Canadian Hornet base) the strange rudder behaviour reappeared again during landings. Then it struck me that it might be connected to 3rd party sceneries and I tested it with other 3rd party air bases I have in P3D and at all locations I get different flight behaviour abnormalities (worst is while flying in Norway for some reason..)... Moved back to a stock airport and all issues mystically disappeared.. I have never seen this with other aircraft! Any advice of what to do?
-
Any advice of what to do?
Only fly out of default airports? ;D
Seriously, though, at least as serious as I get, have you tried flying out of the problem airports, but using the default, default flight? Make the default flight the P3D v3 the default flight, let it load into the Free Flight page completely, with the chosen airport selected. Once in the world at the 3rd party airport, with the default plane, mind, the switch over to the Hornet?
Make sure you have the fewest 3rd party airports required for the particular flight you're doing. Every additional one loads up the VM space more and more, so the fewest possible enabled will allow the VM more room for the aircraft's calculations.
Second possibility, when you get the odd rudder behaviour after loading in, have you tried resetting the FCS? Small button, left side consoles, just aft the throttles. Then see what the rudders are doing. Just press it in, and after about a second it'll pop back up by it's self. Should be done during any flight prep, like wiping the controls.
Does the rudder problem only occur when in multiplayer, or both single player and MP? If in MP only, have you tried loading the Hornet into the world in SP, resetting the FCS, which should be part of any preflight prep, like making sure the generators are on, etc, anywho, and then going into MP? Might be worth a shot.
Another possibility is to reboot the computer before any flight. Might be a bit if a PITA, but it may help. Make sure that you always recalibrate your control device, prior to launching from the Free Flight menu page, after a reboot.
Speaking of, do you have the Rudder Axis with a slight Null Zone? Say about 5 or 10%? You may have a slightly "noisy" controller, especially if it's one that uses potentiometers instead of Hall Effect diodes, and setting a small Null Zone value may reduce the noise input to the system. Also, is the Sensitivity full right?
Ok, my brain just smoke-checked. Not enough coffee. I hope something will help in all my babbling...
Pat☺
-
I've run into an issue, using version 18.3. When selecting a flight in FSX, as the aircraft renders in the 3D viewer, there is a single beep. Start flight and the beep is repetitive every 3 seconds, forever, the MFD's are blank with standby flashing. Switch to a different livery, start flight, single beep, MFD's switch on and everything's OK. Anyone run into this, and is there a switch for the MFD's, read through what manuals I have, but no luck. Tried the FCS reset button, does nothing.
-
I've never seen it either.
Are you using the sim's default flight, the trike over Friday harbour that comes with the sim, as YOUR default flight?
Do you have the .NET Framework 3.5 installed and active? The latest FSUIPC for FSX installed?
Each MFD does have an on/off switch upper right corner, IIRC. I don't think those are the problem/solution, though.
Let us know how things work out!
Pat☺
-
When will the FSXBA_FA-18C_Hornet_v19.4.131 be released
-
Hi to all,
please i need help with this great plane.
Is possible to fly this birds without joystick, eg with keyboard elevators, rudder etc?
I try stable version 18.3 and latest test version with exe file FSXBA_FA-18C_Hornet_v18.4.131 in FSX Acceleration, buth have problem with keyboard steering.
On ground everything is ok buth when in air, keyboard commands not working until cruise altitude, any help please?
PS
sorry for my bad english, kind regards.
-
This forum is dead ? ???
-
No, it's not.
I only check the forums at MOST once a day. I'm working on the Hornet, trying to get the AGM-88 installed and fully functional. It's not an easy task for an XML newb like me, but I'm working through it. Takes a lot of my sim time, that I used to use for flying. I am enjoying the heck out of it though.
Point is, I may not check the forum every day, and I may or may not have an answer to your question. The true pro's at this are still active duty military, and may not be able to check the forums every day either.
So no, the forums aren't dead, but remember, patience is a virtue :D
To answer your questions, yes, you CAN in fact fly the plane using the KB, but doing so is NOT recommended. You can't get the fine control inputs you truly need to fly the plane correctly and well. IMO, a joystick and rudder pedals are the way to go, although given the qualities of the FCS, you can do it very effectively without the rudder pedals. They make doing the pirouette maneuver, and some others, much easier, though.
As to your second question: it sounds like you're using the autopilot during take-off and climbout. The autopilot in an F/A-18 is what's called a pilot relief system. It's really made to take some of the load of flying a high performance fighter aircraft off the pilot for a short time. It allows him to set up systems for the next phase of flight, like landing on the carrier, for example, set up radios, program in new way points, troubleshoot problems that crop up, and so on. It is not made to fly the plane the way the big tube liners do. This is not flown by pushing buttons, like the big planes. If you're using the autopilot like the tubes do, it won't work very well.
Additionally, if you can't get the keyboard to work, are you using the command to make the mouse function as the stick? No, I don't recall it right off the top of my head. CTRL+K? I think? If you are using that, the KB will not function for use as a stick.
SO, you can try either making sure the AP systems are all off, and/or ensure you don't hit the mouse-yoke feature somehow.
Finally, are you using a saved flight that is NOT the sim's original default? The trike ove Friday Harbour. If you are, don't :D Make sure that the sim is using the default default flight only. It sets up systems and various variables the plane needs to fly correctly. Once it's loaded all the way into the Free Flight page, then you can switch to the airport and plane you desire.
By the way, mixing the two versions won't function correctly. If you're using the v18.3 for everything, like panels, sounds etc, but the v18.4 executable, it won't work properly. Use one or the other. Don't play mix-n-match.
Does any of this help at all?
Pat☺
-
Pat, thanks for your answer.
My english is bad, so i will be short
1. "mixing the two versions "... no, not mixing, first install 18.3 and keyboard commands not work ( elevator, ailerons/spoilers, rudder)
then unninstal 18.3 and install 18.4 executable, again dont have commands in air. On ground all commands work .
For elevator up i use number 2 on numeric pad on laptop, 8 for elevator up, 4 for ailerons left and 6 for ailerons right, so not use mouse funkction.
2. "autopilot during take-off and climbout"...no, i try take-off and climb manual from carrier Nimitz, flaps down, stick backward ( in this moment elevators work no problem) then,full throttle for takeoff , catapult, in air,and from this moment commands not work, pilot's stick not responding and stuck in neutral position, can not anything with elevator and other steering command...
Also i tried in registered FSUIPC latest version assigment for commands but not work again.
3. My default flight is cold and dark default C172 in my fictional small airport.
I dont know , maybe is this F18 have fly by wire system, like Aerosoft Airbus for example, and steering command not work without joystick and that's why I asked.
Again, thanks for your intersted for my problem and sorry for your time, cheers.
-
3. My default flight is cold and dark default C172 in my fictional small airport.
In my humble opinion, there's your problem, right there.
Try restoring the default default flight. I'm not trying to confuse you. What I mean is to restore the sim's original default flight. Easy way to do this, I personally find it the easiest way, is to ensure FSX is closed, and then open the FSX.CFG file with the NotePad program that comes included with Windows.
Also, always start NotePad as Administrator. Find the executable for NotePad, usually in the Windows folder, and right click on it. When the menu opens, select Run As Administrator from the choices.
Then, go to C:\Users\<Your User Name Here>\AppData\Roaming\Microsoft\FSX and locate the FSX.CFG file. Make sure you are able see hidden files and folder. I will tell you how to do this if you don't already know.
Once you have the FSX.CFG file opened in NotePad, scan down until you find the title [USERINTERFACE]. Under that heading is a line that reads Situation= . What follows the equals sign ( = ) doesn't matter. Erase everything following the equals sign on that line.
Once you have done that, save the file off, and start the sim. When you get into the Free Flight menu page, it should have he Trike as the aircraft, and Friday Harbour as the location. NOW you can load the flight you want, but I strongly suggest if you want to start the Hornet in cold-n-dark configuration, set up the Hornet that way.
Shut the engines down by hitting CTRL+SHFT+F1. Once the engines are spooled down all the way, IE, RPMs are 0 on both engines, make sure you hit CTRL+SHFT+F4 to turn the fuel valve back on before saving the flight off. Also, it's a very good idea to leave the Battery switch off so you don't drain the battery before you can start up the APU.
Follow the checklists to start the plane up. Make sure you hit the FCS reset, located on the left hand panels, just behind the throttle quadrant, once the plane is completely started up, with the generators on line.
Also make sure you press the take-off trim button top of the rudder trim knob, again, on the left hand panel, farther behind the throttles than the FCS reset button. Do this just before you start the take off roll, after you have wiped the controls. Remember that the plane is a "hands off" system during a launch, especially from the carrier. Once the plane has rotated to the correct pitch after leaving the catapult, about +10° above the horizon, then you take control of the aircraft.
Even with all this, I can not promise that the plane will respond properly to keyboard only command inputs. Just go out and get a decent quality joystick that's within your budget.
I realize this a lot to translate easily, but just take what I've written a little at a time, and make sure you understand it before going on. Any questions you have please feel free to ask. I will do my best to answer them.
Hope all this helps a little bit...
Pat☺
-
Pat, you are man, thanks .
My problem is joystick, BUT,right now i got Logitech 3D pro and command work normally and my
landings on carrier is much better with joystick :)
Only one more problem...
Sometime on startup i got warning APU ACC and not have HUD.
APU switch is in ON position, but where is HUD switches ON/OFF. Button with name Bright under scratchpad ?
My startup procedure is:
1. APU ON
2. Battery ON
3. Start engine left
4. Left generator ON
5. Start engine right
6. Right generator ON
I search over interner for any video tutorial but not found it...
Kind regards !
-
Hi! Glad it's getting better :)
One thing, though...It should be battery ON, Then APU ON. Watch the APU stats on the Engine Monitor page on one of the MFDs. Once it's fired all the way up, ie: 100% RPM, then start switch to Right. Once the engine fires on and climbs to idle, about 68%, right Generator ON. Same for Left, once the Start switch centers it's self. Wait for the switch to center automatically, then go ahead and start left.
The reason to start right first is that it powers the Brakes Hydraulic system, so the plane has brakes if you need them.
Now, as to why no HUD...
It should come on automatically once you turn on the Battery. At the latest, once the Right Generator is on and operational. Absolutely, it should be on when both Generators are on-line.
If not, check the switches below the UFC. One is labeled BRT. Make sure it's all the way on. Another is DAY-NITE-AUTO. It should be in AUTO.
Right under the actual HUD combiner glass, is a switch labeled MAN-OFF-Auto. It should be in AUTO.
If none of this works, try loading the F/A-18C from the Free Flight page. Once the sim boots up completely, with the default flight of the trike at Friday Harbour, select the airport you want, and select the Hornet from the Aircraft Select page. Then select Fly Now. The Hornet should load up in the world on the end of the runway, all systems on, both engines running. The HUD should be ON when everything loads in.
Let me know is any of this works. If it does, we can see if we can find why the HUD's off when you manually start the plane from the cold-n-dark configuration.
Once again, it's important to start the Sim with the original default flight. The trike etc.
If you're determined to use the cold-n-dark C172 as your default, ensure that when you save it off, the Avionics switch is ON, not off. Once you do that, restart the sim, and see if the HUD is on as I described, when you load the Hornet in.
Let me know if you get any error messages. Usually the error shows up as a red or green banner across the top of the screen when the plane loads into the world.
Pat☺
-
Huh...i am so tired with this plane :(
Yes, now is default flight trike on Friday harbour, change to F-18 and he's ready, all systems on, both engines running, HUD working, but, i can't enter Tacan code and ILS frequency in skratchpad...
When enter numbers and click enter i have error in skratchpad.
Also, i have APU ACC warning...
FSX Acceleration, FA-18C_FSXBA_BA_18.4.131 installed with exe file...
I no longer have an idea what to do..
EDIT:
Changed default flight to default C172 cold and dark and now skratchpad work ok except i can only enter ils frequency format eg 110.900 for both Tacan and ILS , format eg 45X ( of course without enter X only 45 numbers ) not work in Tacan mod...anyway, both navigation mode work when flying.
APU ACC warning still here.
My FSX folder is on C partition, not in default program files, antivirus exclusions is set for all FSX things, FSX run as administrator and every addon install as administrator...
I am very active simmer last 6-7 years, so not newbi, i fly some complex aircraft like PMDG 747, 777, 737, A2A Connie, Stratocruiser, Aerosoft etc etc all with cold and dark startup on gate/ramp, but this plane make me crazy :)
One more question, this plane have or dont have autothrottle option?
Best regards.
-
Hello. Of course it has an autopilot option. And much more!! Did you not see this?
http://www.fsdreamteam.com/forum/index.php/topic,20.0.html
-
Yes, it does have the Autothrottle option. It also varies depending on whether you are in Up and Away (UA) or Power Approach mode. The key command is SHFT+R. In UA mode, it holds the airspeed at what it was when the ATC was activated. In PA mode, it holds the plane at the correct AOA, or 8.1°. There are no cockpit switches for it. You must use the key combo.
There are a variety of actions that will deactivate it, too. Throttles above 90% or below 60%, any throttle movement by the pilot, etc. If it disengages, just cease whatever action caused it, and re-engage it.
When you load the Hornet into the world from the default, default flight, you must turn the UFC ON to enter any numbers on the keypad. Select whatever you want, like TACAN, for example, and then press the ON/OFF switch. It's the far right end of the bottom key set on the UFC. At the very bottom of the UFC. You must turn on whatever you desire to enter individually. IE: Select TCN, and turn it on, them select the ILS, and turn IT on.
When you load the plane from the cold-n-dark C172, it messes up the UFC and radios. If you want to do that, try making sure the radio switches are all turned to the ON position before saving it off. Make sure the Avionics switch is left ON too. I can't swear that all this will work anyway, as the C172 radios can't handle tacan inputs, so when it's used as a default it sets the Hornet's radios up the same way. Can't take the TCN style inputs.
I am not certain about that APU ACC error lite. I've seen other people with that problem, but I can't remember what, if anything, they did to fix it, if they did fix it at all.
Just curious, you did make sure you installed all three of the Simconnect files when you installed the sim, yes? You can find them in ...\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces . There are three one in each of the folders. Install them oldest to newest order. They are automatic, just make sure you use Run As Administrator when you run the MSI file, and it will install to the correct location.
I hope something in alll this helps somehow...
Pat☺
-
Ok, i reinstall complete FSX and all addons, default trike in air over Friday harbour and now is ok with HUD and UFC, only APU ACC still here.
Pat, how to start with cold and dark in this plane, what proccedure you recommend?
Kind regards.
-
I am blind for cold and dark :)
NOW you can load the flight you want, but I strongly suggest if you want to start the Hornet in cold-n-dark configuration, set up the Hornet that way.
Shut the engines down by hitting CTRL+SHFT+F1. Once the engines are spooled down all the way, IE, RPMs are 0 on both engines, make sure you hit CTRL+SHFT+F4 to turn the fuel valve back on before saving the flight off. Also, it's a very good idea to leave the Battery switch off so you don't drain the battery before you can start up the APU.
Pat☺
-
Ok, i reinstall complete FSX and all addons, default trike in air over Friday harbour and now is ok with HUD and UFC, only APU ACC still here.
Pat, how to start with cold and dark in this plane, what proccedure you recommend?
Kind regards.
Easiest way would be to set up the Hornet in a cold-n-dark configuration.
Load it like normal, on the end of the runway, engines running from the Free Flight page. Once again, leave the default flight the trike over Friday Harbour.
Either slew or taxi to where you want the plane to be when it loads in, and shut it down. Easiest way is to set the Parking Brake, then hit CTRL+SHFT+F1. After the engine's RPMs indicate 0 on the Engine Monitor page of an MFD, turn the battery OFF. The two generators will turn off by themselves as the engines spool down below about 62%, but you have to turn the battery off manually.
Once it's all done, hit CTRL+SHFT+F4 to ensure the Fuel Valves are back on so you can start the plane normally.
Once all this is done, save the flight off. Do NOT make it the default! Give it an easy name to remember, like Hornet1 or whatever.
Next time you want to fly the Hornet from the cold-n-dark set-up, load the sim normally. It should load with the trike over Friday Harbour. Once it does, go to the Free Flight menu, select the flight you saved off before. Hornet1, for example. The Hornet, parked, in the cold-n-dark configuration. Remember, the batteries in the sim don't last long, so as soon as you turn the battery switch ON, start the APU right away. Once it's running at 100%, set the Start Switch to Right. Watch the Engine Monitor page on an MFD, and once the right engine reaches 65%, roughly, the Start Switch should recenter it's self. Turn the Right Generator ON. Same procedure for the left engine. Once you get both engines running and stable, hit the FCS Reset button. The APU will shut off automatically.
Set up a flight plan, if you want, and taxi out to the runway. Wipe the controls, press the Take-Off Trim button on top of the Rudder Trim Knob. Advance the throttles to 100%, and start the take-off roll. Don't use afterburners unless the plane is heavy enough to warrant them.
Please note, you can not start on a boat in cold-n-dark, if you load the boat in with AICarriers. In other words, if you save the plane on the carrier deck, when you load the saved off flight the next time, there won't be a boat there. You'll take a bath in sea water. Very uncomfortable!
The best thing to do in that case is to load the plane as above, then slew out over the ocean before you start the plane. Set a boat with AICarriers, and slew out to the boat. Set the plane down on the boat in the parking spot you desire, and take it out of slew mode. Set the boat in motion, start the plane normally, and away you go.
Alternatively, you can save the cold-n-dark plane on the boat's deck, but before you save it off, place it in SLEW mode. Once you do that, the next time you load the plane in, it will be above the ocean where the boat was, and in slew mode, when you saved it. Load the boat you want with AICarriers, and set the plane down on the deck. Remember to slew the plane up above the deck a ways, say 50-100', then set it down on the deck. This makes sure the gear is ON the deck, not IN the deck. Take the plane OUT of slew mode, and then set the boat in motion, and start the plane up, and go flying.
Remember, that if you slew out to a boat already in motion, you will have to keep the plane right above the boat, moving, as you set it on the deck. It really adds to the difficulty of placing the plane in the right place aboard the boat. Easiest to set the plane where you want it on the deck on a motionless boat, take it out of slew mode, then set the boat in motion.
Ok,I've rambled on long enough. Does this help at all?
Pat☺
-
Pat you are great and thanks for all your answeres and your time.
Mayday mayday, sometimes I think i use the wrong plane :) ,some of the things you mention to me do not exist. :(
So, i use (after comlete FSX reinstall) plane in this thread from first page : FA-18C_FSXBA_BA_18.3.00 for FSX of course becaouse i find this version have better fps on my configuration, and put this folder in FSX-SimObjects-Airplanes.
You say:"Watch the APU stats on the Engine Monitor page on one of the MFDs'' ... but i dont have this options for APU on the MFD engine page.
Today before your sugestion for cold and dark F18, i try same thngs like you recommend...default trike over Friday harbour is set as default flights, then saved F18 ( not set as default flight) with engine off and all oFF, but when load this flight next time F18 is runing engines and all except APU.
Next you say :'' The two generators will turn off by themselves as the engines spool down below about 62%''...
No, on my plane generators stay ON forever when shutdown engines manualy and even with keyboard command CTRL+SHFT+F1.
Bright (BRT) knob under UFC not work for me, forever stayed in left position, i try with mouse left and right click, mouse wheel, but not work.
That is why I have the impression that we are talking about two different planes...
For carriers takeoff i use rcbco-30 and CV66, CV68 and CV69 on my own customized location around the world, Aicarriers i use only for landing , so not problem with cold and dark start on my carrier .
Kind regards.
EDIT:
Just example for engine info on MDF
Default FSX F-18 have APU info
(https://i.postimg.cc/nzvJ1NC4/default.jpg)
and FSXBA F-18 dont have APU info
(https://i.postimg.cc/XYTmDQMQ/FSXBA.jpg)
EDIT 2:
For generators turn off by themselves as the engines spool down below about 62%, ok not turn off visual but have warning gen off, this is ok.
-
Hmmmm...
You're right. I must be thinking of an older model. Maybe. Let me do some research.
I have some real life stuff to take care of. Let me have a couple of days. I'll have to re-install the v18.3. I'll need some time, ok?
I will get back to this as fast as I can, but like I said, I have some stuff I need to take care of at home.
I'll get back to you as fast as I can. In the mean time, just fly the v18.3 as best you can. It really is a great plane...
Pat☺
-
No problem Pat, just go easy, real life is on first place, cheers.
-
Hi,
I deeply love this plane but there seems to be something awfully wrong with my installation.
(FA-18C_FSXBA_BA_18.4.65, latest P3D 4.5, latest FSUIPC, latest EZDOK)
When the mouse hovers over some buttons then indications show up which do not fit to this button. E.g. CRS button shows Oil temperature. Or clicking on the MAP button on the lower MFD then the cage/uncage button of the ADI moves. (Screenshots attached)
I guess this is related to serious problems with the autopilot.
E.g. deactivating BALT the plane pitches up 50° and more and is completely out of trim.
Another example AP is in BALT & HSEL and I clk CSEL on the MFD in HSI mode the plane goes crazy, pitches up vertically in the sky.
What did I miss or have done wrong?
Regards
-
Hi,
The VMFA-323 Death Rattlers link is dead
???
-
zsoltquack,
What about the one in the master repaint list from Groom Lake?
https://groomlakesimulations.wixsite.com/groomlake/jimi-s-f-a-18-hornet
-
Hi guys !!
Today update to 18.4.... the installation was right but when I opened the P3D v4.5 and load the plane and cockpit....
(https://imgur.com/XTPv36s)
can’t show displays in the screen monitors ... not show AUTOPILOT and any frase in center panel...
Someone can help me ??
-
Re-visit as I'm on a F-18 kick lately with the recent DC Designs payware basic Supers and another combat sim platform. FSXBA 18.4.xxx Tactical installed into P3Dv4.5HF2, current Tacpack and ActiveSky running. Overall great progress so far and mostly the same findings for the autopilot extreme pitch up and a few other minor issues, but I was able to take off, drop bombs, kill a drone w/ AIM-9s and land safely. Working a few things like the FLIR and radar displays.
-
Can I just confirm, when you install the P3Dv4 version you have to have the FSX version installed first like the installer says? Installing the latest version.
Regards
Dale
-
I've been away from the online scene for a while. I have checked in a little here and there but hard to make out what has been happening. Is the Hornet work over with or what?
Since the slew of photos hit the internet of the new Fat Albert paint scheme I started on painting a freeware version.
https://www.premaircraft.com/C-130J/index.html?fbclid=IwAR3lySZ7xJcJo5VLe89GG6Rf3gyTCQUF75m6uPoI5ZqRkptL7CWVxeWkaxM
-
I finished the textures for the 2020 Fat Albert last night.
https://simviation.com/1/search?submit=1&keywords=Lockheed+C-130J+Blue+Angels+Fat+Albert+2020+Textures&categoryId=54
-
Any chance this can be mmade for the Captain Sim C130J? Please
-
Any chance this can be mmade for the Captain Sim C130J? Please
I don't own the Capt Sims C-130J.
-
Hello.
Happy new year to everybody.
Please, where can I find a link to download FA-18C_FSXBA_BA_18.4.131 ?
Best regards
Gilles
-
Gilles, for the downloads, go to the very first page of this topic.
Mike
-
Hi all, i will be switching to P3D v4.5 and wanted to know if the Hornet v18.4 works well with v4.5?
thanks guys.
Jax
-
Hey, Jax. Yes it works great in v4.5.(even with the newest hot fix)
I love it, and use it alot!
Mike
-
Awesome Mike, thanks. ;D
-
Does anyone know where I can find the textures of the 2016 CF-18 demo, if it is at all possible?
-
This the whole aircraft?
Running P3Dv4.5.14.34698
-
This the whole aircraft?
Running P3Dv4.5.14.34698
HI, 72westy. yes. go to the very 1st page, and look for this.... FSXBA F/A-18C Hornet ver. 18.4 (P3Dv4)link (as of 31 AUGUST 2018)
-
Quick question: Is drag of AG ordenance properly set? I am finding it quite heavy to fly and accelerate with 4xGBU12 and 2 external fuel bags. It hardly gets at 410 KIAS MIL, sea level
Thank you!
-
Any further progress on the Hornet?
-
Hi, 72westy. I can't believe nobody responded to you, but here's what happened to Jimi and this project...They are now "MSFS Blue Angels". Here's the link...
https://mfsblueangels.com/aircraft-download
Mike.
-
Testing the Hornet with P3D v5.3, so far so good. One issue is the FLIR not turning on, and I have the latest Tacpack version.
-
It's a known issue that the FLIR only works with FSX. If you look at the issues for P3D it says that.
Take care,
Mike
-
It seems that FA-18C_FSXBA_BA_18.4.65 has not the ability to detect naval targets using radar in SEA mode. Any info about it?
Thank you!
-
Are you on FSX or p3d ?
-
P3Dv4.5