lonewulf

For FSUIPC 4.XX see here: http://www.fsuipc.com/

Anyone going for the FSLabs A320? Would be greatly welcome... Oskar

Thanks Andrew, No worries. In the meantime I can still manage with 2.7.0 which works fine :smile: Oskar

Hi Andrew, I have just installed LINDA 2.8.0 and ran into a problem with my "old" MCP COMBO. When calling the combo all assignments are empty and furthermore an error Window appears that claims a missing file named "btn_mcp_auser_inact.png". Scanning through the indicated path shows a similar file, but with slightly different naming "btn_mcp_user_inact.png" ISO "btn_mcp_auser_inact.png". Nevertheless renaming this specific file did not cure the problem as most probably also other files/filenamings are affected. Can you have a look into this? Thanks in advance! Oskar

Definitely NOT frames-heavy, at least that's my impression after several flights. I have equal or slighty better frames than with PMDG T7. Nevertheless there is no hurry for a LINDA development as long as NavDataPro is unable to provide Navigational Data Service.... :rolleyes: Oskar

While desperately trying to set-up the VRi Airbus FCU with LINDA 2.0 on a friend's computer, there is a general question coming up. Is it possible to set-up LINDA 2.0 without having the original LINDA 1.XX running before? It seems that not all entries are made in the FSUIPC.INI to run LINDA successfully. When I connected the Airbus FCU to my computer (I run the old MCP Combo) and just copy the new LINDA 2.0 files over the existing install of my linda 1.XX I get it to work. No joy however when trying a vanilla install of LINDA 2.0 on another computer. Btw: as far as I have seen when doing some trials on my computer, the ALT managed (push ALT knob) function does not work. It does nothing, While you can clearly see any VC knob being pushed (SPD, HDG, V/S...), the ALT knob does NOT move at all. Pull is ok - just not push. Oskar

This is the FXAA Indicator. Look in NVIDIA Inspector for the entry: "Toggle FXAA Indicator". Most probably your setting is "ON". Set it to "OFF" and the green square is gone :rolleyes: . It happened to me when updatig the driver to 327.23. For any unknown reason this toggle switch was enabled. Oskar

Hi Günter,the problem is that I'm not using a single standard.xml but several for each possible configuration setup such as 1 Throttle, 1 Prop, 1 Mixture, same for double throttles, then for individual settings per A/C type. But you pointed me towards a possible solution. When I look into those XML's I see much too many entires for one component - and not only for the Rudder pedals! It is my understanding that each component should be mentioned TWICE: once for normal ops and once for SLEW ops. As I see it I will have to set up these XML's from scratch. I have no clue who is responsible for those multi-entries - maybe a glitch of FSX ? anyway I will try to sort this out and report back.Oskar

Hi Artem,Nothing uncommon here. LINDA doesn't start a second instance. It's really hard to tell what is wrong with it. You might remember that I have funny entries in the Setup Summary of the Joysticks where it shows 4 entries for my Saitek Rudder Pedals - although I have only one set! This is still the case with V1.1. So I strongly presume that it has to do with my setup with 5 components. I use:1 Logitech Extreme 3D Pro Joystick2 Saitek Throttle Quadrants1 Saitek Rudder Pedals1 VRInsight MCP ComboWell, for the moment it's not a problem as long as I shut down everything before restart. It's not a serious issue - just uncomfortable .Oskar

When I start FS LINDA will be started automatically in minimized mode. So far so good. When closing FS LINDA will remain running. So far not so good. When I start FS again LINDA devices refuse to work. I have to close down LINDA and restart. Then all is ok. Same if MCP Combo is used. I need to shut down everything (MCP Combo + Linda) to have it working at next FS start. My impression is that I didn't have those problems on previous versions. I could keep all devices running and LINDA would syncronize without any problems. Not so with V1.1. Could that be a snag on my system? (Same as with those funny 4 Saitek Rudder Pedal entries...?)Oskar

Nope. It starts instantly - so to speak. There's no noticeable delay and besides this oddity no abnormal behaviour. I must say that I observed this each time I upgraded to 1.1b6 during my "odyssee" so my first thought about all the problems was about those entries. However now everything is perfect - just these odd entries.Oskar

Hi Artem,Thanks, that did the trick . Everything works flawlessly now. There's however one thing that still puzzles me. When I look at the "summary" page I see quite a few entries that are supernumerary - to say the least.If you look at the screengrab you will note 4 entries for the Saitek Pro Flight Rudder Pedals - however I do only have 1 - honestly . All other entries acre correct. Is there any necessity/possibility to correct that?

Well, manually updating didn't cure anything. The same error message is created again. I have to go back to original 1.03 again. Maybe this time I will update incrementally. I have downloaded a few updates. However it is not really easy to keep the oversight if your'e not following the thread on a daily basis. I will use v1.03 as the basis and then use v1.1b, v1.1b4, V1.1b5 and v1.1b6. Maybe that helps. Is it necessary to run the application each time after updating it (maybe it needs to write a few parameters)??Oskar

Well yes, I upgraded directly to 1.1b5 and then to 1.1b6, but both of them not working. I will try your suggestion later this evening and report.

Ok, here it is (that's the one that I'm using right now after reinstalling V1.03 and just modifying a few aircraft settings):VRI["ENABLED"]=1VRI["DEBUG"]=1VRI["COMPORT"]=3Oskar