Andydigital

We have been waiting 3 years for PMDG to fix this, they (Robert himself) promised in person to a VRi developer at an FS Convention that a fix in an SDK update was coming after the 777 was released, but as you can see they still haven't honoured that promise. The door open annunciators don't work either, another missing and promised item in the NGX SDK SP2.

Press DME on the radio section then turn the knob on the radio section and you will see the CRS adjust, press the DME button again to swap to the other DME radio..

You have to assign things twice in FSUIPC with the VRi hardware, that's the way they are designed, each button can have two functions assigned on alternate button presses. If you only want one thing you assign it to both press and release option in the FSUIPC GUI. The only VRi devices that don't work like that are the devices that are seen as normal joysticks, things like the GPS5 and TT Panel etc.

It works with the iFly 737 and the PMDG 737 NGX via the included software. You cannot program it via Linda. It does have some software supplied by the manufacturer that allows you to assign the buttons and switch's to FSUIPC and FSX controls. You cannot assign the annunciator lights on the overhead yourself though.

Simply copy the whole of the modules folder in fsx over to p3d, most of the time its as simple as that.

Check your spam folder perhaps the reply is there. Also use a free email address like gmail to contact them from, a lot of Mail doesn't even get through to them sometimes. Try both email addresses too e.g. Tech and Info @ Vri etc..

Test it with a mouse, it may be the drivers for the trackball that is causing the issue.

Sorry I've no idea I don't use the M-Panel, nor do I assist VRInsight any longer, hopefully someone else reading this can help you with your question, I'm not even sure what you are asking really. Is your problem purely cosmetic, i.e. there is a lack of animation of the dials turning in the 777 or do you mean that it does not allow you to turn or climb the aircraft.

Until you figure out which of your devices is causing Linda to throw the error then yes it will be unusable. Check none of your devices create a virtual mouse. Also to diagnose this some more unplug them all and see if Linda throws the error. Then use a process of elimination, plug one device back in and reload until you get the error again.

It was on the development tracker system, you would need to ask Artem for access to it, I can't even remember the name of the site where it was hosted to be honest. A search for "invalid pointer"on these Linda forums will find some info but not a great deal.

It's Linda itself that is giving the error. This is a long standing problem with Linda that was attempted to be fixed a long long time ago and we failed, and by we I mean by the developers of Linda and I tried to get to the root of the issue during the beta testing of the latest V1 of Linda,

VRInsight do, download the software from their website.

Download the latest software from Vrinsights webpage for support for the 777. VRInsight.com

As I tried to explain previously the software inside the throttle quadrant converts the axis movement into a virtual button press when you move the lever to the red area below the detent. When the pot inside the lever gets old and dirty it becomes noisy and the axis jumps up and down on its own without the user touching the lever. This jumping sometimes is so great that it looks like it is moving into the red reverse zone, thus activating the virtual reverse button and it is this that causes Linda to jump to the quadrant page. Is that clearer now?

Just be really gentle with those thin wires inside and you will be fine.

You have a dirty potentiometer in your throttle quadrant, the reverse button range on the Saitek quads is actually done in firmware when the axis gets to a certain range of axis movement, there is no physical button, the firmware creates a virtual button press as you move the stick into the range below the detent. If the pot gets worn and dirty then the axis output will start to jitter and it is this movement that makes it look like you have moved the stick to the reverse range. If you look on YouTube you will see some simple video tutorials showing you how to take them apart and clean the pots, it is fairly simple, just a little time consuming.

That's not really true, it depends on the aircraft/sim you are using and how the developer has assigned functions. It is highly recommended that you purchase FSUIPC for FSX/P3D though, as it will allow you to utilise all your joystick type hardware in a much better way than you can without.

Disable the MCP combo options in Linda, there is a tick box, remove the Tick and it should stop the error.

It doesn't come with any software, it's a joystick only type device that uses the default Windows joystick interface. You can do things like you want with any joystick in FS with FSUIPC, but it's a fairly complex process that requires manual editing of configuration files. I've no idea if it's possible in DCS as I dont have it.

By making sure that you remedy the errors it is displaying, the only time the window opens automatically is if there is an error message.

No you can't, you would need an internet connection just to simply activate ASN and also you would get no weather downloads either without the connection.

Have you set Voice to go to the headset in the FSX sound options, that's the only thing I can think of. Unless you have to set the sound device in the VATSIM software somewhere. Sorry that is all I can suggest, not being a VATSIM or IVAO user I don't really know how they work.

The display on the MCP2 shows the position of the flap handle selection not the position of the flaps themselves, but if the flaps are moving to the selected position then either a < or > symbol will show next to the number i.e. 5> to show that the flaps are moving to that position. Once in position the > symbol will be removed. I'm not sure if the MCP1 screen has enough room to display that info or not its been a very long time since I used my old MCP1 which is now in storage. This info is correct as far as the NGX is concerned, I can't comment with certainty regarding other aircraft that Linda supports.

The one called LindaCFG I think, I'm not near my FS PC so can't confirm the name.

I found another cause of this error is if you have 2 mouse devices plugged in at the same time, it doesn't always cause a problem with every manufacturers mice, but the two I tried did cause problems, I had a Kingston track wheel mouse and a Logitech mouse and Linda gave the same error. If I removed either mouse it would then work fine.