Andydigital

Tried what exactly? Please us quotes if you cant be bothered typing a more detailed reply. Are you making sure you do not run SerialFP2 manually and are instead letting FSUIPC start it for you? Are you absolutely certain that SerilaFP2.exe is installed on your G: drive? Have you confirmed that nothing else on your computer is using COM port 3 as well? this shouldn't be possible but locking up could be a sign of this if two devices are trying to share the same port. Something screwy is definitely happening on your system, make sure you haven't got any other really old hardware connected that uses real Serial ports.

Makes sure the date and time of your PC clock is correct, also make sure that you copy and paste the key rather than typing it in then you can be absolutely certain that the key is correct.

What? Pete is waiting for you to answer his questions, he cant advise you further if you don't do anything, please review the posts on page 2 at least. Peter is away till next Monday now anyway so it will give you plenty of time to test. Also as Lars said in the post before yours are you sure SerialFp2 is installed to your D or G drive, because the line below must point to the correct location otherwise it wont work. Run1=READY,CLOSE,D:\Program Files (X86)VRInsight\SerialFP2\SerialFP2.exe

Yes just change the item you want to change only, no need to reprogram stuff that already works as default.

I figured it out with a bit of dumb hamfistedness, simply changing the parameter from 32 to 33; -- Master Warn if ipcPARAM == 10 then ipc.control(65823, 32) ipc.sleep(50) ipc.control(65823, 4) -- knob sound end to -- Master Warn if ipcPARAM == 10 then ipc.control(65823, 33) ipc.sleep(50) ipc.control(65823, 4) -- knob sound end That did the trick so anyone else who wants to add the Master Caution button please just add the below to the end of your mustang lua script file. -- Master Caution if ipcPARAM == 11 then ipc.control(65823, 33) ipc.sleep(50) ipc.control(65823, 4) -- knob sound end

OK fair enough, I just thought it was odd that you made one and not the other and thought there was a technical reason for not doing it, especially when the caution one is the one that is used most often. Can you remind me how you go about finding these L:Var parameters as I'm not having any luck so far, its not something I have had to do yet myself as everything I have ever wanted to use has worked fine with macros. I plan to use the two TOGA buttons on the MCP Combi with these master buttons as they are in approximately the same position as on the real Mustang panel :D . Thanks in advance.

Hi Guenter thanks for the work you put into lua package is there a reason why you made the "master warn" L:var but not the "master caution" one as well?

Please make sure you have the MCP plugged in and switched on before you start the simulator, also do not start SerialFP2 manually otherwise it wont work as SerialFP2 will take ownership of the com ports before FSUIPC gets chance to piggy in the middle. You also need to go into device manager and make sure that those com ports aren't already in use by some other device, you would be better off making a virtual pair of something like 11 <--> 12 rather than low numbers as they are more likely to be in use already. Try launching VSPE by double clicking on your saved profile (ComPairs24.vspe) for now just to see if it will load it properly. Time for bed for me now.

I think this is actually down to the aircraft causing a problem, as I see a similar effect in the new Feelthere ERJ V2. I believe Feelthere had something to do with making the Airbus too, although I could be wrong. I think it is down to the way the custom autopilot system works in these aircraft and the way that they can hold a constant speed or VS in the climb and descent. They hold the speed for example by constantly varying the VS speed and you can see this constantly changing on the M-panel VS display and SerialFP2 doesn't like it and gets confused. You can probably confirm this for yourself by trying it with another aircraft that doesn't have the same type of custom autopilot, you will probably find that it works perfectly in other aircraft, this problem only appears with the M-panel because of its multi use single dial, there is no such problem when using the MCP Combo.

Make sure your PC clock is set correctly, including the date.

Are you using mouse macro's? I'm totally unfamiliar with Airbus aircraft so I don't know how it works, but does HDG mode and Track/FPA mode share the same selector dial to adjust the bug? if so then you need to create macro's for the selector dial in both modes, so you would end up assigning 4 macro's (inc+/dec- X2) for the one selector dial on the Airbus panel presuming that HDG mode and Track/FPA are just 2 different modes. If a single dial was to work with 3 modes you would need to create 6 macros for it, and so on. Hope that makes sense.

You are so fast Pete it's unbelievable at times :lol:

Later; Well this is bloody odd, now that I've removed the hide-splash section again the minimise facility has started working again, I simply tried logging out of W7 and back in a few times to test the command lines and now it will minimise even after a cold boot, VERY STRANGE!.

Your path C:/is wrong. Windows uses \ not / for path separators. It's Unix which uses /. Pete

I wasn't sure if it was user error or not and I'd forgotten about it in the mean time Pete.

