virgo47

I've noticed this too for hot start quite often. My custom simple mission with "Takeoff from parking hot" always fails the generators first, then I have to wait and re-enable the autopilot. The same happened with Instant Action called Free Flight that actually started parked hot at Sukhumi. I'm using Synchronize Cockpit Controls with HOTAS option and when I turned it off it didn't happen. I thought I have everything set as I want to - throttle up, collective down... no other axis does anything, right? Wrong! On my TM16000 the axis on the base was predefined as Main Rotor Brake Lever! And depending where this "unused" axis was I got the generator failure (or not). Now sure, the helo could hot start a bit more stable, engine needles are doing funny stuff when it starts and main rotor gets to 90% which makes me nervous, but not having the brake lever accidentally bound, moved randomly and synchronized to the cockpit at start... that seem to help.

Just chiming in with some translations from the Russian cockpit (HKTB is in fact more like NKTV): H=N направление (~napravleniye = direction) K=K крен (~kren = roll, bank) T=T тангаж (~tangazh = pitch) B=V высота (~vysota = altitude) Of course, the meaning was covered by the previous replies, but I was really curious what those letters mean (seeing H and B I guessed these are really N and V but in Cyrillic) - and I wanted to know the words in original. As I couldn't find it anywhere else, I'm just adding the info here.

Guys, I'm not sure how many of you are flying L-39, but here is my main page for it (TPZ file is attached): Now, as mentioned previously, there is also a companion AUX page where mostly the lower middle section is replaced by engine and emergency controls - but it is prohibitively inconvenient to import it as of now, because it shares a lot of buttons with the main page, but these get disconnected (Value ids are not merged, but duplicated, hopefully Touch Portal guys will fix that). The ideas behind this page: Definitely use tablet, mobile phone is not suitable for any serious page. I wanted to control both L-39C and ZA variants from a single page. I could make two separate pages (maybe I will), but most of the controls are shared. Green tinted buttons are ZA only, so they are easy to distinguish. Controls are roughly positioned as in the cockpit - of course with some limitations. Main switches are in L-39C layout, two ZA switches are added under them on the right. Armament buttons are kinda ZA layout, but left vertical panel and the pedestal are merged. But everything is there, even Deblock guns, which otherwise has no control shortcut in game! So now you can shoot at planes even under 400 km/h. Thanks to the later DCS-COINS updates, we can also control various knobs like light intensity! But this is only one way, because Touch Portal does not provide the other direction. RESET Critical Buttons can be used to flip first 10 main switches + some other stuff (like Flight recorder) on and off, to help you sync the page with current flying condition. It's not perfect, but better than nothing. Similarly, you can fix flaps and gear state by tapping on them. Heading is true, in the L-39 fashion, speed is metric (as it should be ) but altitude is only available in feet. There are no meters provided by DCS-COINS/BIOS at this moment. I hope you will find the page useful. Let me know if you have any problems with it. If you want to change something you're free to do so - it's up to you, I like it this way. dcs-l39-main.tpz

I have no TrackIR and just out of curiosity was checking options using Android phone. That lead me to opentrack. I tried it with PC camera (actually a DroidCam using the Android phone) - but the results were less than ideal, very jittery. But perhaps the problem was using neuralnet in opentrack with a camera (and probably not placed and lit ideally either). Then there were other Android options for opentrack: Head Tracker for OpenTrack - free, but I didn't get it, it seems it's using the accelerometer, not the camera, but I may be wrong... TrackAR for openTrack (funny, how everyone is caplitalizing different letters in the name of the project ) - around 3 EUR and SmoothTrack for around 10 EUR I went for TrackAR and while the UI is underwhelming (no axes shown) it actually worked quite well for me. So I spent a day to make it run and another weekend to make a video about it. Maybe it will not cover your situation, but I hope it helps: In my setup I wanted to use a phone under the monitor, either horizontal or vertical. And I was also interested in "hybrid setup" - for some flying I'm lazy to setup the head tracking and want to be able to disable it. All these things are covered in the video.

