|
Post by Travis on Jan 16, 2018 19:26:38 GMT -5
Hello Kekelekou, Yes, the new ACME_FAILURES series of LVARs will report '1701' for a random mechanical failure of engine 1, a '2701' if your engine ate a bird, and a '3701' for a failure where your engine 1 ingested ice. Turboprop and turbojets could also see a '5701' if engine 1 didn't have the igniters enabled and you were in turbulence. There is no '4701' - which would be an engine failure due to a blown tyre.... WIth regards,
|
|
|
Post by kekelekou on Jan 17, 2018 2:47:23 GMT -5
You can not rule out the possibility of the engine ingesting a piece of blown tire! Just pulling your leg.
This is great news! It counter-balances the fact that my FSX got corrupted somehow, so I had to desinstall it. Here we go again with the fun of bringing FSX and all the addons back. The work in progress is safe, but this won’t make things go faster. So don’t hold your breath until the DamageMod is released.
Thank you anyway for providing the interface.
|
|
|
Post by alaskanflyboy on Jan 17, 2018 11:45:19 GMT -5
You can not rule out the possibility of the engine ingesting a piece of blown tire! Just pulling your leg. Hey, if you're flying a Concorde it's a distinct possibility.
|
|
|
Post by Travis on Jan 17, 2018 18:54:29 GMT -5
You can not rule out the possibility of the engine ingesting a piece of blown tire! Just pulling your leg. Hey, if you're flying a Concorde it's a distinct possibility. I thought about this for quite a while earlier last year.... Technically the wing-mounted fuel tank ate the shreds of tire and debris. The engine(s) only failed due to the fuel tank explosion. In a tangentially-related issue, sometime later in 2018, turbojet Captains with engines mounted below the wings can (optionally) face engine damage if they use unpaved surfaces (gravel, etc.) (Yes, we will allow for the possibility of 'Gravel Kits'.) Regards,
|
|
|
Post by Travis on Jan 17, 2018 19:03:55 GMT -5
You can not rule out the possibility of the engine ingesting a piece of blown tire! Just pulling your leg. This is great news! It counter-balances the fact that my FSX got corrupted somehow, so I had to desinstall it. Here we go again with the fun of bringing FSX and all the addons back. The work in progress is safe, but this won’t make things go faster. So don’t hold your breath until the DamageMod is released. Thank you anyway for providing the interface. It's our pleasure and we hope it works well with your DamageMod when you're back in the air!! One thing to note... if you declare a fault (for example, a "701" Engine 1 failure) in ACME_FAULT, we will feed that back to you in the ACME_FAULTS list. It would take the form of only "701" which assumes the preceding type of '0' meaning this failure comes from the aircraft or another add-on. (You. ) Regards,
|
|
|
Post by kekelekou on Apr 19, 2018 13:34:19 GMT -5
Hello there, Even though the FSC interface is not ready yet (the gauge is written, here comes the debugging), I released the v1.1 version of the Damage Mod last week. It’s available on Avsim, FlightSim and Flight1´s library. Download link for v1.1 : library.flight1.net/?p=11388The v1.2 is being worked on, to allow P3Dv4 compatibily and, of course FSC interface. Stay tuned!
|
|
|
Post by peter on Apr 19, 2018 16:19:35 GMT -5
Hi Kekelokou, I will definitely test your module and report back Cheers, Peter
|
|
|
Post by kekelekou on Jun 26, 2018 2:56:08 GMT -5
Hello!
Real life has taken its toll lately, but here is abit of news about the DM/FSC interface: The last test session with Linda (a tool allowing the direct writing of Lvars) last night proved that both directions work now. A DM-triggered failure updates the ACME_FAILURE list, and the other way around. I just have to test the communication between FSC and my DamageMod in flight through the FCDU.
Stay tuned for more!
|
|
|
Post by peter on Jun 27, 2018 4:16:36 GMT -5
Hi Kekelekou,
I tried to do more testing of the interface last weekend, but for some reason it stopped working: I just got a black rectangle instead of the interface window with all the systems. I believe it has something to do with an anti-virus program: at about the same time, GTN 750 stopped working because one of its files had been quarantined. I uninstalled the latter but didn't have the time to reinstall it, or your interface. I will keep you informed.
Peter
|
|
|
Post by kekelekou on Jun 27, 2018 7:20:51 GMT -5
Darn it! Was the Damage Mod working properly before the blackout, or the black panel is all you have ever got? I have had no such feedback so far, so please keep me updated about any hint on your side. I do hope this is « just » an anti-virus related glitch.
|
|
|
Post by peter on Jun 27, 2018 18:44:33 GMT -5
I am pretty sure it was not a problem with your module. It worked fine before, I assume that something ruined the panel.cfg file, or that one of your files got quarantined. I'll try to investigate on the weekend.
Peter
|
|
|
Post by peter on Jun 30, 2018 8:24:18 GMT -5
Hi Kekelekou, your interface works fine in P3D 4.3. The problem last weekend was that, in panel.cfg, the window in which your module is installed has been erased. the window (04) was still in the window list, but the actual entry was not there anymore. I presume what happened is that it got erased when I uninstalled Flight1 GTN 750 after it had been affected by my anti-virus program. I had the GTN installed in the Islander, and maybe the GTN uninstaller remembered the window number for the GTN 750 wrongly. In any way, I fixed that and tried to complete a flight with your damage module switched on. There was a big problem: your module worked and ruined my left engine. So good news for you, but bad news for my pax. I declared an emergency, diverted back to EGEO and landed safely. I was careful not to overstress the engines, but I was sloppy with the engine run-up procedure for the left engine. I guess I will have to read your instructions on how to fly with your module enabled in more detail Thanks for creating the module, it makes the Islander even more interesting. It might be nice to coordinate it with FSCaptain and add some financial costs if you have to do extra repairs. Btw, I repaired both engines after the flight and it worked perfectly fine. Cheers, Peter
|
|
|
Post by kekelekou on Jun 30, 2018 11:48:24 GMT -5
Thanks Peter for your feedback. I am pleased that you have found out what caused the trouble and that it’s fixed now. You are right, you are to read the Damage Mod instructions if you want to land with all systems in a satisfactory state The interface with FSC works fine when writing the failure codes directly with Linda, but I can’t test it though FSC due to the « not in database » issue I am facing. About P3Dv4, I have created an update to enable the 64bit versions of Doug Dawson’s gauges and my throttle and pitch lever intercept ones. But I don’t own P3D, so would you mind testing it (shouldn’t last more than one hour)?
|
|
|
Post by peter on Jun 30, 2018 20:30:57 GMT -5
Hi Kekelekou, I would be happy to test the update, but I still haven't had any luck with Doug's gauges. Maybe your update may even help to solve this Dutch and Travis have been occupied with RL stuff, that's why they are slower than usual with their responses. I have had a look at your log files and it appears to me that it may be a Simconnect issue. I am not sure though. However, it wouldn't hurt to reinstall the SDK package again. Cheers, Peter
|
|