DP Spaz

I just tested this, 100% accurate!.. was able to zoom out a bit more and save the view... now the FOV in 2D is perfect! Thanks for the info, certainly other will want it as well.

I am not seeing the 30 degree down look perspective. What I am seeing is the field of view (FOV) adjustment only allows to see the top half of the top row of instruments directly forward. Tired to adjust the FOV using "/" & "*", this is the max adjustment back from the instrument panel. Would expect adjustment would allow a little further back so that you can see more of the instrument panel. This occurs in 2D using the monitor without head tracking, and also 2D using my Tobii Eye Tracker 5. I tried to slew around in the cockpit with the r-shift number pad keys, its not working. When I hit a key command, it jitters and falls back to this default view. It does not allow me to slew around the cockpit. In VR using my Quest3 and Virtual Desktop, the FOV is perfect and no issues. Here is a screenshot of the FOV furthest back in 2D. You can see what little the instrument panel is visible. Its like you are sit right up against the instrument panel, or a padlock view perspective..

Thanks for getting back regarding my question!.. its great to have you back and working on this really sweet mod!!! It brings so much to DCS and Naval Aviation as a whole. Hopefully you will get some additional help and can get it completed, which would be awesome!!!

It's great to see some work is continuing to fix and bring more capabilities to the T-45! I'm curious and need to ask, are you part of VNAO or working with some of them on this? Been hoping for years now that this effort would get picked back up and finished! I wrote code years ago (very long time ago), without the .dll files, there isn't much that can be done. I looked into the lua code some, and made some minor changes, nothing significant, mostly just testing to see if I understood the T-45 code. Appreciate the work that is being done!!!

I was able to get it fixed, the 3rd time was a charm! That pesky file kept showing up despite running the repair. Appreciate the response!

This is not working for me. Adding the DCS folder to antivirus exceptions eliminated the virus error, I still get the unauthorized error.

Unfortunately the mod has been abandoned from what I've seen, for quite some time, and is really a disappointment. I am quite surprised that they or someone else hasn't picked up the mod and finished it. It adds so much to DCS and Naval Aviation. If I am away from DCS or an extended period of time, I always use the T-45C to get me back up to speed... and I'm an Naval Aviator. This aircraft plays a very important part in Naval Aviation training, so its fitting to bring this to DCS. Hopefully there will be some effort to finish it and bring this very important capability of Naval Aviation to DCS.

Once I engage the afterburner, it wont disengage, no matter if I put the throttle to idle, or any other settiing. Maybe this has something to do with the way the settings are. I dont have any issues with the Phantom.

The addition of the afterburner detent settings in Special Options is not functioning properly. - Mil power slider, can not click on the button and slide it to the desired setting, only way to move it is to click on the bar itself and move it at .1 increments - AB detent appears to function correctly, however pulling back to mil power or less does not disengage the afterburner... it remains engaged. - Afterburner and mil power sliders are not aligned as in the Phantom.

For those who are using Tobii Eye Tracker, if you disable the new launcher, that resolved the problem with my Tobii and now functions normally exactly like the previous DCS version.

I confirm as well the canopy toggle keybind only opens the canopy, you have to manually close it with the mouse.

Updated to the latest openbeta update, after loading the first single mission, jumped in F-14B parked hot, the wings automatically sweep forward, one at a time, not together... interesting. The handle position indicator showed full forward despite the handle being full aft, the wing position did not, but did move forward as the wings individually swept forward. Switched roles to a different location parked hot, wingsweep did the exact same. I'm thinking that the updated changed the wingsweep position when parked hot, not sure why it was moving the wings individually. No specific indication or warning, that behavior stopped and now the wingsweep remains full aft (parked) when selecting a role parked hot. The wingsweep handle still indicates full forward with the handle full aft. Have no idea why the wings swept forward, and no idea why it stopped, unfortunately did not have a recording that I could attach to this report. Asus ROG STRIX B550-F WIFI Motherboard AMD Ryzen 5 5600x CPU TEAMGROUP T-Force Delta 32GB DDR4 Samsung 980 Pro 1 TB M.2 SSD PowerColor RX 7600 XT 12GB RedDevil GPU Corsair RMx 750W 80+ Power Supply Windows 11 Pro 22H2 SAMSUNG Odyssey G7 Series 27-Inch Gaming Monitor

Ahh ha!.. that did it! I really dont understand it because Rwy 32 works with zero wind as does the other ILS signals I've tired on that map. Why Rwy 14 is different, don't have any idea. Thank you @Minsky appreciate working through this with me.

Interesting... I flew the F-16 and you will see the ILS is not active. However, when I switch to Rwy 32, it immediately goes active despite on Rwy 14 final. I did a repair to make sure my files are not corrupted. I tried 0 kts, 5 kts & 10 kts wind directly down the runway... the ILS is not active. If I modify the beacons.lua file to add ICLS channels, ICLS for Rwy 14 works perfectly. Makes no sense... Appreciate sending the .trk files, have no idea why it doesn't work on my system. 230703_NE_F16C_FCLP_001.trk

Thanks @Flappie for the feedback, I read about that in some of the other posts I've found, this does not have an affect from the testing I've done. Runway 32 always works, I can't get 14 to work at all, regardless of no wind, little wind or lots of wind. @Minsky replied to my original post that was accidentally deleted by me, had a 10knt wind down the runway and some screenshots showing it was working... my test screenshots are shown above under the same conditions, showing runway 14 not functioning. I'm stumped!