ivanwfr

Ooooh poor ED team! You're so committed to realism, .... and you bugged the moon ;D

This is interesting. But after flashing INS NAV RDY annunciation stage passed correctly and OSB NAV alignment activated to stop that flashing (FM-P440), there is no reason why a GPS linked system could loose cohesion. The only issue I had with EGI has always been reflected on the Caution Light Panel and had something to do with throttle EAC switch out of sync for some reason (mostly after getting back from Windows desktop to full screen DCS -- DX-Input EAC switch on-state issue...?). But chances are EGI could get out of alignment in some circumstances and this would be a good time to conduct EGI related EMERGENCY PROCEDURE recovery, (FM-P584). There is a REINIT GPS function in a CDU REINIT page.

Very, very short answers: 1. EGI align not complete before moving to runway ( OSB NAV + 4 minutes -> 4.0 0.8 ) 2. ILS NMSP Stow switch should be set to Able

There are things we can do but there are some we can't. ED public documentation for modders are their decision and when you see how obsolete it is, that just makes no sense. Nothing can explain why this page has not been maintained or removed. One way or the other, something has to be done before we know whether we are working with solid or volatile information. Just in about a few weeks, I've already got some of my LUA work based on Export feature to intefrace TM-TARGET made obsolete by 1109. I'm certainly not going to promote anything in that direction unless some sign of good will shows up... in the mean time, I'll stick with just flying.

When I got to the solution, I found you were there already! But it was with pleasure anyway as solving this kind of puzzle is part of getting the best from ME. As you say, it would be another kind of pleasure to get those howtos from just RTFM. That is if we had one instead of this Developer's journal page antique :doh: :D And no, I'm not just kidding as it does not do justice to all the good work it's suppose to display in one of ED site front-page :D ... got that one posted once more ...

I have none and wont have more for the time being because I have been nicely fed up with "Argument in range" for the comming days!

Yea, reached that conclusion too and used it to play with Frequency Mode VHF-FM button #152 in my Repeatable maneuvers misson. Here is a screenshot of how it is used in Missions\Aircraft Operation\1\A-10C-Training-Start-Up.miz.

Will try it and report back as soon as I find something useful. But I know from experience that ME can generate LUA code polluted with some inconsistencies. Searching the "mission" file for some wrong expression could help. I've already found some code that just does not hurt but does nothing obviously like this for example: SOME PARAM IN RANGE: MIN=10 MAX=5 ... never happens

