Archived

This topic is now archived and is closed to further replies.

Artem Crum

Bug reports

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

added a new aircraft "iFly 737-600" with a search string "iFly 737-600" and LINDA automatically switches to this aircraft when I switch to it inside FSX (synch is on).I then add a key for N1: "M: IFLY737-600: MCP N1" (I have tested it inside FSUIPC, it works).It does not work from LINDA. The log shows "MCP MODE 1: Empty command for :: N1". new stick macros doesnt work either, nothing appears in the log.
Have checked your files and LINDA - everything looks correct and works on my system.LINDA shows the "P MODE 1: Empty command for :: N1" message only if there NO assignment done on this button. Your assignment is done however. Could it be, that you were trying to press the N1 button before saving the config?Anyway I need some more data to investigate this case.

Share this post


Link to post
Share on other sites

It seems to work after initial testing, I'll report more if something emerges.A couple of general problems, though:- You must hold down hat at direction you'll want to assign a command until clicking OK.- Assigning key combinations such as alt+space isn't possible.- Green bar indicating resetting of Lua sticks on the screen if changes to configuration are made & saved while the simulator is running.

Share this post


Link to post
Share on other sites
A couple of general problems, though:- You must hold down hat at direction you'll want to assign a command until clicking OK.- Assigning key combinations such as alt+space isn't possible.
1. No, you have not. Button/hat not have to be pressed while you assign it. LINDA detects button presses only to scroll list of buttons for you, but you can assign any button at any time without pressing it. Hat just returns to it's central position, as this is separate state for it.2. There are several other key combination that couldn't be assigned because of limitations of Windows standard controls. But LINDA is not about assigning keypresses, it's about assigning the Lua scripts at the first place. And working with keypresses is the worst way of assigning actions which should be used only if there no other way out.3. LINDA is doing standard FSUIPC call to show these massages. In normal case they disappear automatically. No one yet reported the same problem.

Share this post


Link to post
Share on other sites

Shifted mode doesn't remain enabled after pushing a button on another device.

Share this post


Link to post
Share on other sites
Shifted mode doesn't remain enabled after pushing a button on another device.
Cannot reproduce. Need more details.

Share this post


Link to post
Share on other sites

