SloppyDog

Experienced the same yesterday. Trying to input new waypoint "9.", game crashed to desktop.

It doesn't show the animation anymore neither show them with the visors down. But if you press Shift+N it will show the effect of visor down, or if duly equipped, will turn on the NVGs.

I don't know if it is just me, but I find the suspension struts too frail. You cannot land with speed above 100 knots. It will bounce and break the struts (usually the left one), Watching some videos of the Thunderbolt landing in WWII, it seems to be very sturdy, they really let it fall to the ground without much trouble. Edit: I may be confusing it with the Corsair. Saw some videos of Corsairs landing on a island runway, they've just cut the throttle and let it fall. On the other hand, the training videos on the -47 show them landing very lightly on the runway.

Thanks. I believe it will not work as I envisioned. I'll try to either induce a failure or make the NAV mode knob to be changed to INS only.

Hello all! I'm making a mission for the glorious F-15E, and I want to emulate a GPS signal spoofing by the red forces. The general idea is once the blue force aircraft enter a zone, i.e., Area 51, the GPS signal inside zone is turned off. This way the pilots will have to rely on manual bombing or update their INS system prior to the bombing run. I know I can set in the MIssion options the unsrestricted SATNAV to off. My question is if I could do this in one zone only.

The only WWII bird I fly. Brought me home so many times. I occasionally fly the Mosquito, but while ED does not give us a AI co-pilot, that bird will be in the Hangar.

This is strange, these kind of problems were very common some patches ago. Things that might be interesting to investigate: 1) Are you running DCS under the latest patch? 2) Can be a problem of duplicated controls; 3) What are your settings under the Special Tab? In CLYCLIC TRIMMER MODE I use INSTANT TRIM (FFB FRIENDLY). For some time I used the "Central Trimmer Mode" but couldn't get used to it. Anyway, if you don't have a Force Feedback joystick, then you need to use one of these modes. What may be happening is that you are using the "Joystick without Springs and FFB" mode. In this mode trim does not hold at a position, because it follows the position of the real life joystick. The software is assuming that you are using a FFB joystick, that holds its physical position once TRIM is pressed and released. That may be the origin of the oscillations, because you assume you are trimmed, engages the HOLD modes, but once releasing the joystick, it gets back to its center position and then the SAS tries to compensate for the sudden movement, causing the oscillations. Anyway, I'm assuming a lot here, that you are not really in trim, and using the "wrong", i.e. inadequate, CYCLIC mode in the Special Mode. Please, bear with me, because I'm trying to help you find a solution to the problem. The things you described are not a common complaint these days, HOLD modes seem to be working fine.

nullOn the Patch Notes for the February 22nd patch (DCS version 2.9.3.51704), there is the note highlighted in the picture. It reads: - Control hover added Ah-64 taxi improved. I got confused about it. My interpretation that it should be two topics, not only one: one for control hover (not clear it is for the AH-64 or the AI helos) and other for the improved AH-64 taxi. And of course, at least one should be under the AH-64 section of the notes. Maybe someone from ED can help clarify it. Thanks.

The Syria map is running much better now. Before today's patch, the Instant Action Apache missions in the map were impossible to play. Now, even with textures in high, SSAO, SSLR, SSS, Secondary Shadows and clouds in high, everything runs smoothly, no stutters, few fps drops, running nicely at a fixed FPS. Great work, and thank you for the update.

Well, this is an interesting take on it. I had thought about it and is nice to see other people seeing this as well. As much as a legend the F-4E is, and deservedly so, it is a step back from the "teen series" of fighter aircraft. I believe Heatblur will deliver a great product, faithful to the last screw and rivet, but that may be a problem, because as legendary the F-4 is, it is not without its 3rd gen idiosyncrasies, and many people will be surprised by that.

