escaner

Instead of a key combo, configure in DCS DirectX joystick events for Left Engine Cutoff and Right Engine Cutoff and in the TARGET script activate the event without the PULSE modifier. This way the DX event will stay on while the throttle is in CUTOFF and will turn off when you move the lever to IDLE. E.g.: In TARGET: MapKey(&Throttle, IDLERON, DX29); MapKey(&Throttle, IDLELON, DX30); In DCS: Right Engine Cutoff: JOY_BTN29 Left Engine Cutoff: JOY_BTN30

I dont know about vr, but symbology brightness is much lower in 2d, which makes the mfcd much harder to read and it is not possible to increase to previous levels

Please, read my post. It is not about the FOV function as all those threads. I am talking about the switch between CCD and IR modes in the TGP.

I have found this weird behavior of the TGP (Litening): Use WPDSG to select waypoint as target. Activate the TGP and move it. Use SCS right 3 times to cycle to Area, Point and back to Inertial mode. When going back to inertial, the TGP is moved to the target designated point. Note that if TDC is pressed before moving the TGP away from the WPDSG point and then cycled with SCS to Area, Point and Inertial, the TGP does not move away from current position (last cycle in the track was done using this method). Track attached b-tgp-moves-to-tgt.trk

With Maverick selected and Litening pod as SOI, it is not possible to use RAID/FOV long press to switch between IR and CCD TGP modes. As I understand, it is correct that RAID/FOV short affects the FOV of the Maverick missile instead of the TGP, but it looks like the long press is also interpreted as a Maverick FOV switch even though there is not such function as RAID/FOV long on the Maverick. tgp-no-ir-ccd-switch.trk

How to reproduce: F-18 with Maverick F (IR), activate it (A/G, select weapon twice for Mav sensor, seat as SOI, uncage) and use manual targeting: depress TDC to move seeker and put it over a target for a moment (one or two seconds) without releasing TDC. The Maverick seeker is moved away from the target as if it was repelled. It is important not no release the TDC for this problem to appear. Track attached. bug-mav-hover-over-tgt.trk

Is this correct? In other modules, eg A-10C it can be done

I also do this during the day, but unfortunately I am unable to dim the map and keep bright symbols at night and dusk

Hi Jel, thanks for your reply. Yes, eventually I applied for a 2 week trial of the module and my friend could use the carrier. What was quite frustrating and stupid is that he could not use slots in the Stennis carrier either (he appeared in flight) while I could with no problem.

Hello @Lord Vader, Thanks for your help I didn't know this does not work above M0.9. Another case where I have found this is when selecting as HOME an "undefined" waypoint by mistake. Same example, using WP4, which is not in the route and defaults to N0º E0º. Once the system enters the advisory FPAS status, I am unable to change it to the correct home waypoint. Track attached. If this behavior is also correct, there must be a way to select another home waypoint, right? Thanks! fpas-locked2.trk

In many cases, when selecting an FPAS home waypoint, the system displays the FPAS advisory and removes the ability of changing the home waypoint. This probably happens more frequently when the CLIMB function is selected, but it is not always required. According to the manuals, this should happen only in case of a malfunction in the system that does not allow the FPAS system to calculate home fuel caution anymore, which is not the case in this example: track attached. fpas-locked.trk

For Hold functions, just map either DirectX button events or simple keys, without control, shift, etc Enviado desde mi M2012K11AC mediante Tapatalk

I am serving a MP mission with SC. I don't have the module, so I choose a non SC slot. My friend has the SC module and he can choose a SC slot, but instead of appearing on the deck, he starts in flight. I have checked the mission and his slot is set to start cold from the supercarrier deck (it appears attached to catapult #1 in mission editor). There are more aircraft, both Client and AI in this carrier. This is the mission we are trying (I modified it adding a non SC slot for me): https://www.digitalcombatsimulator.com/en/files/3325580/ Any help would be welcome. Thanks!

