450Devil

Further to the above, when adding or editing waypoints using the Jester wheel, as well as the LAT / LONG, it would be helpful if we could also give the new / edited waypoint a name - such as F-IN or HOLD or HB or TGT as appropriate.

I have set up a single player mission using the waypoint settings F-IN, HOLD, CAP1, CAP2, IP, TGT, F-OUT, HB and ALT. Jester's calls as I approached F-IN, CAP1 and CAP2, IP, TGT and F-OUT are very helpful. It would also be helpful if Jester gave 10 miles to, 5 miles to and at HOLD calls similar to the CAP calls and for Jester to ask how long we are going to HOLD. A five minute alert to HOLD expiring would also be very helpful. Also, when on a bomb run - particular under Direct or Dive Toss - it would be very helpful for Jester to call speed and altitude prior to bomb release. Just some observations and wishes.

Further to the above. When using Stored Heading it is taking about 3 minutes 45 seconds to achieve alignment. The HB manual states that this should only take 2 minutes 15 seconds. Perhaps this second circle is increasing the time it takes to align the INS using Stored Heading.

File uploads fixed. Here is the track and screenshot files. F-4 INS Alignment.trk

Yes. I used autostart. I would love to provide a short track (I have one that is 2,030 KB - and I do not see any way of reducing the size of the file as it only goes from when I spawn in to the jet to when the INS circles appear) but the limit on file size is only 147.23 KB. I used to be able to up load larger files but, for some reason, the forum limit is now set (for me at least) at file sizes less than 147.23 KB. If you can give me an email address I will happy send it as an attachment to an email. As I stated above I also have a screenshot but its size id 1.03 MB.

It appears that the multiple circle INS alignment bug was not resolved with the latest update. I would attach a screenshot and a short track file but both are larger than the piddling size (147.23 kB) allowed in this forum. For information my screenshot shows a orange W circle and a purplish E circle.

Confirmed. The fuel quantity goes down but there is no animation when in external view. It is working for the F-4 so the issue may be confined to the F-18.

Noted Polychop's comments in the Discord channel regarding the issues with the KW after the latest DCS update. Tried to check things out and the first bug I found is that the Auto Start Procedure (LWIN + Home) is no longer working.

If what I think you are trying to do, then the answer is Yes. You can set up Modifiers and then add the Axis into the appropriate setup control. For example, if I were to set up the Joystick Switch 4 on my Sidewinder Wheel as a Modifier. I could then added that Modifier plus a rotary control on my Throttle for zooming my view. To zoom in and out I would first switch Joystick Switch 4 on and then rotate the rotary control. In your case with 2 rotary controls on your X-56 you could assign six different switches on your other controllers as Modifiers and then assign the rotary controls as desired. Alternatively, you could to set keyboard keys (for example, LAlt, A, Del .......) as Modifiers (most are already setup as Modifiers in the Controls Setup); assign the relevant rotary dial. To operate this alternative setup you would need to hold the relevant key down when operating your rotary dials. There are YouTube vids on creating Modifiers in DCS - here is one

For @WinOrLose - if you use Voice Attack you can set up voice commands to input numbers and letters. While I don't personally use it to input numbers / letters for the Jester Wheel (at this time), I do use it to select items in the Comms Menu. Using VA would be a way to get around taking off your headset to input coords. Just a suggestion.

Check the bin-mt folder in DCS World (or DCS Openbeta if you are still using that) and see if it contains the file headtracker.dll. If not, then look in the bin folder which should have a copy of headtracker.dll. Copy/paste headtracker.dll from bin folder to bin-mt folder. Restart DCS (making sure the Launcher is off in the Settings) and Tobii should then work OK.

Sneaky, sneaky HB. I just tested the AN/ALR-46 against both the SA-5 and SA-10 "Tin Shield" radars. Now they both display as "S" on the RWR (at 150 nm range) with SEARCH button activated and UNKNOWN flashing - activating the UNKNOWN button superimposes a "U" on the "S". Also tested the Gepard - it now does not display on the RWR. Lots more testing to do. Why no change notes in the latest Update information?

