XCNuse

As mentioned in OP, I'm unable to get it to force 21 .... period. Not sure why my mission files would be any different from anyone elses' allowing taxi to 21, but here's two files attached, one with very strong winds, and another with hurricane winds as mentioned. -1 has even an incredibly strong 18kts, right down the runway, told to taxi to 3. -2 has 100kts of wind going down the runway and they're still telling me to taxi to runway 3. I even had to point the plane into the wind otherwise it flipped on the ground! nttrno21takeoff-2.miz nttrno21takeoff-1.miz

it's a long standing bug in DCS specifically for the Hornet. Looks like over a year later they may have finally figured it out? thread specific to this bug finally got locked up and set to 'reported' soo... maybe eventually it will be fixed. Unfortunately, either run manual, or just adjust on the fly.

Bump to an old thread; I changed to a new computer for my dediserver and the new computer keeps randomly kicking groups of people. 2022-05-04 01:58:59.527 INFO Scripting: event:type=relinquished,initiatorPilotName=XCNuse,target=Devil-4,t=2715.801,targetMissionID=100, 2022-05-04 01:58:59.530 INFO NET: remove: client[2] 2022-05-04 01:59:02.526 INFO Scripting: event:type=relinquished,initiatorPilotName=RAM 1-4 | Glue,target=Devil-2,t=2718.801,targetMissionID=98, 2022-05-04 01:59:02.527 INFO NET: remove: client[4] out of 3 of us on tonight, 1 person survived, 2 of us were kicked. My old computer never had this issue. For what it's worth, it's the same network, both are static IPs on a external static IP so I can guarantee that is not the issue. I realized this could have also occurred when I updated router as well, so found a different setting, NAT Acceleration (NAT Boost), have disabled that thinking it might have some effect... will attempt to update if I ever find anything further.

None as of yet, all occurrences have been in multiplayer. HOWEVER, one thing that has happened consistently, has been the release of GBU38s during the same missions. I haven't had a moment to do basic tests, but I'm wondering if this is somehow tied into the bug with the gun pipper in AG being wrong in the Hornet when you have employed GBU38s? That said, OP stated this was happening in Viper. Other thing I can say when this has occurred, has been high altitudes; I don't mean aircraft at high altitudes, I mean the vehicles at high altitudes. This happened in the NTTR test ranges, and this past weekend in Syria in some of the mountains.

I have been learning the hornet near the beginning of this year, and I've had a heck of a time trying to get LGBs to hit their targets. I genuinely don't recall this being an issue up through last year. It doesn't make sense to me that a laser guided bomb should ever miss its target unless something went wrong during the release phase. A group I fly with has been absolutely struggling hitting moving targets with GBU12s, like it has constantly missed by <5 feet, and does practically zero damage to them..... because of poor / lack of splash damage. That said the person that likes to build the missions does like to add wind. Regardless....... LGBs shouldn't end up 5ft away from a lased target that consistently, like the lasing point isn't updating fast enough. Hitting non-moving targets, never misses.

none issues here; been working just fine. Tested just now, continues to work just fine.

It would be greatly appreciated if written text in the newer drawing feature had the ability to scale with the map. It's frustrating when putting in zones, or having multiple labels, and as you zoom out, they can begin to overlap, and lose context because of where they might end up visually on the map.