I have a similar problem. I'm experimenting with OpenTrack for the first time and I can stop tracking there with a keybind - but that does not allow me to move the view with mouse or with already assign buttons. I have to go to Adjust Controls and click on the dropdown menu triangle in the TrackIR column header to Disable it in there. Having a button shortcut would be great. The problem is that DCS has no idea I paused the tracking in the opentrack. There should be a way to pause the tracking actually in DCS.

When I was discovering Caucasus aerodromes, I always went for wind 5 m/s roughly in the opposite direction of the preferred runway for that aerodrome. That reversed most of them, and turned on the right NDBs - or disabled NDBs if they were only on one side. I have the following kneeboard pages from all this testing, I'm not sure how understandable they are without explanation. I also used and tested the information from those great DimOn frequency/aerodromes maps. Mine are much rougher and are also more focused on L-39 (like the radio channels).

I set up the hot start mission with wind to reverse the preferred RWY which is 32 for Soganlug. I was already on the runway. But whatever runway you go, it doesn't make sense. It sends you around - which is expected, but tells you to land on the opposite runway than the one you start - which is bogus.

No, no... I'll add the image. I asked Lochini and it navigated me to roughly my current position - as you can see, it makes sense to land on 13 from there. But when I asked Soganlug, it sends me all the way somewhere to the point (2) (roughly) - and then it sends me to runway 14 (blue arrow). How does that make any sense? I'm already way beyond runway 14, I'd need to land on the opposite runway. The messages for both directions have reversed landing runways for Soganlug. As for various aerodromes, I tried them all on Caucasus, without wind and with wind in both directions. I compiled my personal kneeboard for that and I know that some aerodromes are one way (Gelendzhik, Sochi, Batumi and Nalchik) regardless of the wind, but Soganlug is "normal" except for the message. In the mission on the picture there is no wind, Soganlug prefers RWY 32 in that case, Lochini RWY 13. That's also the direction of the hot start on each aerodrome if you create a simple mission for it.

I visited Touch Portal Discord where it was confirmed that currently this is the behavior. I asked for some toggle to merge the Values with the same ID - but if and when this is available is unclear. Until then, however, the pages that share some buttons are virtually unusable after import. We'll see...

Hello, Touch Portal users... I have 2 pages for L-39C/ZA ready (Main+Alt page) and I finally wanted to share them, but I discovered kind of show stopper for me and I hope there is some elegant solution for this. The two pages for L-39 use some shared buttons - each button is backed by a single value (e.g. for the state of the Invertor I). The problem is that after I export both pages, I decided to test the reimport - so I removed all the values as well. I was badly surprised that the values for all the shared buttons got duplicated - which is incredibly silly. Not to mention the original folder for them got lost as well. In general, Touch Portal page organization is pretty horrible. There is no scoping or grouping of anything - everything is global, nothing belongs to anything else. The disconnect in values and pages is the prime example. Ideally, there should be some "module" where I can export both pages and their values together... OK, importing two pages one by one instead of doing it in one step is not a big deal - but the value duplication is super silly - they have the same name, so you don't even know which of the two exactly same values is which. Does anyone have any tips regarding this problem? It's not practical to de-duplicate the values and fix many buttons on one of the pages. Anyone had similar problems with multi-page setup?

I'd like to have it as a Campaign actually. The disk space is no problem for me - we're talking DCS after all, so gigabyte here and there... what is it? I'd also rather not to mess with the original files, so I prefer using Saved Games (user files). BTW: For a short while I was considering doing the voice-over in pseudo-Russian accent... something like this: I really didn't get too far with it though. But I could do more if it makes any sense.

I've tested this in Kursant campaign mission one - and indeed, if I don't set RMI the plane is glued to the apron. I have no idea how he (IP) does it, because if he was on the brakes, the gauges in my cockpit should show it. He has no parking brake, so I hope he doesn't use emergency brake - which I believe is not to be used normally.

