Andydigital

You already can, click info> Runway/Gates and select your stand when you land, or during your descent.

Restarting FSUIPC7 fixes this pretty much every time I have this issue with the connect button not turning green. If you cant see an assigned frequency below where its says connected in the pane to the right then FSUIPC needs a restart. All my other apps using FSUIPC come alive then too.

If you don't have time to try it out in depth you will find a very good video demoing P2ATC at the page below. I don't remember whether the chap uses 3rd party voices or not but its still worth a watch for new or potential users.

I think of "my voice" as you call it as actually being my co-pilots voice, he does all of the comms for me, I just trigger certain parts with my own voice via speak recognition, then let the co-pilot carry on with the rest of the replies to the controller. I have one voice (Cereproc Scottish Stuart) set to exclusively reply on P2ATC (i.e. my First Officer) and I have the same voice assigned in another app called "Self Loading Cargo" which also uses TTS to speak in that app too. Another voice I use as a flight attendant in SLC, then the other 4 or so default and custom voices I have assigned in P2ATC to do things like Tower, Ground, ATIS etc, etc. I just use the random voice feature in P2ATC rather than assigning individual voices to each controller type, because it is easier and feels more natural, rather than hearing exactly the same voice for all towers all around the world. I you already own P2ATC or you haven't tried the trial version yet, you can test all this for yourself with the default windows voices.

Yes Cereproc voices work, I've got 4 of them and 1 Ivona voice, I also use a couple of the better default voices too. Yes you can set different voices for controllers and the pilots comms voice.

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.