I presume this error is from VSPE? I had problems using the command line for VSPE as shown in your example above and as shown by Pete when I put it in the Start Up folder, I had to remove –hide_splash before it would work and minimise doesn't work either even though I've left it in the command line. It would have been better if you had quoted what your virtual pair was called too as it isn't clear what ComPair_24_56.vspe is supposed to mean. Why have one pair as 2<-->4 and another 5<-->6 (or is that not what 24_56 means), it would be better to stick to a convention (i.e. one odd and one even number per pair) to avoid confusion at a later date. Also make absolutely certain your MCP is connected to your PC and switched on before you start FS otherwise FSUIPC will not be able to connect if you try switching on the MCP after FS has loaded.

Hi, it is simple plain English, have you actually tried following the instructions step by step? or did you just read through them and say "I cant do that". If you are stuck at a particular part please do ask, and please don't just say I'm stuck on the com port part, its a large step and there must be one particular section you don't quite understand, please do expand. I would imagine you are having a problem understanding the virtual COM ports and how to enter the correct number in the FSUIPC.ini [VRInsight] section. Its actually quite simple when you know how. First plug the MCP Combo in an switch it on (FS doesn't need to be running) then start SerialFP2. If you look at the image below you will see the real COM port SerialFP2 is using to connect to the MCP Combi (known as FMER by SerialFP2) 1. write the number down (Com 5 in this instance, it will be different for you though most likely) that appears next to Port we will need it later. I have at least 5 VRI devices so I set up 5 virtual Com port pairs in VSPE. 2. Below is how my FSUIPC.ini looks as a whole for my VRInsight hardware, I only use about 3 devices at once in my flying hence only 3 instances of serialFP2 loading automatically in the [Programs] section. 3. . You should be able to work out what to do just from the images above but if you still aren't sure I'll try and explain it as simple a possible. Image 1 above shows Com 5 as the real Com port. (this number will most likely be different on every machine) Image 2 shows the virtual pair of Com ports FSUIPC will use (and which I choose) with that VRI device (MCP Combo in your instance Cathy) in this case I used Com 29 of the pair 28 --> 29, you could use 28 if you wished it really doesn't matter it just has to be one of the pair of numbers. Image 3 the section I have highlighted shows COM 5 (the real port) associated with Com 29 (one of the virtual pair of com ports, you could use 28 or 29 here it doesn't matter) The middle section [VRInsight.Mpanl] in image 3 isn't relevant to you by the way and can be left out of the FSUIPC.ini. I hope that helps a little.

If you mean VRInsight MCP Combo then yes it already does support pretty much all VRInsight hardware, that's one of the new features just added to FSUIPC 4.6a for FSX and 3.98a for FS9.

Please click HERE

I recommend you read through the manual a few times and you will get plenty of ideas for things to do with FSUIPC, reading through this forum will give you lots more ideas too.

Try assigning the button you are having a problem with to something else within FS9 itself, then once you have confirmed it is actioning this new command go back into the controls interface in FS9 and delete the assignment. This is what I do when a button starts to behave unusually, the same procedure works in FSX too.

If the aircraft that is playing silly buggers :lol: with the M-panel is Feelthere's new ERJ 135/145 V2, or one of Wilco's similar aircraft made by Feelthere, then the problem is caused by the way Feelthere control the default Microsoft auto pilot with their custom dll/gauge, they are constantly updating the vertical speed of the aircraft to maintain forward speed and the M-panel doesn't like it as the dll keeps stealing focus from whatever you doing at the time. Unfortunately there is no way around it as far as I am aware, other than purchasing the MCP Combo which isn't effected by this issue because it has separate dials for each autopilot attitude function.

Thanks for the info Pete, maybe I wont go for 12Gb after all then. Sounds like you have a sweet set up for the 737, and by the sound of it you may have got your pre-clocked Piper rig from OCUK, I imagine they are only around the corner for you as well. I get quite a bit of stuff from there and its only 30 minutes or so drive from Macclesfield. I've noticed they aren't as competitive on prices anymore, especially when it comes to the RAM I'm after (1600mhz), SCAN on the other hand seem to be very good on prices and they have a huge selection of hardware too, shame they are a little out of range for me, I know I can get it all couriered but I like to go to a store when purchasing a lot of kit at once.

Hi Pete I remember you asking over at the MyTrafficX forum about some information you required for setting up a RAMdisk to help with quicker loading of textures on AI aircraft, did it actually help in the end? I'm thinking of going down the same route hopefully later this month or maybe next. I'll be going with 12Gb RAM and trying for a 4Ghz overclock on an i7 920 too, I'm wondering if its really worth pursuing 12Gb or not.

Support for VRInsight products can be accessed at the VRInsight forums which can be reached by going to VRInsight.com and clicking on the forum link at the top right of the page. You can also contact them directly via email to get support too. As for your problem with FSUIPC make sure you copy the key exactly, the easiest way is to copy and paste it then you won't make any mistakes with the characters, also be absolutely certain you have your name and other details entered exactly the same as you did when you purchased FSUIPC at Sim-market's website. Also make sure your PC system clock is reading the correct time and date, if the date is set to a date and time before you purchased FSUIPC then the key will not work.