I'm trying mission 3 from the Kursant campaign, and while it's not a showstopper, I repeatedly see this scene at the end of the mission: The marked Mig stays there and is not able to park. The propeller taxiing around is waiting for it. What is going on? I've seen a recording where this definitely does not happen, the MiGs are nicely parked and the propeller can pass around them easily (from 47:20): Is this caused by the recent updates somehow? Messed up AI?

The first mission has quite strict parameters, but it's also the shortest one and the instructions are quite clear - after re-reading them couple of times. It definitely isn't a mission to be done on the first time. You should stay between 150 and 250 m, and the speed should not deviate much either. There are warnings first, but if you stay out of the tolerance, or go way over it, the mission ends right away. Now, the first circle is not evaluated, it's just a warm-up for you. So in any case you have to not screw it up too much to get to the second - evaluated - attempt. And there you can get like 2-3 warnings. Exact triggers are possible to find in the mission file, but simply said - stay in the tolerance. Practice makes perfect. It is doable. It can be frustrating if you miss some trigger, but in that case you probably did something very wrong (like a turn way too soon, etc.). Otherwise this mission is pretty well sand-boxed and I like I can actually go AGAIN after a successful attempt. If the attempt is not successful, you indeed get the order to repeat it - but the IP will also tell you: "You're not maintaining..." and after moment he lists all the things you're not maintaining. Like speed, altitude, etc. It's also good idea to start with some free flying quick mission where you practice turns with the right roll without dropping or lifting your nose too much. No reason to practice it after the cold start really.

Fixed itself somehow, works fine in 2.8.0.32235

Nah, it wasn't that - I was always on the front seat. But I figured it out, because the idea with the rear seat got me experimenting more. In some of my missions starting in the air the STOP worked, in some it didn't. It worked in solo flights. So I checked the rear cockpit where it doesn't work - and indeed - the rear pilot used what is called a "throttle limiter" in the in-cockpit tooltip. I reviewed the docs and it is described from page 87, picture in 88: Now, sure I read it, but I didn't digest it at the moment and forgot it in the meantime. Now it all makes sense. Thanks for the push to the right direction - that is to the rear seat.

After upgrading to 2.8, pressing the hotkey or binding (joystick/throttle buttons) don't focus on the action in the Control Options anymore - in any section. This was a very useful feature and it's sorely missed now.

I have L-39C set all right and have been flying it for months now, without any problem with throttle STOP/IDLE at all. But today I tried one of the provided missions - "Emergency CAS1" - and I was surprised I cannot switch the engine off (toggle STOP). I restarted the mission - and I couldn't toggle the throttle in idle position to stop and back at all - in flight, or right after I landed. I checked other missions - and Mountain Flying and One Pass... also don't allow STOP position at all - doesn't matter whether I use joystick binding or keyboard, toggle or STOP binding, it is totally not responding. Visual navigation starts hot on ground, but I can switch to STOP. All my custom missions (as far as I tried) have no problem - whether I'm starting in the air or not. Is there any logic to it or is it a bug?

No complaints at this moment - good job, it works great. I like the solution in the PP files, seems flexible into the future as well. Thank you.

This threw me off a bit when setting up my panels - but yeah, it works in C version, but not in ZA version. Quite a cheap bug indeed.

BTW: It would be great if COINS could do some transformations - now you do this % thing - but what about some simple math? E.g. for East bloc planes (like L-39) the altitude is typically in meters - but in commons there are only feet. I there was an option to divide that number by some float constant and cast it back to integer it would open some nice possibilities. This could be all in PP files, so it would be on top of DCS-BIOS and before it gets to TP which (AFAIK) can't do math in those text updaters. Another question that is on my mind... do you have a repository with that project, e.g. GitHub or so? I'd not be afraid about forks, while you maintain it, you're the boss - that's how it typically is with solid projects. But it would be a shame to lost this all if anything happens. I don't mean a plane crash necessarily, sometimes people just get bored. Also pull-requests would be a possibility (if allowed), people can test before releases, etc. In any case, it would be kind of a backup for you and us as well, if you don't mind.