I could manage to have Slip Ball (CA #24) working as a trigger in my attached mission of this thread: Repeatable maneuvers

At any time during a track replay the Control option can be selected from the Escape dialog box, near Quit, Continue and Cancel. But I had weird issues after using fast forward before using this "save game" replacement. It looks like some event chains can be broken and result in joystick control loss at some later point.

Here are some exercises to get prepared for Sabre's Flight Qualification campaigns requirements. Immelman and Split-S complementary nature has the friendly side effect of leaving us ready for the other maneuver when executed properly. Immelman [TABLE]1 Check | Mission start | After last maneuver [/TABLE] Message: "Fly heading 040, angle 7 at 260 knots" [TABLE]2 Check | min | max Heading | 30 | 50 Altitude | 6900 | 7100 Bank | -10 | +10 Pitch | -10 | +10 Speed | > 250 | [/TABLE] Message: "Our first aerobatic maneuver will be an Immelman" [TABLE]3 Check | min | max Bank |-10 | 10 Pitch | 45 | 90[/TABLE] ...you're expected to pitch up vertical then upside down. Audible cue when checked [TABLE]4 Check | min | max Bank |-10 | 10 Heading | 210 | 230 Pitch | 10 | 10[/TABLE] ...you should be back to a level flight heading backwards. o Message: "Excellent! You performed that correctly" [TABLE]5 Check | min | max Bank |-10 | 10 Pitch | 10 | 10 Check #2 | | +40s[/TABLE] ...back to level flight but some check missed within time limit o Message: "You failed to perform that correctly." Split-S [TABLE]11 Check | After previous maneuver [/TABLE] Message: "Fly heading 220" [TABLE]12 Check | min | max Heading | 210 | 230 Bank | -10 | +10 Pitch | -10 | +10[/TABLE] Message: "Our next aerobatic maneuver will be a Split-S. Begin when ready." [TABLE]13 Check | min | max Bank |180-10 | 180+10 Heading | 210 | 230[/TABLE] ...you're expected to bank upside down. Audible cue when checked [TABLE]14 Check | min | max Bank |-10 | 10 Heading | 30 | 50 Pitch | 10 | 10[/TABLE] ...you should be back to a level flight heading backwards. o Message: "Excellent! You performed that correctly" [TABLE]15 Check | min | max Bank |-10 | 10 Pitch | 10 | 10 Check #12 | | +40s[/TABLE] ...back to level flight but some check missed within time limit o Message: "You failed to perform that correctly." While executing one of these maneuvers, banking beyond -10...+10 while pitch is beyond -10...+10 is considered a failure. This means, that banking upside down and back must be executed at level flight. Update (110811): 1. Added more messages and audible cues. 2. Added a Cuckoo, an Evacuation alarm and a Chime tone triggered by Cockpit Argument #152 == VHF FM Radio 2 Control Panel--Frequency Mode Dial. BFT07_Loop_Immelman_Split-S.miz

CTRL+SHIFT Num2 and Num8 are Cockpit Camera Move down and up in category View Cockpit. Seat height adjustments can still go beyond max and bellow min camera positions. Those are two different things.

You may be interested by the first version of a replacement I could get working based on a small AutoHotkey script. As I intend to improve this first tool, I opened the ME - AutoHotkey utilities thread where it will be updated with improvements based on eventual feed-backs. And, if someone is interested, I will provide any detailed information that may help.

Named flags instead of numbered ones would be a blessing, among other steps towards lexical constructs.

Here is an AutoHotkey script of mine that helps solving some weird ME maths. These conversions are all obtained with a single Alt+Numpad keystroke: [TABLE]!Num5 | Heading | expected as 360 complement :cry: || !NumADD | Altitude | convert meters into feet !NumENTER | Altitude | convert feet into meters || !NumIns | Speed | m/s into knots !NumDot | Speed | knots into m/s|| || !Num7 | adds 1 | to current field value !Num1 | subs 1 | to current field value || !Num8 | Ranged values | applies +5% (mirror value into clipboard) !Num2 | Ranged values | applies -5% (mirror value into clipboard) || !Num9 | Ranged values | applies +10% (mirror value into clipboard) !Num3 | Ranged values | applies -10% (mirror value into clipboard) [/TABLE] Attached dcs_me.ahk code: Updates: Attached file extension has to be changed from .txt back to .ahk dcs_me.txt

I was just about ready to add some more results from my ongoing attempts with ME and I saw your reply to my previous questions. So I see I'm not taking everything backwards after all ;) Here is something that may help at getting less frustrated after a lengthy cold start, some great maneuvering results all ruined by some tiny mistake you can't avoid until a hundred times at doing each of those aerobatics. Anyway, it helps me as, thanks to you, I really (and I mean really!) know how to behave during a cold start (hundreds of them under my belt for newcomer I still am). Thanks once more for paving the road for me. So, my attached BFT07_Loop_7_Loop.miz (*) is based on the Loop part of your BFT07_Aerobatics_V1.0.miz. The idea is about being able to repeat a very specific part of the whole qualification in order to make it so easy that a mastered 90% success for each topic can get you closer to a good qualification probability. Here is what is in this -very small- miz file, 361k instead of the 6000k of BFT07. For my ME work part, it means that: - I could pinpoint the minimum necessary to be extracted in order to have the intro, check, fail and passed triggers working. - Could replace all the ONCE triggered rules with FRONT CONDITION's in order to make them re-triggerable by a reset rule called by failed or passed triggers from the previous attempt (or at mission start) And for the use experience part: - The start condition expects a heading of 040 (035-045) and you get the message ...Begin when ready. - Then, you get an audible feedback when each trigger gets activated and a white message about the trigger... If you don't hear it when it's supposed to occur... too bad ... hope the best for the next loop. I think you can see why I chose the loop exercise here! Thanks for your Heading Conversion Chart.pdf ... I'm sure it will be handy! And I intend to do more for those other Qualipains :badmood: * ...an improved miz version in this thread: Repeatable maneuvers BFT07_Loop_7_Loop.miz

I'm not sure but just in case it's what you're looking for, here is the simplest way to transmit something from one process to another on a single system: -- socket_send.lua {{{ local host,port = "localhost", 15001 local socket = require("socket.core") local ip = socket.dns.toip(host) local udp = socket.udp() local cmd = "" for i=1, 5 do cmd = "line #"..i udp:sendto(cmd, ip, port) end cmd = "quit" udp:sendto(cmd, ip, port) udp:close() -- }}} -- socket_receive.lua {{{ local host,port = "localhost", 15001 local socket = require("socket.core") local ip = socket.dns.toip(host) local udp = socket.udp() udp:setsockname(ip, port) local cmd = "" while cmd ~= "quit" do cmd, err = udp:receive() if err then print( string.format("err=[%s]", err) ) else print( string.format("cmd=[%s]", cmd) ) end end udp:close()

This was just a placeholder for one of the 10 snap views. In this scenario, one of them has to be turned into a dynamically modified view. It should be one of KP_0 ... KP_9, the one we could spare to that purpose instead of being defined to show a specific region of the cockpit. As I did not try to implement this yet, maybe there will be some tuning involved to make that work. I have to get motivated enough to give it a try... ;)