About a sub menu that calculates this things, well, I don't know abou these in real life. Maybe someone with more knowledge can help you out. From what I've seen in interviews and podcasts, the 'E' is a transition from the analog world to the digital world, and many calculations like fuel consumption and optimal cruise speeds were made manually, unless such menus were added later on. Anyway, from my experience, at high altitude, inbound or outbound the target area, I usually cruise about 400 kts. I saw a former pilot saying that is where the Mudhen likes to be. So, I use it, and it gives me a fairly decent fuel consumption: not many endurance, but a good range, since the E goes fast, even loaded to bear. For CAS at high altitude, then I usually goes at 350 kts in order to maintain the pod unmasked up to the last moment. And ingress, attack, and egress, at low altitude, using TFR, I go usually at 550 knots. This gives me about one hour over enemy territory, more than enough to get in, make the run, and get out. Of course, you better be prepared to find a tanker or divert after that. If you need to be a long time over enemy territory flying low, then I go 450 knots. It gives me much more time, and at Pre-IP, I speed up to 550 kts for the attack run. And by long time I mean 90 minutes. Again, after that, you better find a tanker. Well, that sums it up: and that's why I love the Mudhen. You can be one hour over enemy territory, carrying a full complement of Mk-82's and two fuel tanks, flying very low and very fast, with the engines at 85-90% all the time. The only thing I miss is a auto-throttle of some sorts to help out. TL; DR: High altitude: 400 kts High altitude CAS; 350 kts Low time over enemy territory: 550 kts High time over enemy territory: 450 kts

I believe that there isn't a way to show all the routes, since the B and C routes are created with list points, not proper Waypoints in the ME. So, the only way to check them out is by looking at the TSD.

Did the AI ground unit targeting affected JTACs as well? I'm finding them unrestricted in distance and LOS, also they can see and market targets at night, something that was notpossible before.

I was making a mission and setting up a group of JTACs and I noticed something: they are no longer bound by distance or Line-Of-Sight restrictions. Before it was very restricting since the distance could not be longer than 3 nm, and the JTAC had to have a clear line of sight to the assigned target. If not, a warning in orange would appear on the FAC-Engage Group window. Now, they can mark targets even from behind trees. Also, JTACs now can see in the dark. Set up a mission with them marking targets at night and now they can see the target and mark it as well. Not that I'm complaining, I'm finding it very interesting and freeing, allowing for much more creative mission creation. Can anyone else confirm this behavior? Thanks.

Pictures added again... Don't know why they didn't load the first time.

Here's a compilation: There's also one for the AIM-120 missile:

Check out this thread, if you want more info: Bu basically, you add navpoints/offset points with the names 1.B, 2.B. 3.B, 1.C, 2.C and so on or 1.01B, 2.01B and so on for offset points. Also, you can do the way Casmo did with List points. And you can also pre-plan JDAMs target points this way (pag.499 on the manual). It is an amazing tool being able to do it all through the mission editor, gives much possibilities for mission creation.

Oh, cool! That's interesting and makes more sense. Sometimes, it's the years of Jane's talking.

I believe that wouldn't be the function of the FCR, as radars usually are tuned to detect their own emissions. We've already have the ASE that gives out radar emitters general bearing. The RFI would allow for a better bearing estimation and the system would/can slave the sensors to the general area of the radar emission, including the FCR: Official Lockheed-Martin brochure says that the RFI can detect threats beyond the normal Apache's sensor detection ranges, but don't say how much beyond it is. https://www.lockheedmartin.com/content/dam/lockheed-martin/rms/documents/electronic-warfare/APR-48B-brochure.pdf