No problem, thanks for the info. I tried search & replace and most of the stuff works fine (I just had to be careful about genuine use of L39ZA). One more question though - I had a auto-updated info from common data and this stopped working. I un-commented the lines in CommonsData.pp, recreated the TP plugin file and it started working - but in a strange way. This is the button: But instead of proper numbers it shows 0 deg (always), 0% km/h (yes, with %) and 4% ft. Do you know what went wrong with that? Speed can be fixed by using TEXT and not numbers (not sure though why numbers contain that %). But altitude and heading have no alternatives... Ouch, I've just got a suspicion - you translate all the numbers to % now? Can you make it switchable somehow? Not everything is %.

Thanks for the update, no complaints about the plane! Now my single new button I tested (with L39 prefix) works, so it seems promising. Does it mean that for version 3 I need to redo the actions and events? Is it intentional or is there a chance the prefix in TP actions/events will be L39ZA again? It's OK either way, I just want to be sure before I jump into the overhaul of the panel. Also, the slider for knobs (e.g. light intensity) is welcome addition - works like a charm (one way only, but that is TP limitation as I understand it) - great work!

I suspected I have some old DCS-BIOS installation I used for DCS OpenBeta (not my main installation), I uninstalled that as well just to be sure - that was installed as a Windows application. But that wasn't an issue. I tried the complete COINS install again with clean Script directory and only L-39 module (no FC3 and P-51D) and the log is just a bit different: 2022-10-06T06:32:13.372Z : Munt.G_DCS-COINS :DEBUG: Unhandled type received shortConnectorIdNotification Aircraft: [NO]: Unavailable in installed DCS-COINS module list! Aircraft: [L-NE]: Unavailable in installed DCS-COINS module list! Aircraft: [L-39C]: Unavailable in installed DCS-COINS module list! 2022-10-06T06:33:57.903Z : Munt.G_DCS-COINS :DEBUG: Action Message received Not sure what NO and L-NE means, but perhaps you know. I noticed that in entry.tp file the prefix was L-39ZA in COINS v2 and is L-39 only now - this matches the change shown in the picture above. L-39ZA was used for both L-39C and L-39ZA and worked for both planes.

Hi, I wanted to check it out and my L-39 TP panel for COINS v2 did not work at all. When I started to check the buttons, it seems all the actions and events need to be changed: I guess this is caused by DCS-BIOS and I'm fine with that (it's kinda a mix of boring and fun at the same time). But... it doesn't work even after change. I checked the verbose log and I see this: $ ./DCS-COINS.exe -v DCS-COINS Version 3 (2210.03): Verbose mode enabled. 2022-10-05T20:48:40.164Z [INFO] dcs-bios-api: parsed aircraft JSON - CommonData 2022-10-05T20:48:40.167Z [INFO] dcs-bios-api: parsed aircraft JSON - FC3 2022-10-05T20:48:40.172Z [INFO] dcs-bios-api: parsed aircraft JSON - L-39 2022-10-05T20:48:40.173Z [INFO] dcs-bios-api: parsed aircraft JSON - MetadataEnd 2022-10-05T20:48:40.174Z [INFO] dcs-bios-api: parsed aircraft JSON - MetadataStart 2022-10-05T20:48:40.176Z [INFO] dcs-bios-api: parsed aircraft JSON - P-51D 2022-10-05T20:48:40.186Z [INFO] dcs-bios-api: UDP client listening on 0.0.0.0:5010 2022-10-05T20:48:40.188Z : Munt.G_DCS-COINS :INFO: Connected to TouchPortal 2022-10-05T20:48:40.190Z : Munt.G_DCS-COINS :DEBUG: Info Message received 2022-10-05T20:48:40.197Z : Munt.G_DCS-COINS :DEBUG: Unhandled type received shortConnectorIdNotification Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: []: Unavailable in installed DCS-COINS module list! Aircraft: [L-39C]: Unavailable in installed DCS-COINS module list! Is it a bug or do I do something wrong? For the record, I deleted old Script/DCS-BIOS directory + removed the line for it in Export.lua to get the right version of DCS-BIOS.