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

Folks,I have reported the problem already in the NGX thread however I think it's best to start the whole inquiry as a new support item.Due to the fact that after applying the V1.0b5 and up nothing worked anymore I decided to start up with a basic LINDA setting. Here's what I have done:I cleaned everything up (including removing all LINDA items from FSUIPC.INI) and made a fresh install with LINDA V1.03. After that everything worked well. Whenever I apply one of the patches for the NGX (last attempt done with v1.0b6) the system is NOT working at all as there is that initialization error popping up at the monitor page:"[E] *** LUA Error: ...oft Flight Simulator X\Modules\linda/system/init.lua:53: attempt to concatenate a nil value"Here are my system specs (nothing really exotic that might have an influence as far as I think):ASUS P8Z68V PROIntel Core i7 2600k 3.4 GHz8 GB DDR3 RAM 1.6 GHz1 x 120 GB SSD OCZ Vertex1 x 480 GB SSD OCZ Ibis2 x 1 TB HD1 x Gainward GTX 580 3072 MB GDDR 5, latest drivers 285.62Power Supply 1200 W low noiseWindows 7 Professional 64 Bit1 x HDTV 46", 1920 x 10801 x Acer 23", 1920 x 1080 TouchscreenNow up to you. I would of course like to fly the NGX again with full LINDA support but at this time it's simply impossible as I have to work with V1.03 solely.Oskar

Ahh, I see the logic now. Well put with the brains and muscles Thanks a lot. Oskar

As I said, I'm not using a sound card but the onboard chip and there are Add-ons where this phenomen is NOT occurring. Oskar

When the whole hydraulic system is depressurized after engine shut-down (pressure <100 PSA) shouldn't the yaw damper switch flip to OFF by itself? Just something that I noticed and that would seem logical to me. Not sure anyway - just a wild guess. Someone with hands-on experience on the NG will know better. Oskar

I use a multi-screen environment with 3 screens in total and therefore I'm one of the old-fashioned guys using 2D panels. What I found is the following: Whenever I use the secondary screens for input and thus take the focus from the primary screen (meaning the primary screen to be where FSX ist dispalying and where the 2D instrument panel is displayed) part of the sound diappears. As long as only (I guess) airconditioning sound is concerned I wouldn't mind. However things are a bit worse: all RA call outs including the altitude warning are also lost. Has someone else also noticed this? I'm using Win7 64-bit with the onboard sound chip of my ASUS P6T deluxe V2 motherboard. Oskar

That would make more sense to me. I take it that you are citing from an original maintenance manual. Oskar

Thank you Mark, for your explanation. However I will never be able to understand this kind of logic I can check the power output on the engine's generators before connecting but I can't do so on the APU. If I can't I don't need the indication when it is feedig already. i would rather check BEFORE connecting. Oh well ... every A/C has its' own logic and we have to admire it nevertheless Oskar

Just another thing with the Electrics that came to my attention:When the APU is available the blue "Generator Offline" (or whatever it reads) light is on, indicating that the generator would be available. However I can't see any voltage/frequency indication with APU selected on the rotary switch.. It only appears when the APU generator is engaged online. Compared to the engine generators this indication is different. They show the voltage/frequency even when still idling. Is that correct on the APU? Oskar

Although I don't want to start a flaming war about this I strongly back this opinion. Especially multi-monitor users are quite commonly using 2D-panels. A VC plus TrackIR or similar is not a REAL alternative as it's movement is completely unreal and is not really useable for wearers of corrective glasses - especially when it comes to astigmatism correction. Of course things like these are completely unimportant to the majority of the simmers. Just get a bit older and you might find out Oskar

Hmm, well, let me tell from my RL experience with carbon brakes: they heat up considerably quick. Much quicker than steel brakes. After a landing at 50 t with Autobrake at 2 they should go up to at least 150°C if not higher. Also riding the brakes during taxiing you will have the very cuickly above 200°C Oskar