XCNuse

The menu seems to exist; but ED's documentation also states N/I, which I'm going to assume means "not implemented" (and after fiddling with it just now, can indeed state that it definitely doesn't do anything)

Well, Wags just released a video on the Viper getting an ability to do INU fixing. When can we expect this for the Hornet?

Consider your friend lucky then. After an hour or so flight and returning to airfields, I'm generally ending up with <20 FPS in 2D And I'm still trying to figure out why the others who fly in group in VR seem to not have whatever this issue is that I'm getting! There is something very very wrong with the map around airports; and definitely affects some of us more than others. I watched one of my group Viper guys do a touch and go at Rio Gallegos; and my FPS dipped down to 3! THREE!!!! FPS. Something is very very wrong. I've never had that low of an FPS in DCS before in my life.

As a follow up; interestingly ... this works just fine in single player. (which is why our mission maker was caught off guard) My assumption is, instead of delaying the spawn in time for the KC, it went ahead and spawned it on the runway, I'll have the miz attached. looks like he did a fixed "start" time of 90 seconds after mission beginning time (not trigger based, not that it probably matters here). I wonder if this is somehow tied into the few times I've had "mission start" triggers not work on me in multiplayer. The E3 is barely off the runway by the time the KC spawns in, so there isn't much give time on this, but it seems like the E3 was sitting on the runway maybe 60 seconds longer than it normally would have in single player. (there are many obvious fixes for this, including delaying flights longer, spawning in air, etc. but obviously the real issue here is, and as I just tested myself, it seems to work just fine in single player) Aaaaaaaand I'm going to start all over! Fortunately the track file is pretty short and.. does work since it's the very beginning. So the KC135 and E3 are indeed both set to runway takeoff. For some apparent reason in this multiplayer mission; they didn't spawn... on the runway like they're set to be. Not sure what to make of that.... track: https://drive.google.com/file/d/1v6Ixs3-5b8w_4prpiBp96Tdm3GpvSzvC/view?usp=sharing They actually ended up spawning on pads that connect to that runway, and back taxied to where they're supposed to take off from.

I have no idea if it's a DCS bug or specific to this map, or relating to. We had a mission (and I can recreate the miz if need be), that spawned an AWAC, and roughly 30 or so seconds later a KC135; both on the runway. but even with ground wind, they spawned on opposite ends of the runway... and ended up crashing in the center.

Up high performance for me has been ... very high, probably the highest of all. At airports and around airports..... By far the worst I've ever experienced in DCS. Something is very wrong with some of the airports. Flew around the mainland with some buddies this past weekend to check out the map; they were doing touch and goes in Vipers, and when they touched down... my FPS would drop to single... SINGLE! digits! Oddly, taking off as a group out of an airfield, it doesn't seem to be an issue; but later on "in the day" for some reason, I can't figure out what the cause is. I've played with my settings, lowering preload radius to 50,000 helped tremendously, but still getting insanely low lows when near or on the ground.

Wait really? I'm seeing Vipers do backflips in place! What on earth happened!?

I will say, I'm a bit blown away by the fact that M3/LN is about to quite literally single handedly add an entire new theater to DCS, that is truly not something I was expecting. I was just thinking the Corsair and a carrier was coming and that was that. It doesn't make complete sense to me due to the lack of support other than the coming Marianas WWII map, but I hope the efforts are worthwhile.

They showed off scans of the cockpit and exterior; so I'm of course referring to the mention of redoing the model. Which no, I haven't been around since 2014, but I must be the crazy one for forgetting it had a major rebuild in 2019 and more stuff again in 2020. And despite Leatherneck stating they had a "professional record the sounds of a CEii" the thing doesn't even have doppler sounds in DCS, and can be heard from miles and miles away, and still sounds like a 2 stroke engine.... which can be heard over the sound of something like an F14B's engines....

Another year...... Another Mig21 redo??????? When can we expect the CEii to get literally any attention your buyers have asked for. Who on earth is asking for the Mig21 to be redone... AGAIN!?

Major Update from Leather.... Magnitude3 https://leatherneck-sim.com/2022/06/01/2022-summer-update/

Popping in to wonder if this was also my situation was in relation to the F14; This mission I ran had 2x groups of F14B's (AI), and all 4 of us on that server locked up multiple times; no crashes, just total freezes oddly at separate times. I will have to attempt to replace the F14s with something else and run the mission again and see if it locks up....

I'm not sure where else to put this, and I'm genuinely confused what is going on with this mission; it was doing fine, and for some odd reason.. the hornets on the SC slide towards the front of the ship, and it prevents all other aircraft from taxiing. (and I don't mean just aircraft on the carrier, I mean... period) Shift the timer on the start for the Vipers and Eagles, and you'll see them stop in their tracks (freeze, not slow down), while taxiing. Whatiswrongwiththis.miz

I gave up completely. Then, went into the ME, cheated, tried again knowing where it was; nope! Then for the actual fun of it, went the other way, opened a blue slot, and tried finding the T80. Still nope! As an interesting side note; when controlling the T80 the second time around; I could hit lock target and it would actually show it. But then going from the Abrams to the T80... it couldn't ever see anything to lock up. Side note; I'm curious how graphics settings can affect the possibility of finding the target.

I feel like we've used Devil and Wolf on missions before without issues; certainly Devil, maybe I'm crazy? I haven't had a moment to try to play this in single player yet, spectating I never had issues. Also, I'll have to check whose log that is with the broken tacview; only one of those logs is actually mine, the other two are from some of the guys that I was flying with who experienced the lockup as well. We ran an older mission immediately after everyone had locked up a second time, and didn't run into any issues; I went back through the logs and didn't see those errors for sounds either; BUT, that mission was untouched prior to the recent patch; so I'm wondering if there's something the ME is doing to the current build missions, that it wasn't doing a patch ago. I've experienced weird ones like this before; when 2.7 dropped and glass reflections were weird, I was helping Nineline figure out why the SU25T didn't always have canopy reflections; turns out the miz files just had to be re-saved. So... is it possible something is wrong with currently saved / generated missions? unfortunately being lockups, we'll never get crash logs.. edit- oh hah, that was my log with the error LOL, that was for the DCS UFC exporter which I haven't used since last year, whoops! cleared that one out.

It should also be noted that actually all maps in DCS (short of the WWII maps of course), have some amount of orthoimagery in them (Caucasus is very limited until you reach the "play area" edges) Use satellite view in the F10 map and you'll see it. Fly over those spots, and you'll see it. NTTR has very prominent orthoimagery. Ortho in a DCS map is literally nothing new; in fact... it's not new period. Ortho taking a front seat in a DCS map, however is different and a first with this map. (but absolutely possible with other maps)

Was doing a multiplayer mission today, and a couple weird things happened. For starters, the radio presets on the Hornet weren't saved, and NVG's weren't saved from the ME as well, so we had to reinstall NVGs despite... knowing they are installed, and double checking, and same with radios. The within 40 minutes mission time or so, 4 of us started to lock up at random times. I managed to be lucky, and surely enough within another 15 or so minutes, I locked up, and two of the other three locked up again as well. Being locks, these logs aren't entirely useful, but... literally all logs show lockups during these missing audio errors. Everyone locked up at separate time for the record.dcs.log(1).old dcs.log.old dcs.log.old dcs.log

excuse me then for not realizing this was about OpenTrack and not TrackIR with TrackIR mentioned everywhere. I know nothing about OpenTrack.

One important thing to know about AI, they don't go exactly to their waypoints. I've noticed anywhere within ~100ft radius is "close enough" for them. And unfortunately, DCS can't force AI to go to specific coordinates. So it's worth noting that it's entirely possible your waypoints are too close to each other, and the AI decides that it's "close enough" that it doesn't need to go anywhere. (couldn't say on the perform task or command, that one is unusual and I've never noticed if those words ever changed)

Okay so do you have a profile that is then linked to DCS, and isn't the same profile that MSFS or BMS use? Once again I'll say reset your profiles. Again, this is an issue with your TrackIR profile, not DCS.

Have you tried resetting or making a new TrackIR profile? if it skips in the middle it sounds to me like you have two verticies bunched up near the centerpoint of your TrackIR profile This shouldn't be a DCS issue, but an issue you have with TrackIR. Reset your profile, and use the 3D head movement to better understand what's going on here. You should never have to touch TrackIR in DCS.

This might sound a little... underhanded... But is there any particular reason why an aircraft with literally a "single" task left, had its single developer scooped away to another project just to leave this one sitting around for over a year? From a leadership position that doesn't even make any logical sense. 15 months, and a single item keeps an entire module from being "feature complete" One person. How.

Another year has passed, the CE II still doesn't sound like a CE II and doesn't seem to match volumes of any other aircraft in DCS. Why is this still an issue 3 years down the road?

No description really needed. See image attached of tree blocking roadway, which causes unusual vehicle behavior.

Unfortunately within the circumstances of the lengthy mission I am unable in the current time to reproduce the issue in a single player mission despite ensuring near identical circumstances. That said, it's still not a lie that it is happening, here are screen grabs from tacview of it happening the previous two times I recall. I find it interesting that both distances to target are incredibly similar. Both missions were 1.5 hours in (more accurately, BMP3 on Syria was 93 minutes in, the T72 at NTTR was 103 minutes in) Both vehicles I believe were moving in the ~12kts range. Is it entirely possible this is an issue with lag? One important piece of information about this was being on a server with 100-150ms ping.