People here in this forum are discussing the Techniques, Tactics and Procedures, which are all very interesting and I'm learning a lot from reading it. However, from the physics/engineering side of things, the FCR has a short range due to the nature of the radar waves. The name of the game here is called Resolution. Basically, is the ability of the radar to detect something and differentiate it from the background or from other things. The higher the wavelength, the better the resolution, however, these higher frequency waves are absorbed by the atmosphere (mainly water droplets) and lose strength over large distances. A millimeter wave radar can detect and identify things in a millimeter scale (or 0,0394 inches, or 3/64" for those who not speak metric), but in turn it loses in detection range. In practical terms, what the FCR radar does is to send a very narrow and focused radar beam, and as soon as it is swiping over the targets it is also receiving back the signal reflections. The resolution is so good that the radar knows what is the background and what is a truck, or if there are two trucks parked next each other. Also, different materials reflect radar waves in different ways, so a truck chassis will reflect the radar waves, and the rubber tires will not (as much). Or a tank will have a high reflection all around, including its tracks. Then these signals are processed by the computers to detect, identify and classify the targets. The best analogy that I can think of is putting objects in front of a lamp and observing its shadow. You know it resembles a truck or a tank, you just don't know what model it is, so you would classify it as a wheeled or a tracked vehicle. Also it can't tel if is a T-72 or a Abrams tank (if it does IRL, then must be hush-hush top secret). The real magic happens tough when looking at air defenses, where it can differentiate between a Shilka or a SA-6, for instance, just based on its format. Well, this is a very basic and simple explanation, because when talking about radars, things get really complicated really fast.

Well, it's coming in the next patch: From the Razbam Discord: Official Changelog for the December 2023 OB release: **DCS: F-15E Suite 4+ by RAZBAM Simulations. Version 1.8.1.219** Added: AGM-154A JSOW Added: Smart Weapons MC Synch Added: Full featured IFF transponder Added: Radar IFF Interrogator Modes 1/2/3/4 Added: Radar IFF AUTO ID Added: Radar IFF AAI slave mode Added: IFF Latched status displayed with cursor highlight Added: IFF Interrogation possible in RBM Added: Can stop AAI/EID with another long press Added: IFF Mode 2 code configurable in Mission Editor Added: TWS > STT retains IFF and NCTR tags Added: Other seat scratchpad display Added: Dumb bomb & CBU lofting Added: A/G RDR Cursor BullsEye coordinates Updated: All bombs have now a 30ms minimum release interval Updated: A/G RDR quickstep relatches to PB17 first Updated: BE points now allowed in A/G RDR PB17 Improved: NCTR behavior Improved: Radar IFF correlation mechanism Improved: BOT aiming significantly more accurate Improved: Low drag bombs accuracy Improved: CBU accuracy Improved: Bomb calculator wind compensation Improved: Station position accounted for in CDIP/AUTO Improved: RBM gain logic Fixed: GBU-31V3 x 2 load not showing in CFTs when selected Fixed: CBU height/time release modes not being applied Fixed: ASL issues Fixed: RCD saving all mimpap sizes Fixed: Frozen HRM patch images being lost when taking control Fixed: Jumping cursor coords & symbols in RB Fixed: A/G RDR behavior of cursor latched to an offscreen SP Fixed: UFC Wind direction TO instead of FROM Fixed: HUD laser cue not synchronised Fixed: JDAM Terminal Angle is reversed Fixed: JDAM laser code not used Fixed: TGP ALAS mode fires the laser when it is not armed

One thing that always gets me is the Master Mode I am at the moment: the AP works well in AG, NAV and INST master modes, although are not perfect in holding altitude. In AA master mode it does not follow waypoints nor hold altitude, and that is by design.

You have to bind different controls for the Pilot and the WSO. The TDC only works for the pilot. In the WSO cockpit, the Full Action function on either controller does the same functions as of the pilot's TDC. Also, in the back cockpit, the WSO controls have a few more functions than the pilot's HOTAS. And, once you are in the back cockpit, all the controls assigned to the pilot do not work. As said above, it is necessary to bind WSO own controls .

Nope. But if you are in a Cold and Dark state, you can press LCrtl+W and the panels will open. But no ladder, unfortunately.

Around the world? Cool! Must have been quite an adventure!