Thanks @sleighzy. Problem fixed. In the Tobii Discord @SamStarion had highlighted the problem and advised the fix was to ensure the headtracker.dll was in the DCS bin-mt folder. I copied the headtracker.dll file from my DCS World version and now all is OK with my Tobii Eye Track 5. Now to make a note to self for future updates because I have little confidence that ED will not stuff it up when the next update comes out. As an insurance I will continue to keep my DCS World version one update behind so that I can compare it to the latest version after future updates.

After installing the latest update my Tobii Eye Track 5 no longer works. I have the Launcher turned off (given that it was the Launcher that was causing the Tobii to not work after the previous update). (I have tried turning the Launcher on but still no Tobii) My Tobii does still work with the previous DCS version. For the last few updates I have been updating my DCS Openbeta version and keeping my DCS World version at the previous version - just in case. Looking at the logs of the two versions - the log from my previous version has the line 2024-10-01 05:12:20.622 INFO INPUT (Main): created [HeadTracker]. The log from the updated version does not have this activity in it. I have checked that the Tobii software (Tobii Game Hub) is looking at the correct DCS folders and executables. When I start DCS the Tobii Game Hub recognizes that DCS is running but then shortly after gives a "Unable to track game window" warning. Any help greatly appreciated.

Another option is to use Voice Attack. I have VA commands (using the Context Actions) for locking targets, dropping locked targets, caging and uncaging etc. Instead of having to use key binds it is much easier to use voice commands. Attached is my current F-4R-45MC Voice Attack Profile and its html command list. F-4E-45MC-Profile.vap F-4E-45MC-Profile.html

@Northstar98. Thank you. On balance I have to agree with you. The "Tin Shield" displaying as "S" would be much better that the current situation and it would be consistent with the other two DCS SA-10 search radars - the SA-10 S-300 "Clam Shell" and the SA-10 S-300 "Big Bird" - which both display as "S" on the RWR. The big discrepancy is the "Tin Shield" currently displays an aircraft symbol whenever the AN/ALR-46 detects it - thus making tactical decisions much more difficult as the pilot / player may believe they are facing an airborne threat when in fact they are facing a SAM threat. I also agree with the point you make about the use of the "Tin Shield" IRL.

After about a week of researching the AN/ALR-46 and analyzing the various (Russian) radar search and track radar frequencies (using the .lua files and running trial missions flying towards each radar at 450 KIAS and at altitude 15,000 MSL) I have the following observation / queries: 1. From information on the internet the AN/ALR-46 was fitted with a crystal designed to detect radar emissions between 2 Ghz and 18 Ghz. And that appears to be how the AN/ALR-46 is modelled in HB's F-4E-45MC. 2. The AN/ALR-46 should not (and does not) detect most DCS EW radars as their emissions are generally lower than 2 Ghz (for example, the EWR 1L13 emits in a range 0.18 to 0.22 Ghz and the EWR 55G6 in a range from 0.03 to 0.3 Ghz). 3. The AN/ALR-46 should not (and does not) detect the SPAA ZSU-23 Shilka "Gun Dish" as it emits in a range 20 to 30 Ghz. Note: the F-4 RWR Keyboard card does contain a symbol for the "Gun Dish" - probably a mistake. 4. The AN/ALR-46 does detect the Generic EW Tower, although if this radar uses the "AN/FPS-117 Radar Dome.lua" then it should not detect this radar as the frequency given in the .lua file is 1.215 to 1.4 Ghz. 5. The RWR symbol displayed for the SA-5 S-200 ST-68U "Tin Shield" is which is the symbol for a number of aircraft. Why does the RWR not display a "5"? 6. The RWR symbol displayed for the SA-10 S-300 "Tin Shield" is which is the symbol for a number of aircraft. Why does the RWR not display a "10"? 7. The RWR displays alternating "A" and when it detect a SPAA "Gepard" even though the F-4 RWR Kneeboard card only indicates an "A" should be displayed. 8. The LOW ALTITUDE button does not appear to add any additional capability to the current F-4 RWR. 9. Flying with both the SEARCH and UNKNOWN buttons activated appears to be the best procedure for detecting radars within the 2 to 18 Ghz range of the AN/ALR-46. Perhaps this should be noted in the standard procedures section of the manual? As I have stated before in other threads - this is a great module (and I fully appreciate that it is still in early access and will receive many improvements over time). Well done HB and I offer the above simply as information that may assist with the development of this excellent module.