At minimum, I'd like to see it shown when using the ruler in the map. Personally, that's all I need to see.... again, personally. Flight routing is based on ranges and magnetic headings (ignoring GPS waypoints). So I would like to see this on the F10 map as well, not just a feature of the ME. As far as display... just give me a heading with parenthesis and "M" aka: 14.5nm : 245° (230° M) (15 declination for say NTTR, where it's a massive impact to have this visible)

Bump. This is still an occurence in 2.7.11.22211 Had this occur to a miz on us yesterday at NTTR, track too large but I can share the miz file at minimum. I will also share these interesting pictures, where all I did was go back in, alter the weather from 1C, to 5C (lines transparent), to 10C where they appear to be mostly opaque. edit- mission designer was able to fix it on his end actually by going into "Map Options", and disabling airfield layer filter, and clicking on it again. edit2- I am unable to replicate that fix on my end. OPERATION_RED_FLAG_1-1_FINALv5.miz

Have set up a new server computer myself and have had this happen twice now. Once to myself, tonight to another person. Log shows nothing interesting; just as if we had exited to main menu, nothing on our end either, just... straight to main menu. Server log just reads a line that starts off with "Scripting: event:type=relinquished", then the username.

And all of the sudden light wands get mentioned in the weekly newsletter. Imagine that.

To extend Digital's speech ... A couple of other things also drastically can help. Formation flying in general is a good place to start; even if it's for 60 seconds here and there, and it doesn't have to be fingertips, but able to keep with someone, is good practice in throttle control, and that's... 98% of what AAR is; throttle control. Second thing that a lot of people struggle with is hardware; having a curve can help a LOT of people, and I'm not saying you need to put 30%+ curve in anything, and keep it there, just put some in, see if it helps you hold formation better, and then over time back it down unless it becomes otherwise comfortable. We did AAR training this past weekend, and watching people do it their first times, they get tunnel vision on something, and start putting all the stick effort in the world to hit their mark. Less stick. But for many, they might not make that connection yet. This is more of a side thing, but I see tons and tons of people talk about "reference this or reference where the hose is on the hornets canopy" etc. etc..... IMO, it's poor advice. Coming from racing, the fastest drivers are always looking an entire turn ahead, they've already planned their route, and onto the next. Looking at where the hose is on the canopy of the Hornet's brow is like looking at the car right in front of you on track. It's dangerous, causes you to have delayed inputs, and gives you poor picture of the whole scene. So for those giving advice; stop telling people to see where things line up in their canopy. It's poor form. (also, if you say the word autopilot, and they say "oh yeah, I'm on altitude hold" or anything like that... reach through the screen and slap them)

Had this issue with a server the other week; then buddy said it just happened to him on his server a few moments ago. I know the mission he was running had MIST running; I can't say if the previous mission I was playing with a group when that happened was running MIST specifically; but it was running something like CTLD and the ability to pick up downed pilots. So I'm betting it's some error on the server side from scripting, that either doesn't chuck out an error to be cleared out to continue or something of the sorts. ie: if a script errors in single player, a popup appears, but the game still runs, if you hit OK, it will continue; I'm wondering if the servers are running into the same issue; but either no error appears, or there is no ability to clear it / accept the error. Edit- As a follow up; that's exactly what happened to my buddy, who doesn't have direct access to the "computer" that his server is running on, as a rented server. Mist specifically was still loaded into his mission, and is what caused the issue ... somehow, and since he had no ability to click on the warning box on the server, it just "active paused" Second edit; it wasn't Mist specifically, but a sub script that required mist; loading a table for units, but said units did not exist.

It's wild to me an entire year later and things like Rain 3 still doesn't show rain, and the fog is still in whatever ... this is. And over a year later from the roadmap of: Still not a peep news wise on sensor blockage, dynamic system, nor fog. Don't get me wrong folks, but a little clarification would be really appreciated. I'm getting incredibly tired of seeing all of these videos from these youtubers and instagramers of versions of DCS that others appear to be playing now for months or even an entire year that nobody has access to. Why share these videos? It's irritating not to mention, false marketing.

Yeah, just started looking into this yesterday and going through it. If there's anything seriously positive to say... so happy you put all the notes in that you did, makes finding things SUPER EASY! haha Yeah, not too happy with the BDUs, and kind of surprised some of them don't smoke (what's the point??). But I don't really want explosions (although this might change). Anyways, looking forward to your further revisions! Definitely can see some more extensive use for training stuff down the line. Finally getting some use out of flying in NTTR again

Interesting (and complicated) script! Fiddling with it, and plan to use it for a multiplayer for bomb toss testing practice, and have .. I think gotten one thing as far as functionality goes working. I don't like how this script sends all messages to the unit requesting "in". I've instead replaced the message functionality for in to be universal, so everyone knows that someone is "in" to the target. And have done the same for the output (or at least I think I have, I haven't had the ability to test yet), so that everyone can see the results. Couple functionality issues I am not a fan of such as that. I also frankly am not a huge fan of being forced to use the F10/Comms menu. The ability to use a trigger zone to set a unit as "in" is also something I hope I can figure out how to do (I'm not a coder in any way shape or form, and this is my first time dealing with MIST). Same with the ability to automatically set "out" when said unit leaves the trigger zone. And I know MIST has this ability. Then on an unrelated note, I had noticed the BDU's I'm using are not smoke bombs, so a way to mark the last "hit" with smoke, is the last thing I'm trying to figure out how to do. (Surely it can't be that hard, this script tracks all of that information) But appreciate the efforts, pretty impressive what this can do!

Aircraft type doesn't really matter, but it was testing between Hornet and Viper, winds anywhere from 80 to 300, even gusting as high as they go, ATC always was telling me to depart from Runway 3 This is departure; not arrival for the record.

Bump. Just found out last night how massive of an issue this is on NTTR specifically with 12 degrees of variation, means dropping in your waypoints based off bearings from departures and the arrivals end up being incredibly far off when not paying attention to this! Even if it just showed a separate set of numbers in a different color below the current angle, would be HUGE.

Unable to force 21 as the active at Nellis; even with hurricane-like winds out of downtown Vegas.

Seeing as though the current state of the game involves AI that won't actually land their aircraft, and would rather do orbits somewhere and go into AB every time they bank, and end up running out of fuel and ejecting................ I'm okay with there not being a dynamic campaign right now, because it would go horribly thanks to the current AI, who may or may not do as they're told. Beyond that, my speculation is it's currently between this, and sitting behind multicore work, both of which are vital to the performance and capability of the dynamic campaign's functionality.

Phantom news:

Kind of a weird statement after ED's own update to FLIR broke only their own aircraft, where all other third parties (whether they meant to on purpose or not [Razbam]), managed to get it right without issue themselves. This Briefing room for the SC is kind of weird, I really wish ED would better explain what the purpose of it is for the game itself. It seems ..... well, like a Briefing Room in-game to where you can't share powerpoints, but talk in voice I presume? But it's... Supercarrier only? It's a very strange puzzle piece in DCS, that I find interesting; but the lack of details as to what function it serves has been ever-lacking. Limited to, but not necessarily including expansion to.... non-Naval rooms, is the part that really throws me off.

I was running a test of Liberation the other night, LAN multiplayer, and thought I was going crazy Same, not all vehicles made noises. I don't use mods, never really have, and actually did a repair a few days before this past patch, and still no dice.

FYI this may or may not work; last time I tried... it did not work for me. But earlier this year and or last year, it worked for me a couple of times. So... this isn't actually a solution. ED needs to give us an actual solution.