It seems to me that now it needs a lot more thrust for taxiing Enviado desde mi M2012K11AC mediante Tapatalk

Same problem here. Actually the Tornados do not even fly formation anymore, each one flies and circles on its own. I am flying again the whole Campaign before going for the Nevada one that I purchased several years ago and I am finding many problems like this one. Planes that get stuck and do not continue, messages that appear late (eg startup messages appearing when coming back), and so on. This campaign needs an overhaul (and ED to fix all those new AI bugs they keep introducing).

What you say is true when the helicopter (or any other target aircraft) is flying below your own Hornet due to the ground filter in the doppler radar. That filter is disabled when the target is above and the problem should disappear, yet in DCS is still impossible to detect helicopters flying above. And this is true for any doppler radar, not only the F-18's. I have not found this problem detecting helicopters in any other module.

Same problem here. The only workaround I found is to steal the Hellfire from George, then I get the symbology, it locks in LOBL mode and I can fire it myself.

Same problem here, working as CPG with a friend PLT. Sometimes the Hellfire does not detect the laser and the square will stay small. And when it locks, the missiles consistently go to the exact same spot 20-30m away from the lased target. Looking at the Hellfire from external view, in the terminal phase it moves all around the place. Even more problems: I introduce points, routes and make direct, select acquisition and my pilot does not see anything of that, he has to do everything by himself. Once we landed and he saw my TADS drifting away from the place I was aiming it. It is as if the syncing is constantly lost. Probably everything is related. I have tried to leave the aircraft and join back, but the Hellfires still consistently miss. We have tried this both serving myself a mission and using a random public server, it never worked.

As we know, there is a delay when launching an air to air missile (in particular the radar western variants) while the aircraft feeds the missile with target data and gets ready for the launch. It is implemented in most DCS modules: F-16, F-15C, F-14, etc.; but not on the F/A-18. For me, not having this delay reduces a bit the immersion of the module. Will it be implemented at some point? E.g., here is a part from The Fighter Pilot Podcast where Mongo describes that "it takes about a second to leave the airplane" when launching his AIM-7. Thank you

Also please note that this problem is not exclusive of the exp modes. It happens in all a/g that I have tried: standard ground mapping, freeze, even in sea mode... Enviado desde mi Redmi Note 4 mediante Tapatalk

CBU-97 and -105 are basically the same bomb, just the -105 is wind corrected but it cannot be used in CCIP mode.

I wonder how you can visually id a locked contact in the Hornet with the bugged launch steering dot over it hiding it.

This happened to me yesterday too. I remember this bug from the legacy A-10C: a pitch down was felt after passing under a bridge or under another aircraft. Then when landing at the threshold the pitch did reset, so a strong pitch up was felt there. It was fixed years ago. I had no time to check whether it is the same bug, but it definitely felt the same. A few threads from that time:

Ignore the ATC, it will not give you the QNH altimeter setting but the pressure at the field elevation (QFE). For QNH, just set the altimeter so it reads the correct field elevation or use Alt+B to display the briefing and there you can see the QNH setting at the end.

How was that video recorded? Is it a superposition of the aircraft recording the HMD display over a gopro video mounted on the helmet? There the symbology on the HMD is very easily made out from the one on the HUD (this one is not even in focus and cannot be read at all). The problem in the sim is that it is very difficult to distinguish between the symbology in the HUD and the one in the helmet, so for example when I get something like in this video, with 2 TD boxes one pointing up and the other one that seems to be pointing down because it is drawn on the lower of the HUD, it is painfully confusing. And in dogfights this happens all the time. I am sure that we are missing something here. Probably in the real life is easy to differentiate which symbology is from the HUD and which from the HMD and everything is more intuitive Perhaps because of the missing arrow in the HMD that Dorian says. Perhaps because the HMD is only in one eye or it is just more apparent. But I am sure that it cannot be as confusing as what we have now in DCS or they would have told the HMD developer to modify it.