Tshark

Not working for me as well.

Quick question. What Nvidia driver is needed to take advantage of preset "K"? I am currently running a 4090 on driver 566.36.

Here is a quick YouTube on HF8 repair. Hopefully the HF8Pro does not share these same shortcomings. https://youtu.be/4_jA88VdQhE?si=nKC2M7SGPHSiBgCS

Hopefully they fixed the two biggest flaws in design that cause 80% of the HF8 failures. Larger gauge wire that doesn't break at the pad fold/motor solder points and replacing the IC motor controller chips with chips that have a higher power rating.

Since the March update, my mouse button 6 no longer works as an "ESC" keypress in VR. My mouse driver has button 6 mapped as an "ESC" keypress. I checked the mouse button functionality on a keyboard test and it registers the button press as "ESC". The keyboard "ESC" key works in DCS VR. Looking into the UI layer mapping there is no mouse button 6 shown (although I never had to map that button in DCS). This issue only occurs in VR. When I start DCS in 2D the mouse button "ESC" works. I fly VR, so having a mouse button "ESC" is very handy. Any suggestions?

For those in the area of Palm Springs CA, the Palm Spring Air Museum is holding a Huey event this Saturday the 19th of April. The event allows you to sit in the pilots seat of the Huey, have your picture taken, and they have a Huey pilot there to answer questions. I have been to these "Open Cockpit" events several times and use the DCS cold start procedures to "touch" start the aircraft. It really brings DCS to life. https://palmspringsairmuseum.org/programs/open-cockpit-saturdays-uh-1-huey/

No offense taken, just wanted to clarify that the problem was not experienced by two noob players who can't RTFM. For the six of us, bombing in the F-4 with a human WSO does appear useless. Desync issues are not uncommon in DCS. It is suspected as there are other issues with two human crews of the F-4. For instance, if you start a multiplayer mission with the mission paused until both slots are filled in a F-4 you will not have any counter-measures when the mission is un-paused. Start the same session with a human pilot, mission un-paused, and have the human WSO join (displacing Jester) then you have counter-measures. We have submitted the requested track files and WSO descriptions. It does not appear the track files have been downloaded even once and we are being told "you are doing something wrong" with no further clarification. You can see how that can cause frustration. I do sincerely hope that it is user error, then it will be something we can correct immediately and not wait for a patch. How can we help further?

It may very well be our error, but it is not just the two of us. There are six of us who all have the same issue. The six of us comprise of a nuclear weld quality inspector, major airline pilot instructor, retired collision re-constructionist, and three that are in IT/programming, all with 3+ years of experience playing DCS almost daily. We are use to learning and troubleshooting technical matters. Manuals on technical procedures are standard fare for us. We have spent quite a few hours trying to get bombs on target with a human WSO with no success. If the Phantom were not such an iconic aircraft we would have given up on HB's version of it quite a while back. I do hope someone takes the time to look at our track files and delve into this issue so that a clarification can be added to the HB F-4 manual for others as well as us.

So, no suggestions on what we might do differently to get bombs on target? I wonder if WSO de-sync or lag could account for the difference in accuracy compared to Jester?

There is some confusion within the manual. In DT for instance there are several places in the manual that say no preparation is needed by the WSO: http://f4.manuals.heatblur.se/stores/air_to_ground/bombs/employment/overview.html Yet, in this kneeboard a weapon coefficient is needed: http://f4.manuals.heatblur.se/procedures/bombs/bombs_dive_toss_and_laydown.html So, do we use the bombing calculator, inputting speed, release alt, etc., to get a coefficient? Could you clarify please.

Here is the second track file. This with Mk82s. Phantom Bomb Test-20250220-175158.trk

Still having problems. We made up a kneeboard that is directly from the manual. Four drops with Mk82s and Rockeyes all Dive Toss over two days and only one drop on target. Here are track files from the pilots PC. This first is with Mk20. Any help would be appreciated. server-20250222-172129.trk

Yesterday, I updated from an i9-10900K to the AMD 9800X3D. I have a 4090 GPU and use a Pimax Crystal. My default DCS benchmark is the F/A-18 Supercarrier Cold start mission in the Persian Gulf. With my Pimax set at 90hz, DCS Fps cap of 60, and using Mbucchia dynamic foveated rendering I was getting 42-43 fps (using the DCS frame counter). After upgrading to the 9800X3D, with no other changes, my Fps went to rock solid 60 fps. I changed the Pimax to 72hz and took off the DCS cap. I now am at 72fps with an occasional dip to 71fps. Definitely a game changer for me and sooo smooth. Hope this helps

The group I fly with have been trying to get ground ordinance on target with human WSOs for months without success. It does not matter the type of ordinance or bombing method. If we use Jester then the bombs work as expected, no matter the ordinance or bombing method. We have even tried to let Jester make the WSO settings, then jump into the back seat to see what he did. Unfortunately, the settings zero themselves out as soon as you occupy the rear seat. The only thing we can figure is that there is such a de-sync between the human players that ground pounding is next to useless. We are now avoiding flying the F-4E, which is really a shame. Is ANYBODY having success bombing with human WSOs?

The above repair procedure did not entirely repair my pad. It did stop all motors from coming on full power along with a bright white LED. Now only four motors and the LED are working correctly. It appears the ATMEL chip is still malfunctioning, but at least there is partial usability restored. Next Level Racing support did reach back out to me and we were able to come to a satisfactory replacement solution. Hopefully, NLR will be able to fix this long standing issue or offer a standardized repair solution.