v81

As much as i'm annoyed at ED for being slow to respond to bugs any post here should have at least something to back it's claim or question. @TomCruise if you have the mission and track file it would at least provide people here with something that can be investigated. If you're just asking as a general question then the bugs forum isn't the place.

ED - I'm fairly determined to not see another 8 years pass before this is fixed. How about some action? Surely when a bug gets this old it deserves some special attention.

@Flappie Just moved on to mission 'Haymaker' The kneeboard distances don't make sense there. To waypoint 1 is showing 8 over 3 - 090degrees. 8 kilometers should be 5 NM or similar To waypoint 2 kneeboard is showing 34 over 10 - 103 degrees. again, 34km should be about 16 NM I think this is why i was never able to make sense of these numbers.. some of them must be wrong.

Come to add me a me too. Wasn't sure what had caused it but it all makes sense now. @Scott-S6 - Haven't found any info on exporting the 430, are you able to share what you know?

Thanks for the reply @Flappie The number of number makes sense now, just hadn't seen it before. Appreciate that being cleared up. Re the Garmin, another thread confirms this is a bug, i have no issues applying compensation for the doppler and getting where i need to go. The Garmin shows Desired Track and Actual track both denoted in degrees magnetic. So if one flys the Garmin on an Actual track that matches the desired track everything should line up, but instead one drifts off course. Bug for the Garmin here... Re the mission being designed for the Doppler nav system, if i recall correctly some of the middle and later missions don't have the info to enter into the doppler, or as i mentioned earlier it's provided via audio and fiddly to enter in flight. I think this campaign has prompted me to begin taking specific notes next time i start a campaign.

Coming up to a 5 year anniversary on this ED. 8 Years on the Mi8 hardpoints bug. Can we get a real bug tracker yet and start getting these triaged? It's starting to look grossly unprofessional from the point of view of a paying customer. It's a complex product and i don't expect instantaneous fixes or perfection, but you have admit this is getting silly.

Worked today 2.7.16, but took a long time for the arty to launch and hit. In the minutes i was waiting i thought nothing was happening and saw the mortar crews still up so i tried again and almost right away rounds came and hit the mortars. I then got the green flares and OK to land. Put her down next to the base facing east (wind dir), and .... round filled the windshield of the Mi8. Turns out the first call did work and was the one that killed the mortars, but they took a long time to come making me think they were the result of the second call. The second calls rounds.... they ended up on the friendly base.... the one i landed at. As mentioned in another thread, would be good to have a confirmation from the battery indicating that it would be a few minutes before rounds were inbound, then we'd know to wait.

Worked OK 2.7.16 but with a long wait. After requesting the strike it took a few minutes for it to happen. I didn't think it was coming or thought i had chosen the wrong grid so chose again. I then immediately saw the incoming fire clear out the mortars and thought the second call was what did it. I got a green flare and permission to land, landed at the position facing ~ east and.... saw more ordinance incoming. Was mission end with a court marshal, the new rounds were the second call can they were directed at the friendly base... and myself landed there. This mission could be improved by adding a notification along the lines of "fire order received, wait 2 minutes for setup" or something. I'm finding many of these missions need re-doing due to lack of information, misunderstandings or triggers not triggering properly. Best of luck.

Just flew this and did OK. In fairness to OP it is a close one, if you flew 090 without factoring in magnetic declination it may fly you into the circle. Need to fly 083.5 magnetic for true 090 That 6.5 degrees will put you easily in the detection zone and it would take almost nothing but a tiny bit of being off track to get shot.

C'mon people. 8 years is a bloody joke. FIX THIS ALREADY.

Had to fly this 6 times to get it to work. This needs to be looked at and bought up to a more reliable state. If there have to be delays before the Mi28 can engage effectively then fine, but make it known through an audio prompt.

I gotta chip in here... this campaign is a hot mess. I have managed to get through to about mission 15 or so, but so many things broken along the way. The grid system used needs more explanation, there are bearings and other numbers on some kneeboards, but i have no idea what the numbers mean. It's one number on top of another number, this is never explained and I've not seen it in charts before. If it wasn't for the garmin and using F2 a lot i wouldn't have made it this far. On of the biggest issues when flying with other helos is the pathing AI takes. It makes me wonder if this was never updated for the updated of the Caucuses map. I'll make a separate post regarding the worst case of this. Simply put though, this mission needs more documentation, an average player with an average aptitude should be able to perform the missions from the charts alone, and without the optional garmin. Also, the garmin desired track and track don't agree, and i read somewhere the bearing is wrong too. The track and desired track is supposed to be magnetic, to not stray from the track one needs to fly 6 degrees to the left of it at all times. It's clear one of the figures is wrong. Suggestions... 1) More documentation... whats with the crazy numbering of the grids, the numbers are non sequential, what's with that? 2) It would be good to make use of the doppler nav system. 3) More landmarks and / or audio prompts especially for the far away outposts. 4) Re-visit pathing on the new Caucases map. AI when encountering a hill drop from 230kMh to 50kMh almost instantly causing me to overshoot them despite pulling up as best i can. 5) Find out what is with the lack of engine power, i appreciate high altitude can be an issue, but at least 2 missions so far have required me to roll off the pad and 'fall' down the side of the FARP to get airborne. Don't get me wrong, i appreciate accurate simulation of difficulty, but if a helo cannot take off with levers set to full and / or FreeTurbineRPM govenor wound to max and dust protection off then they aren't fit to fly. Some difficulty to make you think is good. making it impossible to perform a sensible takeoff is not. Regarding the last it almost feels as if the engines were de-tuned in the mission to simulate high alt ops, and then separately in another update high altitude engine parameters were adjusted as part of an overall update to the helo, then both combined makes it near impossible.

