meandme

You got FSUIPC running properly?

Just FYI, I'm maintaining a repository with the A320 module at https://github.com/winternet-studio/linda-fenix-a320 - this particular issue I have also documented there.

FYI I'm trying to keep this page updated with the latest status: http://aviation.allanville.com/tileproxy/

DivineSense, I'm with you all the way! I can only hope that your thoughts and your name match up Regarding the 3D maps I would think it's just a matter of time until someone picks it up for flight simulation - but who knows when... For TileProxy services I'm keeping an up-to-date list at http://aviation.allanville.com/tileproxy/ - I hope people will let me know if they find new services or tweaks. But I'm wondering about Google Maps and why it can't work. I would assume TileProxy downloads tiles just like a browser - and in that case, how can Google know that TileProxy is downloading the tiles rather than the browser - unless the user agent string says that it is TileProxy?? But in the services a user agent string from a normal browser is used, so I wouldn't think that would be the case???! Anybody can explain that?

Ok, so this is intended and I can understand why in some cases (with some aircraft) you want that. But then at least the label in the display should be corrected accordingly.And also I would really like to have an option (preferrably per aircraft) where I could select whether or not it should automatically switch back. Wouldn't that be possible, Mr Crum?

In the new version 1.11 there seems to be a problem with selecting, or in particular, remembering the EFIS mode. The last 3 buttons on the USER panel I have assigned to EFIS mode 1, 2, 3 respectively. When I choose mode 2 or 3 it correctly switches mode and shows M211 or M311 in the display and for some seconds the buttons and knobs also use that mode. But when I don't touch the panel for a while it automatically switches back to mode 1 when I hit buttons or knobs again - even though it still says M211 on the display! So there is something wrong there...I haven't tested this with the MCP or USER panels.

I'm working on one and is mostly done but there are a few knobs (and most of the MCDU keys) that are troubling me...

Would it be possible to add an option for executing a simple mouse click on a x,y coordinate and deciding whether it should be a left-, right- or middle button click? I have a few functions which I unfortunately cannot command any other way than clicking with a mouse, so therefore I would really appreciate that feature...

Of course! Done!

Ahh, I didn't compare it with other macro files. I'm not sure who put the vasfmc.mcro file there (whether it's vasfmc itself or FSUIPC) but I think this is a legal format to leave out the gauge name. The reason it does not have a gauge name is that it's not a gauge vasfmc is a stand-alone program that I run side by side with FSX. The new version has a gauge you can install within FSX but I'm not using that...

When I want to assign the vasfmc mouse macro "NL_L range inc" to a knob it is not listed in the UI in the "FSUIPC Macros" window in the "Available macros" section. When I look in the file vasfmc.MCRO it is there, but it's the very first one, so maybe you accidentally skip that one when parsing the file. When I manually go and edit the config-mcp.lua it works just fine. So it's only a UI issue. This is the beginning of my vasfmc.MCRO file: -----------------------------------------------------------------[Macros]1=ND_L range inc=Cx01006dd0,12=ND_L range dec=Cx01006dd0,-13=ND_L mode next=Cx01006dd0,24=ND_L mode prev=Cx01006dd0,-25=ND_L arrow L next=Cx01006dd0,506=ND_L arrow R next=Cx01006dd0,517=ND_L airports=Cx01006dd0,608=ND_L VORs=Cx01006dd0,619=ND_L ND_LBs=Cx01006dd0,62...-----------------------------------------------------------------

How can I create a module for an aircraft that LINDA detects as an "Default FSX" aircraft? For example my Carendao Mooney is detected as a default aircraft but I would like to make a separate module for it... and possibly for other default FSX airplanes as well...

In the beginning when I first tried LINDA I'm pretty sure I was able to monitor LVars in the console window. But now I cannot in any way get them to show up in the console again - and I can't for the life of me figure out why! I have enabled all checkmarks and tried changing FSUIPC loggin options etc. - but nothing works. Any idea as to what could cause them not to show up??! I finally saw the "log lvars.lua" script that comes with FSUIPC and got it working, but why can't I get it to work in LINDA again?!

Could the update where the latest bugs have been fixed made public? Would be nice to not having to do the workarounds anymore...Allan

I don't have enough buttons on my joystick either so I wanted to use my keyboard - but my main keyboard though, but another keyboard through the use of HIDMacros. Ahhh, ipc.set actually sets a global variable - awesome! This just gets better and better!!Allan