norman99

I'd also like this addressed. Significant wind increases within 500ft are frustrating when operating around the boat.

Great app, I use it all the time to display the Hornet IFEI on my phone. I just have one request. Is there any possibility of adding working nozzle position indicators to the IFEI?

My big complaint is why are ED spending so much time and resources upgrading models that already exists in DCS, instead of first adding much needed new models to the simulator? The SA-5 comes immediately to mind. Why not develop the Square Pair, Tall King, IFF & Odd Pair radars units so we can deploy this system correctly? Or, instead of reinventing the wheel, why not just purchase the readily available models and incorporate them into DCS?

Flying around with the burners barely lit up for a few minutes without realising is not ideal. If you don’t have a physical AB detent, setting MIL power can be tricky, hence I glance down here to see RPM, FF and nozzle position. I too sometimes have to tilt my head to see everything.

Maintaining 4999ft above the target, should work well. 5001ft won’t. The radar in the hornet has a significant (many would say very unrealistic), arbitrary look down penalty applied when the target is more than 5000ft below your aircraft. This is applied irrespective of target RCS, closure, altitude, background clutter etc etc. Apparently ED is re-writing/improving the radar, so that it behaves more realistically. All we can do is wait and see what this brings. Whilst not necessarily the only thing affecting you in the scenario you described, it definitely doesn’t help.

Still no chance of getting nozzle position working on the Hornet IFEI? Other hardware manufacturers (Tek Creations are one) manage to make this work, so the data must be available to read somewhere.

Seems like ED are back to burying their head in the sand when it come to things they don't understand. The AZ/EL FOV is wrong, and should be fixed. If it is incorrectly showing the bounds of the radar scanning area as absolute elevation values (as opposed to angular elevation), then there is a misunderstanding on what this function is actually supposed to display. Some feedback from either @BIGNEWY or @NineLine would be greatly appreciated.

9.7 seconds!

WOW!! Based on that list, it almost looks more feature complete than the Hornet already!!

I’ll add that you can turn the burble effect off, by disabling wake turbulence.

But how often are you (or viper/hornet drivers) heads down, working the radar & TGT pod, whilst simultaneously flying at <200ft agl, at night without NVGs?…… This is the mission the F-15E was designed for. (It’s basically a poor man’s F-111 replacement).

Just bumping this issue again for users without a depressable TDC cursor on their controls. ED, can this please be considered?

Accurately tracking to a TCN with a significant crosswind can very easily be done in HSEL. Simple adjust the HSEL bug until the ground track pointer, (small diamond at the top of the HSI, is perfectly in line with the TCN bearing pointer (triangle on the outside of the HSI compass rose). Even easier, engage the AP in TCN CPL mode. Then just move the HSEL bug to match the aircraft heading, under the lubber line at the top of the HSI. Then select HSEL.

Yep. You can have a course line selected, and couple the AP to fly that specific course, or you can hide the course line, and have the AP fly straight to the TCN. You just can’t do both. The simple answer, change to HSEL before you select the runway course. In this regard, it’s exactly the same as coupling the AP to a VOR NAV receiver in any civilian aircraft. Want to fly straight to the station but have a different radial selected on the OBS, then you’ll need to use HDG hold to make it work.

Another issue stemming from the same problem. As DCS incorrectly senses any turning of the carrier as the aircraft moving, as soon as it moves the AI wingman instantly start to taxi towards the catapults for launch, even if the player lead hasn't moved. This breaks missions where the player colds starts, with launch 10-15min away, as the rest of your flight just launch immediately and go off without you. Mission & Track attached. P.S. I'm sorry if this sounds like a whinge, but can the SupperCarrier please get some love soon. It's still full of significant bugs, and nowhere near feature complete. I know the briefing room and other new tech will take a while to develop, but in the meantime, can we get some improvement/fixes to what we already have? Carrier Taxi Bug.miz Carrier Taxi Bug.trk

Thanks @Dos, I'll give that a try.

I've experienced this when changing slots too. I Have to exit the server completely to get it working again.

So, I'm having an issue with SimAppPro and the export.lua which prevents the MIP UFC displays from working. The only fix I've found which works is to re-order the entries in my export.lua, placing the two WW entries at the bottom. Unfortunately, everytime I open SimAppPro, it checks to see if the two WW entries are listed first, and if not, it adds them to the top of the export.lua, regardless of whether they are already present in the file. The end result of all this is I need to start SimAppPro, then manually edit the export.lua to remove the newly added entries at the top of the list. Every single time!! It's beyond frustrating. Dose anyone else have this issue, and or a permanent solution? Here's my export lua for reference. local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') pcall(function() local pw=require('lfs');dofile(pw.writedir()..[[Scripts\pw-dev_script\ExportInit.lua]]); end,nil); local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); local TheWayLfs=require('lfs'); dofile(TheWayLfs.writedir()..'Scripts/TheWay.lua') local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua')

Yep, it’s just a shame that CBUs in DCS are so ineffective against SAMs.

Because, the ACLS system is in Traffic Control mode, indicated by T/C on the link 4 display. Technically, the T/C mode provides data link heading commands to aid the pilot in reaching the marshal point and/or it may be used for azimuth alignment from marshal until ACL acquisition. These heading commands can be coupled to the flight control computer for automatic lateral axis control or can be used for manual steering aids. In practice, DCS’s version of T/C seem to always direct you to a place on BRC, about 30-35nm from the boat. There is no real variation to this.

Disregard the above, I've found a solution. In the Hornet, if you create the waypoint sequence you want first, and box it, then The Way will add its data to the waypoints in the current sequence, rather than starting at waypoint 1. It does however skip the first waypoint in the sequence, so add an additional waypoint to make it work. For example, if you need 4 waypoints, make sure there's 5 in your desired sequence. eg. 15-16-17-18-19. Then just delete waypoint 15 from the sequence to have 16-19 programed correctly. If everyone already knows this, I apologise.

Fantastic mod, absolutely love it. I only have one suggestion. Would it be possible to have the user select the first waypoint number that The Way uses to insert its waypoints? For example, a lot of MP servers will have waypoints already setup, such as WP 1-14. It would be great if I could select WP 15 as the first place The Way starts inserting data, so I'm not overriding any mission data already present, rather just adding to the waypoint list at a selectable point?

Blame Windows 10, and it’s poor multi monitor support. Apparently upgrading to Win 11 helps, as it stores the additional monitor’s settings after they’ve been disconnected. I haven’t personally tested this though.

Any update on the overly exaggerated burble/ground effect combined with ACLS Mode 1 causing constant bolters? @BIGNEWY, as per your response here, this was reported a year ago. This has been an issue since ACLS release, and makes Mode 1 almost completely unusable. I understand we can downgrade to Mode1A/2, or turn off the burble effect via the wake turbulence option, but this is a temporary workaround, not a long term solution.

So, seems this problem has returned, even with all texture mods removed. I can't see the deck lights till almost at the ramp, exactly as shown in the video in the first post. Any suggestions?