1 Year and nothing?? Is this ever going to be implemented?

Regarding this, is the Arduino Mega a *HARD* requirement in code, or does it just happen to be suited due to the number of serial ports it has? I assume 1 port is needed to speak to the host PC and then at least one extra to connect the transceiver to. In some Arduinos the UNO for example, the USB is connected via a USB/Serial adapter to the solo UART on the chip so that naturally rules the UNO out. The Leonardo has 1 port in addition to the dedicated USB/serial, sounds like for a single transceiver this should be valid. The Pro Micro also has the dedicated USB/Serial interface + one additional UART - very compact and cheap to buy. The FlightPanels arduino library now claims support for STM Blue Pill, that has 3 UARTs plus dedicated USB/Serial... ~ USD$5 shipped in single units i think? Am prepared to do my own testing (when appropriate parts arrive) but wonder if someone closer to the code could clarify weather the Mega is essential, or just an ideal candidate.

Bit of a shame.. just not a Chrome fan but it's a small price to pay. My only previous experience is with BIOS is the original, it's great how it's browser agnostic. I'd have the browser open and watch something happen on screen and mirror on the hardware.

I've confused the Flightpanels profiles to be the same thing as DCS BIOS 'modules' that are installed separately over that side of the fence. Have just installed DCS BIOS Flightpanels and found that all the aircraft are already inbuilt. Didn't realize that's how the FP version works. Now if only there were a way do do everything without Chrome I'd be fully happy. Any way the ditch the Flightpanels imposed chrome app nonsense? Kind of annoying to only need chrome for the one thing and not have full control over window size etc..

@toutenglisseAppreciate your input. I was thinking more like ED could implement it in the game code itself. My level of programing is 0.1 out of 10... i can sometimes take a working script or program and tweak or adjust it to do something slightly different... but that's about it.

This has been a issue for years, but I've never seen it reported. Happens predominantly on busier servers, If someone has returned from a sortie, taxied to the ramp and is shutting down / rearming / whatever and another player selects a slot that the first player is physically occupying the aircraft are destroyed. This presents an additional issue of there now being debris in that location rendering it useless until the debris de-spawns or the server resets. Spawning in the debris causes the same issue. Suggestions on how to deal with it range from trivial to significant work. Easy way, have the server check that the location is suitable to spawn in before inserting the joining player. Could do this by sampling weather or not another aircraft is present within xyz co-ordinates of the spawn center. Then delay spawning for new player with a client message saying the current location is occupied. Crude but effective enough to stop telefraging. Most complicated - have a system of aircraft inventory and some logic in the game itself to determine where 'client' aircraft spawn. Something should be done... can happen not at all or a few times in a session. Either way it's unpleasant and DCS should be better than to fall victim to such a simple issue. Can this get a look at please?

Any chance this can get looked at?? It's a mission breaker and a game breaker when you're relying on this unit being destroyed to achieve something. Keep in mind the CH47 and a bunch of other aircraft suffer this issue.

So... I'm lost. Is there a way to with Flight Panels then to connect physical I/O to DCS. Can flightpanels profile make an LED on an arduino blink.

Yes... already reported 8 years ago... And several times since. This is game breaking in that if when playing multiplayer i want to slot for troop transport or logistics i remove hardpoints to reduce weight and get better visibility without the gun sight, then i cannot re-add the hard points Additional Info: Hardpoints appear for a moment only at time hardpoint 5 is loaded and flicks off again immediately when loading points 3,4,2,5 Hardpoints also appear for a moment only when loading hardpoint 1 and disappear when 6 is loaded when loading when loading all points - but this was not consistent. Attached is a demo mission file and also a track from same mission. This has been reproduced over and over and I'd love to see it fixed. Mi8 missing hardpoints.trk Single FARP support vehicles test.miz

Would like the PKT to go. Would love to see the others become options. They don't have any place in a civillian bird. Could they be tied to the removal / installation of the hardpoints & gunsight (which currently has bugs persisting 2+ years... please fix this too!).

Similar issues with other helos in AI hands. This was first reported elsewhere, i don't recall where over a year ago. Still happening and needs fixing. I have attached a TRK of an M1 Abrams emptying it's ENTIRE STORES into an Mi26 helo, and whilst the helo will be damaged it cannot be destroyed. That all HEAT, APFSDS, .50 and 7.62 bar for 1 accidental shot into the dirt when trying to recall the ammo switching bind. I have witnessed in Georgia at war an A-10C dropping a GBU-12 on an Mi-26 at Kras-Pash.... after emptying my tank into it.... only for it to still remain. 2 more GBUs later it was destroyed. This is broken, has been for >2 years. Track attached. I've seen reports of this being an issue with many helos in AI hands, please investigate. Indestructable Mi26.trk

Can't see it, any chance you can link it? Here is where I'm looking... https://github.com/DCSFlightpanels/DCSFlightpanels-Profiles

Can we expect an Apache profile? Is something holding it up?