Habu_69

Can anyone explain why J-83 is Xed out in HUD? I am armed, IN ZONE, targeted, etc. On release the weapons guide and detonate properly.

At the risk of being labeled a dumb-ass I will admit my error with sincere contrition. I decided to double-check everything that could possibly be causing my targeting issues and discovered at last that the HOTAS button I had once assigned to TDC DEPRESS was in fact NOT assigned correctly. Now, I have been flying Hornet since its OB release and have no idea when that gremlin creeped into my controls assignments. All is well. Appreciate all the assistance and apologize for wasting everyone's time. Habu out.

I am not trying to be a butthead and I do not dispute that the targeting mechanics are working correctly, I am just curious why Tholozor's experience seems to be different from mine. When in WPDSG and I UNDESIGNATE, the TGP cursor snowplows; and in order to slew to a target I must SCS-right to ground stabilize (in SCENE track), then UNDESIGNATE and SCS-right again to update the weapon coordinates to new cursor position. Guess I will end this discussion since I have a procedure that works for me. Appreciate everyone's input.

Interesting, because using ATFLIR I find I must UNDESIGNATE cursor then SCS-right to stabilize cursor in SCENE track to enable slewing to target. Then UNDESIGNATE and SCS-right again to set new coordinates in weapon. After WPDSG, TDC DEPRESS does nothing.

Have to say: As much as I enjoy DCS and flying the Hornet, the fact that all these features remain to be implemented 4 years after OB release is disappointing.

Catching a wire and no jet damage is job 1. My goal is (Airboss) grade of at least 3.0 and groove time not exceeding 18 sec.

After several hours of repetitive procedures testing I devised the following mechanics for targeting JDAMs in TOO mode with the TGP and HSI WPDSG. Set up the jet for AG mode and activate TGP. Set up JDAMs normally and set TOO mode Set HSI to target WP. Press HSI WPDSG OSB. TGP display goes to WP SOI to TGP right DDI UNDESIGNATE TGP cursor Quickly SCS right to ground stabilize cursor in SCENE track. Slew SCENE track cursor to target SOI to TGP. UNDESIGNATE. SCS right sets target coordinates to JDAM TOO mode Pickle when IN ZONE. I realize this in a lot of button pushing, but it is the most efficient procedure I could find. YMMV. IMO being able to refine JDAM target acquisition near a WP is a very useful tool.

Devised a work-around. After slewing TGP cursor from waypoint to refined target, switch JDAMs to PP mode, then back to TOO and TGP designate. JDAM updates to new coordinates. This procedure does work, but difficult to believe it is expected behavior.

Your description of the TGP/JDAM behavior is accurate as far as it goes. My point is that if the operator attempts to refine the original WPDSG JDAM target coordinates by slewing the AUTO or SCENE mode cursor and re-designate with either SCS right or TDC DEPRESS, the JDAM target coordinates will not update from the original waypoint. Demonstrated in attached track. JDAM TOO No Update 2.trk

Lots of issues about JDAM TOO mode, but I have not found this one articulated. In both VVSLV and in WPDSG targeting mode there seems to be no mechanism to update or refine the target coordinates using the TGP. This makes locating and targeting an object in TOO extremely difficult. I also note that Chuck's Guide states that in VVSLV mode TDC DEPRESS should designate the ATFLIR target with a diamond symbol. I can only designate target with SCS RIGHT (to right TGP DDI). I am not a real Hornet pilot, but I fly one on my PC. So I do not know whether these are features or bugs. JDAM TOO No Update.trk

OK, but does activating the button have any effect on other platform's ability to detect your aircraft? True EMCON would seem to be a complex coding task.

NVD_HDR.fx fix no longer works in 2.7.11.

Are target points not just waypoints?

At both Akrotiri and Incerlik in Hornet with correct tower freqs I can get no voice comms from either tower. Comms with ground crew function correctly and the ATC comm menu advances from Request start-up, then request taxi, etc, but I hear no voice comms. No problems on other maps, Caucasus for example. Test Syria.miz

+1. Frequent Access Violation errors. Worse in MP.

Yes minor, but I found it annoying nonetheless. YMMV Guess it depends on the definition of "gold standard". My definition is best available at a given point in time, flawed though it may be.

The 2 shell halves of the Cougar stick attach to the base shaft with 1 interior screw and 1 long screw through the shell surface. See attached photo at 5. When the screws are tightened the shaft still does not fit snugly against the stick shell halves. Fix is to fashion a tiny shim, with a hole for the screw, and place it between the shaft screw flange and the shell. Voila! snug fit and no wobble. I used an aluminum beverage can for the shim material. Requires some patience and small fingers. Be careful of the fragile wires.

Some historic perspective from a simwar veteran. I bought one of the first Cougar HOTAS sets as an upgrade from the previous "gold standard" TM Pro F-22 and TQS. Believe me, AT THE TIME, Cougar was indeed the gold standard and held that distinction for more than 10 years. Its Foxy software made it the most versatile HOTAS by far. Yes, the gimbals proved to be its Achilles heel and the stick developed excessive center-play over time. Moreover the switch solder connections would occasionally fail and some PCB's would fail with time. I found a fix to eliminate the center-wobble and became adept at trouble-shooting and repairing the solder connections. I also replaced the gimbals with a force-sensing solution. The Warthog throttle has replaced my Cougar throttle, but I am still using that old original Cougar joystick to this day. Back in the day Cougar-envy was a real thing.

An alternative, which I prefer, is the Open Mod Manager. Both work well, tho.

I aim the VV a little high and right of the green light, guessing about where the island bridge would be, until I have a clear view of the flight deck. Regarding the needles and IFLOLS, the closer you approach, the more subtle your control corrections.

Tx for info.

I have an old F-22 Pro HOTAS with the Stickworks digital upgrade. Any way to get it working with Windows 10/11??

Unfortunately many of the older Moose YouTube videos, including setup procedures, are obsolete; and the current developers have no control over them. Recommend you visit the Moose Discord where plenty of current guidance and help reside.

Lots of methods to do this in Moose. One way is to use event.dead method to detect when the CAP meets its demise, which initiates a timer to trigger a spawn function (NewBandit) after an expired time (1200 seconds). timer.scheduleFunction( NewBandit, {}, timer.getTime() + 1200 ) or adapt a SpawnScheduled like this Red_CAP = SPAWN:New( "Red_CAP" ) :InitLimit( 2, 1 ) -- Spawns two 2-ship groups, only 1 group alive at a time :SpawnScheduled( 1200, 0 ) -- Spawns subsequent group(s) after 1200 seconds

This tool is the bomb now and just getting better.