Thanks for the reply. Another improvement would be for Jester's tone to be less "panicky". At the moment he sounds more "Hollywood" and less like an experienced, trained WSO.

I love the F-4 and, in my opinion, the F-4's Jester seems to be an improvement on the F-14's Jester - so, well done Heatblur. The Good - Jester is very helpful with Startup / Shutdown procedures, takeoff and landing calls and, particularly, when doing air to air refueling. The Bad - Jester often calls bogeys that are not there. He also calls bogeys on friendlies even though he has (very) recently identified them as friendlies (this is a particular nuisance/distraction when flying in a loose formation - combat spread with friendlies). Jester's assessment of a bogey's altitude (when it is there) is very hit or miss, often missing the altitude by thousands of feet. The Ugly - there appears to be no way to refine/limit/define what Jester calls out - for example, limiting his bogey calls to aircraft that come within 25 miles or some other limiters / limiting his calls to confirmed bandits / limiting his Mud/Dirt calls to only enemy radars - in a known operational area, the WSO would have intelligence regarding the location of friendly radars and be able to geo-locate them is relation to the flight plan. Yesterday, I participated in a 20 player mission. At time the volume of Jester calls were overwhelming as he was calling out repeat contacts (particularly friendlies in the formation whenever the formation altered course), non existent contacts and missile launches from friendly SAMS. Overall, Jester is a plus that adds to the F-4 module. However, he does need to become more discriminatory and selective in what he calls out. Just my observations and thoughts and in no way intended to diminish or criticize the terrific work Heatblur has put into developing the F-4 module.

I have TE5 and it is not laggy. I was in a MP server last night with about 20 other players for a Liberation campaign on the Marianas map and everything was OK (Tobii wise). Do you have a track?

Just tried the SA-19 and found that there is no radar contacts showing on the screen even though I set up three aircraft flying orbits at 2000 feet MSL within 15 miles. Not much fun having a player drivable SAM that cannot be used as designed. From the posts above it seems that this bug (affecting all the player drivable SAMs) has been known for some time - wonder when it will get fixed?

Many thanks Zabuzard for the explanation above.

I have found this thread fascinating to read. From some testing I have done it appears that, when on the ground, the pilot's joystick moves to a position that is fully forward when the Stabilator is trimmed to 1.8 units Down and moves to a position that is fully back when the Stabilator is trimmed to Neutral. Attached is a rough drawing that I made showing Trim Indicator - Stick Position - Stabilator Physical Alignment. The travel of the stick when trimming the aircraft appears to be limited to fully back (to the rear) when trimmed neutral and fully forward (to the front) when trimmed 1.8 units Down. Passed these limits there is no physical travel of the stick. Is this how the F-4's pitch trim is supposed to work in real life?

You may need to zoom in a little. The rings are not a pronounced as they used to be but they are still visible.

Just started Mission 1. On the ingress to Indian Springs (in company with my Flight Lead) Jester started giving bandit calls. The calls appeared to be on my Flight Lead. The calls continued through the descent and landing checks. The calls commenced from where I selected to ignore the USAAF F-4 that saddles up on the starboard side of my flight when we are flying towards Indian Springs.