Overriding a standard mapping: 1 - If the "normal" LTB_MO layer is redefined, its standard function Toggle Autopilot will be removed. ...But APENG_MO=DX26 AUTOPILOT ENGAGE/DISENGAGE is there to do the same job ;) 2 - This is the first overriding definition I've made so far to a button that has a default action and it shows that the place of js_SHIFT() and th_SHIFT() function calls has to be changed in DCSW.tmc. They have to be called at the last possible moment, just before js_map() and th_map(). (...updated in DCS_ivanwfr_110803.zip first post archive) SHORT and LONG key press: Keypress duration is to be considered only when some long press on the same button on the same layer action is defined, otherwise, press duration is not a concern. Here, Pause TrackIR will be toggled with a short or a long LTB press as long as the MI-shift-modifier is pressed. Redefining LTB MO and MI layers: Those 2 variables are already declared in file th/th_declare.tmc. Here are 2 lines that will redefine LTB mapping to your liking and that's it. LTB_MO = TEMPO(USB_F13, USB_KP_5, 200); // SHORT=CENTER-TRACKIR, LONG=HUD-ZOOM LTB_MI = USB_F14; // PAUSE-TRACKIR Here is a new file to be included and called by DCSW.tmc. (just uncomment the 2 corresponding lines from my first post archive) And 1109 changes have not affected any of these mappings as they consist in some added combos:

Hi hreich, lunch time for me right now... coming back on the subject in the afternoon... I'm pretty sure there will be no problem to do all this ;)

The issue for those modified coordinates are all those "0"... these beasts are bug prone... Just change origin coordinates in order to push those viewports outside of the screen, say X,Y = 10000, 10000 and you won't have zero sized rectangles... you know, the divide by zero thing that hurts.

You just don't play it but rather "Replay" it! (see menu).

An effective display of how hard devs are listening would be to see the dedicated LUA ED Site wrong and outdated page be updated. Reading this Developer's journal->Lua exporting in DCS is somehow scary while considering whether you should spend a huge amount of your time on things that could get freezed for years. Should mods features be considered as something from the past for some smart marketing reasons, this page must be removed. If this is not the case, this section would be the effective showcase of what we're talking about here. Both ways, Developer's Journal site page has to be reworked. What do you think ?

+2

From my back seat - as watching your track felt somewhat like it ;) - I realized the number of things to do I didn't know about a few weeks ago... There I was just watching without the stress from having not to forget a single click here or a reverse-scroll there... But it was satisfying, you're so smart when you're only watching someone else do things or hesitate. Like the TACAN right button scroll BEFORE the right click and f*g X/Y flip instead of the 6 of 16X channel... kind of a bad-ass feeling ;) ... but you were the one who talked about publishing your track, I was just the one who said ...well, ok. In fact, that was not funny enough! I would say I could have done better it that situation, something with more light at the end and some big noise :music_whistling: But this kind of track can also serve the purpose of improving as you can jump into the front seat with Escape + take control to try a better handling at some point. And Fast forward can even get you close sooner to retry. Time-reverse would be nice too, like what you have in Dirt-2-3 although I know it is not possible in a sim as it would require to undo things like if we could un-brake a broken glass :lol: