Andydigital

The email address doesn't need to be active forever, it's just a way to uniquely identify you, as long as you do not forget it, its not an issue.

Yes FSUIPC can launch up to 9 programs via manual ini entries, search the documentation for RUNReady that should get you to the right part of the manual that explains it all in detail.

Take a look through the document I mentioned above and see if you can find anymore likely candidates, I haven't got time to look myself.

You could just use the keys options on the opposite side of the page if you wish and send the key presses instead, just tick the keys box on the left instead of FS controls on the right. The proper FS control names you are looking for are; NEXT_VIEW 65827 PREV_VIEW 65828 NEXT_SUB_VIEW 66153 PREV_SUB_VIEW 66154 You will find a document called "List of FS Controls.PDF" that list every control available in the folder; ....Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC Documents\ or similar for FS2004

I think the default top down view key on the keyboard is F9 does that work?

What version of FSUIPC are you using? Do you have some software installed for the HOTAS that came included with the joystick that lets you program the buttons and switches to do various things? If you have installed the software have you tried disabling this joystick software, it may be interfering with FSUIPC in some way.

Just keep answering yes, eventually it will work and not ask you the question again, its a bug in the FSX trusted modules system and nothing at all is wrong with FSUIPC. This question pops up on the forum every couple of weeks or so, if you care to have a look through a few pages of the forum you'll probably find another post asking the very same thing.

You need to open a support ticket at Simmarket and explain the situation to them, Pete has no control over the sales side of things, thats purely down to Simmarket.

A and S and then there is SHIFT A and SHIFT S which scrolls back the opposite way through the views.

Ok Pete I understand now thanks.

Hi Pete, isn't my button macro above calling parameters in his Lua script? Thats why I asked him to confirm his Lua script does actually do what he thinks it should, the script is the most likely place for the issue now I think. I must admit button macros like this is something I've never done before, so I wanted to confirm my bit isn't at fault.

Have you actually tested your Lua script ND Mode increase/decrease commands to see if they work with keys or joystick buttons? Looking at my code it appears that the formatting is correct, so I don't think that's the problem. Is the Lua script for this 747 really listed as number "1" in the [LuaFiles] section of the FSUIPC.ini?

Using Pete's efficient method you should be doing this; APP - - - 17 17 17 VOR - - - + 17 17 17 16 MAP + + + - 16 16 16 17 PLN + + + 16 16 16 Which translates to; 30=APP 30.1=P170,16,CL1:R,17 30.2=P170,16,CL1:R,17 30.3=P170,16,CL1:R,17 31=VOR 31.1=P170,17,CL1:R,17 31.2=P170,17,CL1:R,17 31.3=P170,17,CL1:R,17 31.4=P170,17,CL1:R,16 32=MAP 32.1=P170,18,CL1:R,16 32.2=P170,18,CL1:R,16 32.3=P170,18,CL1:R,16 32.4=P170,18,CL1:R,17 33=PLN 33.1=P170,19,CL1:R,16 33.2=P170,19,CL1:R,16 33.3=P170,19,CL1:R,16 There I did it for you, its the last time I will though :wink:

Presuming your go flight mode dial is set out APP VOR MAP PLN, to get to each setting you need to do this with the ND decrease and increase functions in macros in the FSUIPC.ini; APP = -3 (dec) + 0 (i.e. leave out the increase) assign this to Go Flight EFIS Button 16 VOR = -3 (dec) + 1 (inc) assign this to Go Flight EFIS Button 17 MAP = -3 (dec) + 2 (inc) assign this to Go Flight EFIS Button 18 PLN = -3 (dec) + 3 (inc) assign this to Go Flight EFIS Button 19 EDIT: You beat me to it Pete, lol. Also my version isn't as efficient.

Make sure the eye point isnt inside the seat or headrest in the VC, if it is you will find that you cant click on anything in the VC with the mouse.

I'm not saying they only work when in the 2d panel view or put another way I'm not saying you cant use the macros you created with a 2d panel in the VC view. Try creating a macro in a VC from physical 3d buttons in an aircraft like the PMDG MD11 and you will see what I mean, you need an actual 2d panel/gauge to capture the functions from in the first place. Most aircraft with 3d VC only are not amenable to mouse macros, in that instance you'll most likely need to go down the L:vars route instead.

The Duke uses default MSFS commands for the altitude so there should be no need to use Macros or L:vars in this instance. Macros dont work in the VC by the way, they only work on 2D panels. Do make sure you have the patch for the Duke, the initial release didnt fully work with MSFS commands, the new turbine Duke works perfect straight out of the box.

http://forum.simflight.com/topic/66139-updated-modules/page__pid__417029#entry417029

Just to be clear FSX doesnt have a modules menu, its called Addons.

Pete not everyones first language is English "Hey there" isn't an insult or shouting its also a way folk greet one another these days. OP go to Windows "folder options" and remove the check mark from the box that says "hide extensions for known file types", you will now be able to see what the real file names were of all those FSUIPC files.

You will find the documentation and manuals in the folder shown below, there is a great deal of information in the manuals and this topic has been covered. *:\....\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC Documents\

"L:Duke_Inverter_Switch" is the inverter switch. 0 = off, 1 = Main, 2 = Standby "L:MW_Reset" = the master warning reset button. Send 1 to turn out the light. "L:ignSwL" = Left ignition. 0 = off, 1 = Auto, 2 = On "L:ignSwR" = Right ignition. 0 = off, 1 = Auto, 2 = On Below is an example Lua I use for this aircraft, for the inverter I only bother with switch positions Main and Off. The ignition switches I only bother with Auto and Off positions. I've not bothered looking for the oil doors at all yet, use the method Peter spoke of above to find those if you can. if ipcPARAM == 1 then LVarSet = "L:Duke_Inverter_Switch" val = 0 if ipc.readLvar(LVarSet) == 0 then val = 1 end ipc.writeLvar(LVarSet, val) end if ipcPARAM == 2 then LVarSet = "L:MW_Reset" val = 0 if ipc.readLvar(LVarSet) == 0 then val = 1 end ipc.writeLvar(LVarSet, val) end if ipcPARAM == 3 then LVarSet = "L:ignSwL" val = 0 if ipc.readLvar(LVarSet) == 0 then val = 1 end ipc.writeLvar(LVarSet, val) end if ipcPARAM == 4 then LVarSet = "L:ignSwR" val = 0 if ipc.readLvar(LVarSet) == 0 then val = 1 end ipc.writeLvar(LVarSet, val) end See the tutorials in the user contributions section of the forum for help on using the above.

It sounds like the OP only has a vanilla install of FSX to me, thats the only time I see a sub 1 minute cold boot load times in FSX even with the OS and FSX on SSDs. Adding an AI traffic package seems to make the biggest increase to loading times for FSX.

The key is not sent to your email address, you have to log into the Simmarket website and look at the "my orders" section and then click on the FSUIPC order you just made, your key will now be visible.

Did you buy FSUIPC3 for FS9 in the past? Maybe that is where the discount is coming from, it does clearly state on the webpage that previous owners of FSUIPC3 who purchased after July 2009 would get a discount when purchasing FSUIPC4 or WideFS7.