Bug in generating the config-mcp.lua file after I customized my MCP-Combo buttons. I have a line that looks like this:["WX"] = FSX:_FUEL_DUMP_TOGGLE:0 ,It is missing the double-quotes around the value. Once I added those LINDA didn't complain with the message "function arguments expected near ':' " anymore and my MCP-Combo worked again.I also see lines like these:["A -"] = GPS_ZOOM_dec ,["A --"] = GPS_ZOOM_dec ,["PRESS"] = GPS_MSG_button ,["FPV"] = Battery_toggle ,They don't seem to be a problem (probably because they don't contain special characthers but shouldn't they be strings and therefore quoted as well?Allan

Share this post


Link to post
Share on other sites
Bug in generating the config-mcp.lua file after I customized my MCP-Combo buttons. I have a line that looks like this:
Confirmed. And fixed. Thanks.

Share this post


Link to post
Share on other sites

OK, Got it sorted out by uninstalling FSUIPC and doing a fresh install. Not sure what the conflict was, but fixed now. Just need to have more than 5 devices available for use.

Share this post


Link to post
Share on other sites

Just a little thing that confused me:Flight Director On in linda is activated when the FD switch is down, and Flight Director Off is activated when the FD switch is up inside Linda.This is a bit confusing since the FD switch in aircrafts normally is on when up.The same issue may be relevant for the AT switch.Maybe change the names to Up and Down instead of Off and On?On the other hand I wouldn't loose any sleep if this isn't changed :( Helge

Share this post


Link to post
Share on other sites

Helge, are you talking about the FSX default aircrafts or..?

Share this post


Link to post
Share on other sites
Helge, are you talking about the FSX default aircrafts or..?
I am talking about what is listed on the linda setup display for the MCP. If I assign a command to "F/D On", then that command will get called when the switch goes to the down position, and likewise any command assigned to "F/D Off" will get called when the switch goes to the up position.That would normally be intuitive since most switches are thought of as on in the down position. However F/D and AT both tend to be in the up position when on (in for instance Boeings), thats why I suggested that you named the buttons up and down.So on the Linda screen, do not show "F/D On", show "F/D Down" and replace "F/D Off" with "F/D Up".Same goes (I think for) A/T. Not sure about the AP master switch.

Share this post


Link to post
Share on other sites

Helge, as I can see in my code, the FD On in LINDA corresponds to the FD UP on physical switch.

["F/D UP"] 		= Autopilot_FD_on  ,["F/D DN"] 		= Autopilot_FD_off  ,

Left part is a COM-port command we are receiving from MCP and the right part is an action LINDA executes on that command.If only something is messed up somewhere deeper...

Share this post


Link to post
Share on other sites

I've checked a bit more, it is only F/D that has crossed wires...Here is what I did to test it.Created two functions in aircraft.lua:AP_FD_On(){ DspShow("FD", "ON")}AP_FD_Off(){ DspShow("FD", "Off")}then I assigned AP_FD_On to "F/D ON" and AP_FD_Off to "F/D Off".When setting FD switch to upper position I now see the text "FD OFF", and when I set switch to lower positioni, I see the text "FD ON".A/T and MST switches both does the right thing, it is only F/D that seem to be inverted.

Share this post


Link to post
Share on other sites

Hm.. interesting.Just had it tested. No "crossed wires" detected. Default FSX Boeing 737 - FD switch on Combo is synced with AP panel inside FSX.1. Quit the FSX2. Run SerialFP23. Let it connect to the MCP4. Mark both test checkboxes5. Try to switch the FD switch and note what will be show in SerialFP - upper switch position should send the FD+ command.

Share this post


Link to post
Share on other sites

Upper switch position shows "FD-" for me, lower "FD+" (this is in the Rx part of the test window).Hmm, does that mean that my MCP Combo has buggy firmware?It's very new, maybe newer versions react differently from older?

Share this post


Link to post
Share on other sites

Mine shows the FD+ in upper position. Version is 2.520.Wires are crossed somewhere inside your device :-)

Share this post


Link to post
Share on other sites

lol ok, well I can live with that, I just switch the two commands. I wonder if others that have a new MCP Combo has the same problem.Another mini mini thing (I am afraid you don't have anything to doBig%20Grin.gif)I have FSX Sync on and load for instance the default Cessna, and Linda switches to the FSX Default (or whatever plane I loaded) and turns the box orange.I then just stop FSX.The orange box disappears, but I can no longer switch to another plane in LINDA, its locked to whatever plane it was in when FSX ran.After stopping and starting LINDA everything works again

Share this post


Link to post
Share on other sites

Hi HelgeWith my new MCP Combo v2.520 :FSX Boeing 737 loadedF/D On on MCP makes F/D On in FSXF/D Off on MCP makes F/D Off in FSXsame for A/** looks normal here.Michel

Share this post


Link to post
Share on other sites

HelgeSome tests with PMDG MD11 :1. MCP Combo : Disengage is UP --> FSX/MD11 : AFS OVRD OFF is DOWN and vice versa2. MCP Combo : F/D is UP --> FSX/MD11 : F/D is OFF and vice versaIt is not what we thinck it will be logicaly.LINDA settings for PMDG MD11 takes FSX Default aircraft for these 2 switchs.Possible solutions : 1. Inverse the functions settings (set OFF for ON and ON for OFF - not very good)2. Search the good offsets and write the new functions - better)Michel

Share this post


Link to post
Share on other sites
I have FSX Sync on and load for instance the default Cessna, and Linda switches to the FSX Default (or whatever plane I loaded) and turns the box orange.I then just stop FSX.The orange box disappears, but I can no longer switch to another plane in LINDA, its locked to whatever plane it was in when FSX ran.After stopping and starting LINDA everything works again
Cannot reproduce this either.. any additional details and/or conditions?

Share this post


Link to post
Share on other sites
Cannot reproduce this either.. any additional details and/or conditions?
Strange...Here is a very detailled step by step to reproduce it, at least for me and my mal-wired mcp :(- Start LINDA- Choose "A2A Spitfire" (The important thing here is to notice that you in fact CAN chose the spitfire).- Start FSX- Choose the default Cessna- I Get an orange bar around the text " * FSX Default" and "FSX sync" is orange too.- Note it is no longer possible to switch away from the "* FSX Default" which is as expected since sync is on...- Close FSX.- "* FSX Default" is still selected, but orange textbox is gone and so is orange FSX Sync.- Now try to select the "A2A Spitfire". It looks like you can, but it immediately returns to "* FSX default".THIS is the mini bug I talked about. Its certainly not that important to fix, since I just can close LINDA and open it again to clear the problem.If you still cannot reproduce it, then it must be my computer that has crossed wires too :)

Share this post


Link to post
Share on other sites