Pete Dowson

Okay, but simply running the FSUIPC installer should easily fix that by re-adding the correct entry. There's only the one, in the FSX Modules folder. None other matter. For the FSX installation? The Installer gets the correct FSX path from the Registry. If the Registry is pointing to the wrong place it sounds like you bodily moved FSX without uninstalling and re-installing. That will mess a lot of things up. If you've not done that then somehow your Registry is corrupted. If you mean it goes to the C: drive for FSX.CFG and the DLL.XML file, then this is perfectly cporrect if the C: drive is your Windows drive, as that contains all your settings. I really do need to see the Install log. The very reason it produces an Install log is so that such matters can be resolved quickly and efficiently. There is no point in speculating over what the problem might be when it is probably obviously set out in black and white! If is cannot find FSX.EXE it provides an Explorer-type dialogue for you to find it and select it. If it is not doing that then you are not reporting the actual problem correctly. It is more likely that it cannot find your FSX.CFG file, which should be on the Windows drive. In any case, if the FSX installation cannot be found through the correct registry entries for it, then you will have many more problems from other add-on installers. You would really need to get that fixed. The FSUIPC installer can fix it for you if you find the FSX.EXE via the dialogue. In your original message in this thread you were talking about some message regarding internet explorer and signatures. What happened to that error, the one I didn't recognise? Why is it different now? Regards Pete

By "disappeared" do you mean the FSUIPC entry in the Add-Ons menu is no longer present? If so, can you look in the FSX Modules folder and see if there's an FSUIPC4 Log file with the date and time of the most recent FSX session you've had? If there's no FSUIPC entry in the Add-Ons menu, but it is creating a Log file, then it is most likely a SimConnect problem. Show me the FSUIPC4.LOG file. If there's no log being produced either then FSUIPC4 is not getting loaded in the first place. The most likely cause of that is that your DLL.XML file has been corrupted, probably by something else you tried to Install. If this is the case it might be repaired by running the FSUIPC4 Installer again. If that doesn't help then you can try one of two things: 1) delete the DLL.XML file and re-install FSUIPC4 again. This may mean other add-ons with DLLs will not load, so you might need to do futher re-installs, or 2) show me the DLL.XML file here and I'll try to repair it for you. You will find it in the same folder as your FSX.CFG file. If you don'yt know where that is, show me your FSUIPC4 Install Log (in the FSX Modules folder) and I'll point it out to you. The DLL.XML file can be read into Notepad and pasted as text into a message here. Sorry, "latest" is not very meaningful as it depends where you download from. Please ALWAYS quote version numbers! (Ah, I see you did, later on: 4.57). If there's any sort of problem on the Install I need to see the Install log file, which you should find in the FSX Modules folder. As described in the Installation document, if it doesn't get as far as creating and storing these things into the FSX Modules folder, you can always use the "File" menu on the displayed log Window to save the Install log where you want. When you report error messages you need to be more specific and accurate, please. There's no message I am aware of containing the words you mention you were "given". When you get error messages please find a pencil and paper and write them down. Regards Pete

Do you mean WideFS? PM doesn't use WidevieW. That is a program for linking multiple copies of FS running on different PCs, with the clients used to provide more scenery views. For WideFS there really shouldn't be any settings necessary -- only enabling it on the Server and running WideClient on the clients. Depending on versions of Windows and your WorkGroup names you might have had to put the ServerName and Protocol details in the client parameters, but there's nothing to set or change on the Server. So what was the problem and what did you have to change? If you don't fly on-line then I'd recommend Radar Contact. I've used it for many years and it is excellent. With the free SuperATC program from ItsYourPlane it is even better now, as you can use spoken commands and responses. There are no flaps nor gear on a WideFS Client. The only thing with gear and flaps is the aircraft in flight simulator, and that's running on the Server. If you are instead asking whether you can use joystick buttons or keypresses on the client PC to operate things on FS on the Server, then, yes, of course. Best with buttons -- FSUIPC's Buttons tab will recognise any types of buttons on normal joystick devices, and GoFlight modules, connected to the client. For keypresses you have to do some modifications to the Client INI, as described in the documentation. It is more usual, and easier, to get keypresses sent to client programs when operating buttons or keypresses on the Server. You use KeySend for that. Regards Pete

Yes, sorry. I was thinking of 4.57. Working too hard! 3.962 is latest. Regards Pete

Please don't start new threads for the same subject. The clock sync function works the same for all versions, and only adjusts the seconds, not the minutes. Pete

Please note that, as announced above, version 3.90 is very old and completely unsupported. The currently supported version is 3.97, with an update to 3.972 already available in the Updates Announcement. Pete

You are in the wrong Forum! The install was perfect, no problem. For a no add-ons menu problem it is the FSUIPC4.LOG file you need to show. But please go to me Support Forum. Regards Pete Dowson

If you mean with the Ariane, there's no offsets involved at all. Maybe some of the switches will activate the underlying subsystems and i think that's the only possibility, but that is by using the Lvar macro facilities, or a Lua plug in, not via any FSUIPC offsets. As I said, I could operate the switches that way but I think mostly the LVars simply record the switch positions rather than activate the functions. No, please don't send me anything. I don't think there's much at all on the default FSX aircraft which is amenable to mouse macros. I already told you this! In fact there wasn't much in FS9 either. Microsoft never followed the rules for Gauge programming which they provided for third parties. If you want to see the mouse macro function working with a default FSX aircraft, the only place I remember it working in in the Cessna 172SP. Click on the "Select" or "Ctrl" switches on the clock, or on almost any part of the radio stack (though all of that is really well catered for by regular controls in any case). I think even the push/pull engine controls respond too, and the lights -- in fact all of the lower panel except the fuel selector. Regards Pete

Ah, some facilities I've never heard of! So you can see you are in the correct "mode" and it still doesn't work? You mean the Shift+O? It must surely be an FS control. Doesn't it get logged? Let me try ... ...Yes, it's called "Mouse look toggle". But it doesn't work here, either. Let me try things ... ... Okay. It's "JOYSTICKS=0". Seems that saying there's no joysticks stops the mouse being used like a Joystick too. Probably stops "mouse as yoke" too. [LATER] Yes. Confirmed. It's actually easy to check really. Look in the FSX Menu, "Options-Settings-Controls-Calibration". The "Enable Controllers" checkbox top left IS the CFG "Joysticks" parameter. Enable it there and look in the "Controller Type" drop-down. You'll see not only real joysticks but also "Mouse yoke" and "Mouse Look". So, it looks as if you can't have it both ways. Very short-sighted of that, by Microsoft. They should certainly have separated the mouse use from the joystick use. Pete

The popup won't popup if the structure for the mouse position cannot be found. It means the hook is not being triggered. I don't think the Ariane aircraft use and C/C++ gauge structures. Aren't they all XML gauges? What other aircraft have you tried? Pretty much none of the default FSX aircraft are amenable to mouse macros either. Sorry, no. I did obtain one of the new Ariane 737NG X2 aircraft to test whether it flew better in FSX than my transposed FS9 PMDG 737NG, but I found it wasn't usable without it's 3D-only panel, and I don't use any FS panels at all -- I have a hardware 737NG cockpit, so I only use FSX for flight models and outside views. I did play a little while, seeing if I could assign controls, and I think I found that it was certainly not written in any way that Mouse Macros could work, but it does have a huge number of L:vars. You can see those quite easily by assigning a keypress to the "List Local Panel Vars" FSUIPC control and using it. This is what I got: 186594 Aircraft="Boeing_737_800 Base Pack classic" 186594 Panel includes these local variables: 186594 L:ariane_737VC_standby_power = 0.000000 186594 L:ariane_737VC_p0470 = 0.000000 186594 L:ariane_737_b1135 = 0.000000 186594 L:ariane_737_b1133 = 0.000000 186594 L:ariane_737VC_p0648 = 0.000000 186594 L:ariane_737VC_b0631 = 0.000000 186594 L:ariane_737VC_b0630 = 0.000000 186594 L:ariane_737VC_b0629 = 0.000000 186594 L:ariane_737VC_b0628 = 0.000000 186594 L:ariane_737VC_b0627 = 0.000000 186594 L:ariane_737VC_b0626 = 0.000000 186594 L:ariane_737VC_b0625 = 0.000000 186594 L:ariane_737VC_b0641 = 0.000000 186594 L:737_cowlvalve1_light = 0.000000 186594 L:737_LRvalve_light = 0.000000 186594 L:ariane_737VC_b0618 = 0.000000 186594 L:ariane_737VC_b0617 = 0.000000 186594 L:ariane_737VC_b0616 = 0.000000 186594 L:ariane_737VC_b0615 = 0.000000 186594 L:ariane_737VC_b0614 = 0.000000 186594 L:ariane_737VC_b0613 = 0.000000 186594 L:ariane_737VC_p0612 = 0.000000 186594 L:ariane_737VC_p0611 = 0.000000 186594 L:ariane_737VC_p0608 = 0.000000 186594 L:ariane_737VC_p0610 = 0.000000 186594 L:ariane_737VC_p0609 = 0.000000 186594 L:ariane_737VC_p0607 = 0.000000 186594 L:ariane_737VC_p0606 = 0.000000 186594 L:737_cowlvalve2_trigger_plus = 0.000000 186594 L:737_cowlvalve2_timer1 = 0.000000 186594 L:737_cowlvalve2_trigger_startup1 = 0.000000 186594 L:737_cowlvalve2_light = 0.000000 186594 L:737_cowlvalve2_timer = 0.000000 186594 L:737_cowlvalve2_trigger_startup = 0.000000 186594 L:ariane_737_engantiice2_switch = 0.000000 186594 L:737_cowlvalve1_trigger_plus = 0.000000 186594 L:737_cowlvalve1_timer1 = 0.000000 186594 L:737_cowlvalve1_trigger_startup1 = 0.000000 186594 L:737_cowlvalve1_timer = 0.000000 186594 L:737_cowlvalve1_trigger_startup = 0.000000 186594 L:ariane_737_engantiice1_switch = 0.000000 186594 L:737_LRvalve_trigger_plus = 0.000000 186594 L:737_LRvalve_timer1 = 0.000000 186594 L:737_LRvalve_trigger_startup1 = 0.000000 186594 L:737_LRvalve_timer = 0.000000 186594 L:737_LRvalve_trigger_startup = 0.000000 186594 L:ariane_737_wingantiice_switch = 0.000000 186594 L:ariane_737VC_p0602 = 0.000000 186594 L:ariane_737VC_p0601 = 0.000000 186594 L:ariane_737VC_p0600 = 0.000000 186594 L:ariane_737VC_p0599 = 0.000000 186594 L:ariane_737VC_p0581 = 0.000000 186594 L:ariane_737VC_p0582 = 0.000000 186594 L:ariane_737VC_p0515 = 0.000000 186594 L:ariane_737VC_p0512 = 0.000000 186594 L:ariane_bleedair_sound = 0.000000 186594 L:ariane_737VC_p0516 = 0.000000 186594 L:ariane_737VC_p0517 = 0.000000 186594 L:ariane_737VC_p0514 = 0.000000 186594 L:ariane_737VC_rfan_switch = 0.000000 186609 L:ariane_bleedair_trigger5 = 1.000000 186609 L:ariane_737VC_click1 = -9005.000000 186609 L:ariane_bleedair_trigger6 = 1.000000 186609 L:737_click1_trigger_plus = 0.000000 186609 L:737_click1_timer1 = 36833.277786 186609 L:ariane_bleedair_trigger1 = 0.000000 186609 L:ariane_bleedair_trigger2 = 0.000000 186609 L:ariane_737VC_lfan_switch = 0.000000 186609 L:ariane_737VC_p0589 = 0.000000 186609 L:ariane_737VC_p0592 = 0.000000 186609 L:ariane_737VC_p0590 = 0.000000 186609 L:ariane_737VC_p0593 = 0.000000 186609 L:ariane_737VC_p0588 = 0.000000 186609 L:737_cvalve_trigger_plus = 0.000000 186609 L:737_cvalve_timer1 = 0.000000 186609 L:737_cvalve_trigger_startup1 = 0.000000 186609 L:737_cvalve_light = 0.000000 186609 L:737_cvalve_timer = 0.000000 186609 L:737_cvalve_trigger_startup = 0.000000 186609 L:ariane_737VC_p0552 = 0.000000 186609 L:ariane_737VC_p0554 = 0.000000 186609 L:ariane_737VC_p0553 = 0.000000 186625 L:ariane_737VC_p0558 = 0.000000 186625 L:ariane_737VC_p0557 = 0.000000 186625 L:ariane_737VC_p0556 = 0.000000 186625 L:ariane_737VC_p0555 = 0.000000 186625 L:ariane_737VC_p0539 = 0.000000 186625 L:ariane_737VC_p0538 = 0.000000 186625 L:ariane_737VC_p0509 = 0.000000 186625 L:ariane_737VC_p0492 = 0.000000 186625 L:ariane_737_exit_light = 0.000000 186625 L:ariane_737VC_p0504 = 0.000000 186625 L:ariane_737VC_p0499 = 0.000000 186625 L:ariane_737VC_p0497 = 0.000000 186625 L:ariane_737VC_p0494 = 0.000000 186625 L:ariane_737VC_p0507 = 0.000000 186625 L:ariane_737VC_p0505 = 0.000000 186625 L:ariane_737VC_p0506 = 0.000000 186625 L:ariane_737VC_gauges_light = 0.000000 186625 L:ariane_737VC_b0596 = 0.000000 186625 L:ariane_737VC_b0595 = 0.000000 186625 L:ariane_737VC_b0594 = 0.000000 186625 L:ariane_737VC_p0591 = 0.000000 186625 L:ariane_737VC_b0583 = 0.000000 186641 L:ariane_737VC_p0573 = 0.000000 186641 L:ariane_737VC_p0572 = 0.000000 186641 L:ariane_737VC_b0570 = 0.000000 186641 L:ariane_737VC_b0569 = 0.000000 186641 L:737_1svalve_light = 0.000000 186641 L:ariane_737VC_b0564 = 0.000000 186641 L:ariane_737VC_b0563 = 0.000000 186641 L:ariane_737VC_b0562 = 0.000000 186641 L:ariane_737VC_b0561 = 0.000000 186641 L:ariane_737VC_b0560 = 0.000000 186641 L:ariane_737VC_b0559 = 0.000000 186641 L:ariane_737VC_b0551 = 0.000000 186641 L:ariane_737VC_b0550 = 0.000000 186641 L:ariane_737VC_b0549 = 0.000000 186641 L:ariane_737VC_b0548 = 0.000000 186641 L:ariane_737VC_b0547 = 0.000000 186641 L:ariane_737VC_b0546 = 0.000000 186641 L:ariane_737VC_b0545 = 0.000000 186641 L:ariane_737VC_b0544 = 0.000000 186641 L:ariane_737VC_b0543 = 0.000000 186641 L:ariane_737VC_b0542 = 0.000000 186641 L:ariane_737VC_b0541 = 0.000000 186641 L:ariane_737VC_b0540 = 0.000000 186641 L:ariane_737VC_p0537 = 0.000000 186656 L:ariane_737VC_p0536 = 0.000000 186656 L:ariane_737VC_p0535 = 0.000000 186656 L:ariane_737VC_p0533 = 0.000000 186656 L:ariane_737VC_p0534 = 0.000000 186656 L:ariane_737VC_b0530 = 0.000000 186656 L:ariane_737VC_b0529 = 0.000000 186656 L:ariane_737VC_b0528 = 0.000000 186656 L:ariane_737VC_b0527 = 0.000000 186656 L:ariane_737VC_b0526 = 0.000000 186656 L:ariane_737VC_b0525 = 0.000000 186656 L:ariane_737VC_b0524 = 0.000000 186656 L:ariane_737VC_b0523 = 0.000000 186656 L:ariane_737VC_b0522 = 0.000000 186656 L:ariane_737VC_b0521 = 0.000000 186656 L:ariane_737VC_b0520 = 0.000000 186656 L:ariane_737VC_b0519 = 0.000000 186656 L:ariane_737VC_b0518 = 0.000000 186656 L:ariane_737VC_p0513 = 0.000000 186656 L:ariane_737VC_115AC_power = 0.000000 186656 L:ariane_737VC_rfan_trig = 1.000000 186672 L:ariane_737VC_fan_trig = 1.000000 186672 L:ariane_737VC_p0502 = 0.000000 186672 L:ariane_737VC_p0501 = 0.000000 186672 L:ariane_737VC_p0503 = 0.000000 186672 L:ariane_737VC_p0500 = 0.000000 186672 L:ariane_737VC_b0632 = 0.000000 186672 L:ariane_737VC_b0633 = 0.000000 186672 L:ariane_737VC_b0634 = 0.000000 186672 L:ariane_737VC_b0635 = 0.000000 186672 L:ariane_737VC_b0636 = 0.000000 186672 L:ariane_737VC_b0640 = 0.000000 186672 L:ariane_737VC_b0637 = 0.000000 186672 L:ariane_737VC_b0638 = 0.000000 186672 L:ariane_737VC_b0639 = 0.000000 186672 L:ariane_737_aft_service_door = 0.000000 186672 L:737_fwd_service_door_pos = 0.000000 186672 L:ariane_737VC_p0649 = 0.000000 186672 L:ariane_737VC_p0650 = 0.000000 186672 L:ariane_737VC_b0651 = 0.000000 186672 L:ariane_737VC_b0652 = 0.000000 186672 L:ariane_737VC_p0653 = 0.000000 186672 L:ariane_737VC_b0658 = 0.000000 186672 L:ariane_737VC_b0659 = 0.000000 186672 L:ariane_737VC_b0660 = 0.000000 186688 L:ariane_737VC_b0661 = 0.000000 186688 L:ariane_737VC_b0662 = 0.000000 186688 L:ariane_737VC_b0664 = 0.000000 186688 L:ariane_737VC_b0663 = 0.000000 186688 L:ariane_737VC_b0665 = 0.000000 186688 L:ariane_737VC_b0666 = 0.000000 186688 L:ariane_737VC_b0667 = 0.000000 186688 L:ariane_737VC_b0668 = 0.000000 186688 L:ariane_737VC_b0669 = 0.000000 186688 L:ariane_737VC_b0670 = 0.000000 186688 L:ariane_737VC_b0671 = 0.000000 186688 L:ariane_737VC_b0672 = 0.000000 186688 L:ariane_737VC_b0673 = 0.000000 186688 L:ariane_737VC_p0674 = 0.000000 186688 L:ariane_737VC_p0655 = 0.000000 186703 L:ariane_737VC_p0676 = 0.000000 186703 L:ariane_737VC_p0675 = 0.000000 186703 L:ariane_737VC_p0678 = 0.000000 186703 L:ariane_737VC_p0677 = 0.000000 186703 L:737_2svalve_light = 0.000000 186703 L:ariane_737VC_compass_lightswitch_pos = 0.000000 186703 L:ariane_737VC_b0382 = 0.000000 186703 L:ariane_737VC_b0383 = 0.000000 186703 L:ariane_737VC_p0379 = 0.000000 186703 L:ariane_737VC_p0386 = 0.000000 186703 L:ariane_737VC_p0471 = 0.000000 186703 L:ariane_737VC_b0482 = 0.000000 186703 L:ariane_737VC_b0484 = 0.000000 186703 L:ariane_737VC_b0487 = 0.000000 186703 L:ariane_737VC_b0486 = 0.000000 186703 L:ariane_737VC_b0485 = 0.000000 186703 L:ariane_737VC_b0483 = 0.000000 186703 L:ariane_737VC_b0427 = 0.000000 186703 L:ariane_737VC_b0428 = 0.000000 186703 L:ariane_737VC_b0429 = 0.000000 186703 L:ariane_737VC_b0430 = 0.000000 186703 L:ariane_737VC_b0431 = 0.000000 186703 L:ariane_737VC_b0432 = 0.000000 186703 L:ariane_737VC_b0433 = 0.000000 186719 L:ariane_737VC_b0402 = 0.000000 186719 L:ariane_737VC_b0404 = 0.000000 186719 L:ariane_737VC_b0406 = 0.000000 186719 L:ariane_737VC_b0408 = 0.000000 186719 L:ariane_737VC_b0410 = 0.000000 186719 L:ariane_737VC_b0412 = 0.000000 186719 L:ariane_737VC_b0414 = 0.000000 186719 L:ariane_737VC_b0416 = 0.000000 186719 L:ariane_737VC_b0418 = 0.000000 186719 L:ariane_737VC_b0420 = 0.000000 186719 L:ariane_737VC_b0422 = 0.000000 186719 L:ariane_737VC_b0424 = 0.000000 186719 L:ariane_737VC_b0426 = 0.000000 186719 L:ariane_737VC_b0463 = 0.000000 186719 L:ariane_737VC_b0464 = 0.000000 186719 L:ariane_737VC_b0465 = 0.000000 186719 L:ariane_737VC_b0466 = 0.000000 186719 L:ariane_737VC_b0467 = 0.000000 186719 L:ariane_737VC_b0468 = 0.000000 186719 L:ariane_737VC_b0469 = 0.000000 186719 L:ariane_737VC_b0477 = 0.000000 186719 L:ariane_737VC_b0438 = 0.000000 186719 L:ariane_737VC_b0440 = 0.000000 186719 L:ariane_737VC_b0442 = 0.000000 186734 L:ariane_737VC_b0444 = 0.000000 186734 L:ariane_737VC_b0446 = 0.000000 186734 L:ariane_737VC_b0448 = 0.000000 186734 L:ariane_737VC_b0450 = 0.000000 186734 L:ariane_737VC_b0452 = 0.000000 186734 L:ariane_737VC_b0454 = 0.000000 186734 L:ariane_737VC_b0456 = 0.000000 186734 L:ariane_737VC_b0458 = 0.000000 186734 L:ariane_737VC_b0460 = 0.000000 186734 L:ariane_737VC_b0462 = 0.000000 186734 L:ariane_737VC_b0346 = 0.000000 186734 L:ariane_737VC_b0347 = 0.000000 186734 L:ariane_737VC_b0348 = 0.000000 186734 L:ariane_737VC_b0349 = 0.000000 186734 L:ariane_737VC_b0350 = 0.000000 186734 L:ariane_737VC_b0351 = 0.000000 186734 L:ariane_737VC_b0352 = 0.000000 186734 L:ariane_737VC_b0353 = 0.000000 186734 L:ariane_737VC_b0354 = 0.000000 186734 L:ariane_737VC_b0355 = 0.000000 186734 L:ariane_737VC_b0356 = 0.000000 186750 L:ariane_737VC_b0341 = 0.000000 186750 L:ariane_737VC_b0343 = 0.000000 186750 L:ariane_737VC_b0345 = 0.000000 186750 L:737_1svalve_trigger_plus = 0.000000 186750 L:737_1svalve_timer1 = 0.000000 186750 L:737_1svalve_trigger_startup1 = 0.000000 186750 L:737_1svalve_timer = 0.000000 186750 L:737_1svalve_trigger_startup = 0.000000 186750 L:ariane_737VC_p0740 = 0.000000 186750 L:737_2svalve_trigger_plus = 0.000000 186750 L:737_2svalve_timer1 = 0.000000 186750 L:737_2svalve_trigger_startup1 = 0.000000 186750 L:737_2svalve_timer = 0.000000 186750 L:737_2svalve_trigger_startup = 0.000000 186750 L:ariane_737VC_p0741 = 0.000000 186750 L:ariane_737VC_b0597 = 0.000000 186750 L:ariane_737VC_p0001 = 0.000000 186750 L:ariane_737VC_p0027 = 0.000000 186750 L:ariane_737VC_p0311 = 0.000000 186750 L:ariane_737VC_p0002 = 0.000000 186750 L:ariane_737VC_p0003 = 0.000000 186750 L:ariane_737VC_p0004 = 0.000000 186750 L:ariane_737VC_p0034 = 0.000000 186750 L:ariane_737VC_p0033 = 0.000000 186766 L:ariane_737VC_p0312 = 0.000000 186766 L:ariane_737VC_p0090 = 0.000000 186766 L:ariane_737VC_p0089 = 0.000000 186766 L:ariane_737VC_b0145 = 0.000000 186766 L:ariane_737VC_b0146 = 0.000000 186766 L:ariane_737VC_b0147 = 0.000000 186766 L:ariane_737VC_b0148 = 0.000000 186766 L:ariane_737VC_b0149 = 0.000000 186766 L:ariane_737VC_b0150 = 0.000000 186766 L:ariane_737VC_b0151 = 0.000000 186766 L:ariane_737VC_b0152 = 0.000000 186766 L:ariane_737VC_b0153 = 0.000000 186766 L:ariane_737VC_b0154 = 0.000000 186766 L:ariane_737VC_b0155 = 0.000000 186766 L:ariane_737VC_b0156 = 0.000000 186766 L:ariane_737VC_b0157 = 0.000000 186766 L:ariane_737VC_b0158 = 0.000000 186766 L:ariane_737VC_b0298 = 0.000000 186766 L:ariane_737VC_b0299 = 0.000000 186766 L:ariane_737VC_b0300 = 0.000000 186766 L:ariane_737VC_b0301 = 0.000000 186766 L:ariane_737VC_b0303 = 0.000000 186766 L:ariane_737VC_b0302 = 0.000000 186766 L:ariane_737VC_b0307 = 0.000000 186766 L:ariane_737VC_b0306 = 0.000000 186781 L:ariane_737VC_b0304 = 0.000000 186781 L:ariane_737VC_b0305 = 0.000000 186781 L:ariane_737VC_p0310 = 0.000000 186781 L:ariane_737VC_click = 0.000000 186781 L:ariane_737VC_b0330 = 0.000000 186781 L:ariane_737_b1156 = 0.000000 186781 L:ariane_737_b1151 = 0.000000 186781 L:ariane_737_b1149 = 0.000000 186781 L:ariane_737_b1153 = 0.000000 186781 L:ariane_737_b1148 = 0.000000 186781 L:ariane_737_b1154 = 0.000000 186781 L:ariane_737_b1073 = 0.000000 186781 L:ariane_737_b1145 = 0.000000 186781 L:ariane_737_b1147 = 0.000000 186781 L:ariane_737_b1152 = 0.000000 186781 L:ariane_737_b1146 = 0.000000 186781 L:ariane_737_b1072 = 0.000000 186781 L:ariane_737_b1155 = 0.000000 186781 L:ariane_737_b1150 = 0.000000 186781 L:ariane_737_b1256 = 0.000000 186781 L:ariane_737_b1257 = 0.000000 186781 L:ariane_737_b1258 = 0.000000 186797 L:ariane_737_b1259 = 0.000000 186797 L:ariane_737_b1260 = 0.000000 186797 L:ariane_737_b1261 = 0.000000 186797 L:ariane_737VC_b0159 = 0.000000 186797 L:ariane_737_b1134 = 0.000000 186797 L:ariane_737VC_p0684 = 0.000000 186797 L:ariane_737VC_p0683 = 0.000000 186797 L:ariane_737VC_p0682 = 0.000000 186797 L:ariane_737VC_p0679 = 0.000000 186797 L:ariane_737VC_p0680 = 0.000000 186797 L:ariane_737VC_p0681 = 0.000000 186797 L:ariane_737VC_b0709 = 0.000000 186797 L:ariane_737VC_b0722 = 0.000000 186797 L:ariane_737VC_b0718 = 0.000000 186797 L:ariane_737VC_p0690 = 0.000000 186797 L:ariane_737VC_b0706 = 0.000000 186797 L:ariane_737VC_b0710 = 0.000000 186797 L:ariane_737VC_b0707 = 0.000000 186797 L:ariane_737VC_b0711 = 0.000000 186797 L:ariane_737VC_b0708 = 0.000000 186797 L:ariane_737VC_b0712 = 0.000000 186797 L:ariane_737VC_b0723 = 0.000000 186797 L:ariane_737VC_b0713 = 0.000000 186797 L:ariane_737VC_b0705 = 0.000000 186813 L:ariane_737VC_b0714 = 0.000000 186813 L:ariane_737VC_b0715 = 0.000000 186813 L:ariane_737VC_b0716 = 0.000000 186813 L:ariane_737VC_b0719 = 0.000000 186813 L:ariane_737VC_b0717 = 0.000000 186813 L:ariane_737VC_p0688 = 0.000000 186813 L:ariane_737VC_p0687 = 0.000000 186813 L:ariane_737VC_b0720 = 0.000000 186813 L:ariane_737VC_b0704 = 0.000000 186813 L:ariane_737VC_b0703 = 0.000000 186813 L:ariane_737VC_b0721 = 0.000000 186813 L:ariane_eyebrow_windows = 0.000000 186813 L:ariane_737VC_alt_intv = 0.000000 186813 L:ariane_737VC_spd_intv = 0.000000 186813 L:ariane_737VC_b0113 = 0.000000 186813 L:ariane_737VC_b0115 = 0.000000 186813 L:ariane_737VC_b0117 = 0.000000 186813 L:ariane_737VC_b0119 = 0.000000 186813 L:ariane_737VC_b0121 = 0.000000 186813 L:ariane_737VC_b0123 = 0.000000 186813 L:ariane_737VC_b0125 = 0.000000 186813 L:ariane_737VC_b0127 = 0.000000 186828 L:ariane_737VC_b0129 = 0.000000 186828 L:ariane_737VC_b0131 = 0.000000 186828 L:ariane_737VC_b0133 = 0.000000 186828 L:ariane_737VC_b0135 = 0.000000 186828 L:ariane_737VC_b0137 = 0.000000 186828 L:ariane_737VC_b0139 = 0.000000 186828 L:ariane_737VC_b0142 = 0.000000 186828 L:ariane_737VC_b0143 = 0.000000 186828 L:ariane_737VC_b0144 = 0.000000 186828 L:ariane_737VC_p0109 = 0.000000 186828 L:ariane_737VC_p0110 = 0.000000 186828 L:ariane_737VC_p0111 = 0.000000 186828 L:ariane_737VC_p0112 = 0.000000 186828 L:ariane_737VC_mcp_type = 0.000000 186828 L:ariane_737VC_b0761 = 0.000000 186828 L:ariane_737VC_b0762 = 0.000000 186828 L:ariane_737VC_b0763 = 0.000000 186828 L:ariane_737VC_b0764 = 0.000000 186828 L:ariane_737VC_b0766 = 0.000000 186828 L:ariane_737VC_p0767 = 0.000000 186828 L:ariane_737_forward_galley_flag = 0.000000 186828 L:ariane_737_b1136 = 0.000000 186844 L:ariane_737_b1063 = 0.000000 186844 L:ariane_737_b1064 = 0.000000 186844 L:ariane_737VC_asi_hide = 0.000000 186844 L:ariane_737_galley_lights = 0.000000 186844 L:ariane_737_entry_light = 0.000000 186844 L:ariane_737_work_light = 0.000000 186844 L:ariane_737_ceiling_light = 0.000000 186844 L:ariane_737VC_cockpit_door = 0.000000 186844 L:ariane_737VC_emergency_power = 0.000000 186844 L:ariane_737_extend_cover = 0.000000 186844 L:ariane_737VC_airstairs_extend = 0.000000 186844 L:ariane_737_stairoper_light = 0.000000 186844 L:ariane_737_grdsrv_bus = 0.000000 186844 L:ariane_737VC_main_door_handle = 0.000000 186844 L:ariane_737VC_main_door_pennant = 0.000000 186844 L:ariane_737VC_fwdservice_door_handle = 0.000000 186844 L:ariane_737VC_fwdservice_door_pennant = 0.000000 186844 L:ariane_737_retract_cover = 0.000000 186844 L:ariane_737VC_airstairs_retract = 0.000000 186844 L:ariane_737_standby_light = 0.000000 186844 L:ariane_737_window_light = 0.000000 186844 L:ariane_737_wingtip = 0.000000 186844 L:ariane_737VC_28AC_power = 0.000000 186859 L:ariane_737VC_wblock = 0.000000 186859 L:ariane_737VC_p0508 = 0.000000 186859 L:737_retract_LL_pos = 0.000000 186859 L:ariane_737_b1335 = 0.000000 186859 L:ariane_737_p1140 = 0.000000 186859 L:ariane_737_GPU_door = 0.000000 186859 L:ariane_737VC_pins = 0.000000 186859 L:ariane_737VC_ecovers = 0.000000 186859 L:ariane_737_w1_left = 0.000000 186859 L:ariane_737_w2_left = 0.000000 186859 L:ariane_737_w3_left = 0.000000 186859 L:ariane_737_w4_left = 0.000000 186859 L:ariane_737_w5_left = 0.000000 186859 L:ariane_737_w6_left = 0.000000 186859 L:ariane_737_w7_left = 0.000000 186859 L:ariane_737_w8_left = 0.000000 186859 L:ariane_737_w1_right = 0.000000 186859 L:ariane_737_w2_right = 0.000000 186859 L:ariane_737_w3_right = 0.000000 186859 L:ariane_737_w4_right = 0.000000 186859 L:ariane_737_w5_right = 0.000000 186859 L:ariane_737_w6_right = 0.000000 186859 L:ariane_737_w7_right = 0.000000 186859 L:ariane_737_w8_right = 0.000000 186859 L:map_ZoomStep = 0.000000 186875 L:map_ZoomFactor = 0.000000 186875 L:MapInit = 0.000000 186875 L:LayerAirports = 0.000000 186875 L:LayerAirspaces = 0.000000 186875 L:LayerTerrain = 0.000000 186875 L:LayerVORs = 0.000000 186875 L:LayerILSs = 0.000000 186875 L:LayerNDBs = 0.000000 186875 L:LayerLowAirways = 0.000000 186875 L:LayerTags = 0.000000 186875 L:LayerCompass = 0.000000 186875 L:LayerIntersections = 0.000000 186875 L:LayerRangeRings = 0.000000 186875 L:VehicleObjectDetail = 0.000000 186875 L:Filter = 0.000000 186875 L:ariane_737_random = 0.000000 186875 L:ariane_737_b1160 = 0.000000 186875 L:737_trigger_plus = 0.000000 186875 L:737_timer1 = 0.000000 186875 L:737_trigger_startup1 = 0.000000 186891 L:737_timer = 0.000000 186891 L:737_trigger_startup = 0.000000 186891 L:737_trigger_fs_door = 0.000000 186891 L:737_timer_fs_door1 = 0.000000 186891 L:737_trigger_fs_door_startup1 = 0.000000 186891 L:737_timer_fs_door = 0.000000 186891 L:737_trigger_fs_door_startup = 0.000000 186891 L:ariane_737_p1040 = 0.000000 186891 L:ariane_lib_737_airstairs_top = 0.000000 186891 L:ariane_737_p1039 = 0.000000 186891 L:ariane_737_b1161 = 0.000000 186891 L:dict_737_rudder_freeplay = 0.000000 186891 L:ariane_lib_737_airstairs = 0.000000 186891 L:ariane_737_c1322 = 0.000000 186891 L:ariane_737_c1323 = 0.000000 186891 L:ariane_737_c1324 = 0.000000 186891 L:ariane_737_c1325 = 0.000000 186891 L:ariane_737_c1320 = 0.000000 186891 L:ariane_737VC_HUD_screen = 0.000000 186891 L:ariane_737_b1071 = 0.000000 186891 L:ariane_737VC_p0025 = 0.000000 186891 L:ariane_737VC_p0039 = 0.000000 186891 L:ariane_737VC_p0095 = 0.000000 186891 L:ariane_737VC_p0028 = 0.000000 186891 L:ariane_737VC_flaps_pos = 0.000000 186891 L:ariane_737VC_p0053 = 0.000000 186891 L:ariane_737VC_p0091 = 0.000000 186891 L:ariane_737VC_p0685 = 0.000000 186891 L:ariane_737VC_p0689 = 0.000000 186891 L:ariane_737VC_p0082 = 0.000000 186891 L:ariane_737VC_p0462 = 0.000000 186891 L:ariane_737VC_p0345 = 0.000000 186891 L:ariane_737VC_p0385 = 0.000000 186891 L:ariane_737VC_p0043 = 0.000000 186891 L:ariane_737VC_p0030 = 0.000000 186906 L:ariane_737VC_FO_check = 0.000000 186906 L:ariane_737VC_p0478 = 0.000000 186906 L:ariane_737VC_p0479 = 0.000000 186906 L:ariane_737VC_p0032 = 0.000000 186906 L:ariane_737VC_p0343 = 0.000000 186906 L:ariane_737VC_p0384 = 0.000000 186906 L:ariane_737VC_p0074 = 0.000000 186906 L:ariane_737VC_p0656 = 0.000000 186906 L:ariane_737VC_p0035 = 0.000000 186906 L:ariane_737VC_p0341 = 0.000000 186906 L:ariane_737VC_p0103 = 0.000000 186906 L:ariane_brake_pressure_flag = 1.000000 186906 L:ariane_brake_pressure = 100.000000 186906 L:ariane_hyd_pres_flag = 0.000000 186906 L:ariane_no_alt_brakes = 0.000000 186906 L:ariane_737VC_cap_check = 0.000000 186906 L:ariane_737VC_t0654 = 0.000000 186906 L:ariane_737VC_p0654 = 0.000000 186906 L:ariane_737VC_p0657 = 0.000000 186906 L:EmergencyThrottleInUse = 0.000000 186906 L:Engine1ThrottlePosition = 0.000000 186906 L:LastLandingLightPosition = 0.000000 (Scroll that list to see how enormous it is!) Now, by using the supplied Lua plug-in "Log Lvars" you can get a real-time display of these as they change, so by flipping switches etc you can find out which LVar is which. But, I remember trying this to find a few, and then writing those Lvars with macros (or with a Lua plug-in), and, though I could get the visible switch to operate on screen that way, the underlying system in the aircraft didn't operate. So, I concluded, this aircraft is not designed in any way amenable to the use of hardware. I was in touch with a chap in Ariane's team and mentioned this to him, that they ought to consider doing something about this. I've not heard anything though and suspect that the extra sales they think they'd get wouldn't be worth the effort. There's a spurious value being seen then. That was proven to have no effect, probably because the cause was not in how FSUIPC was resetting its values. You'll notice there's no mention of it anywhere now. Instead I implemented this (as listed in the 4.57 History document), which is much more effective: If you are still seeing spurious values even after the first few are ignored, something really odd is going on in your drivers which I doubt i could deal with at all without wrecking normal use. What is the real problem, the one upsetting you so? Are you getting incorrect actions when flying? Incorrect readings from a reset driver won't matter if they only occur when you are going into FSUIPC options, surely? Are you doing such things whilst flying? If you want help with anything like that I'd certainly need more information, but you also have to explain what's troubling you. The information I'd need include (1) The FSUIPC4 INI file (2) An FSUIPC4 log of the incident with Axis Event logging (3) A full blow-by-blow description of what you are doing, as related to the period of the Log, step by step. There is absolutely no way that FSUIPC can "invent" values coming from your axes. If a value arrived indicating "full flaps", then that is what you'll get. Pete

The FS CFG file? Sorry, I don't know anything about mouse operations there. I don't think it has any influence. But panning and zooming are virtual cockpit operations, aren't they? Perhaps you are in 2D cockpit mode? Use the keyboard control to switch. "A" isn't it? Or perhaps "S". I never remember.. None of my software knows anything about the mouse. Well, except for the facility to use the mouse wheel for elevator trim. It most certainly cannot interfere with or affect mouse operations. Regards Pete

Good. Thanks for letting me know! Regards Pete

Okay, I had time this morning to read through the whole thread to work out what you were talking about. I assume that this is the part relevant to your question: Now I know it looks like I could, if warranted, increase the default for the maximum N1% value from the 90% it states here, but if I did do so I'd be worried that some other users could just possibly be relying on this being defaulting at 90% (After all, perhaps 90% is okay for some aircraft but not others? This is precisely why they are only default values and not fixed). Even if you are not writing a program to modify the values, and only using the built-in test controls offered by FSUIPC for assignment to buttons or keys, you could add, to that button or keypress programming, an "Offset Word Set" control to write the increased value you require to the relevant offset. Since the maximum N1% goes into Parameter 1, bytes 20-21 of the speed control block starting at offset 0730, the WORD offset to be changed is 0730 + 14 (hex for decimal 20). i.e. 0744. So, use "Offset Word Set" with offset x0744 and the parameter set to, say, 97% of the N1 max of 16384: in other words 15892 (or x3E14). Noting this statement in the document: you could experiment with smaller or larger values, "on the fly", to find your ideal value. Try it and please let me know how you get on. Regards Pete

Good. Thanks for confirming. Pete

Whether mouse macros will work or not doesn't depend on anything related to visual design, but the way the gauges are programmed. Gauges developed in C or C++ using the older-style gauges SDK from Microsoft, and using the standard MS-supplied macros, should always be amenable to mouse macros, because it is the structures in the code created by those macros which allow the hooking which the macros perform. The L:vars accessible via additional Lua library facilities tend to be the way that gauges written in XML keep track of their specific and local switches. Sometimes, the way they are written, changing those values does actually change the thing the switch operates, but it is just as likely that the values only denote the way the screen image of the switch is shown, and not the subsystem circuit it operates. So that is rather pot luck I'm afraid. There's no reason why C/C++ gauges shouldn't use L:vars too, by the way. In general, there is no easy way to know if something is going to work without actually trying it. No, that's entirely separate. Nothing in my software cares about screen positions. If you were using something like "Key2Mouse" then TrackIR would give you a real problem because nothing will be in the same place on screen at any two times. Regards Pete

Is it still mentioned in the Readme? Oh dear. I'll remove the reference. The guide isn't relevant these days. Please email me about this. petedowson@btconnect.com Email about this too. Regards Pete

Ah, good. Well done! Pete

I didn't say updating FSUIPC would "fix" anything, because there's nothing to fix. I needed you to update because I don't support old versions. As I pointed out, you had the keypress "G" assigned in FSUIPC to at least two of your Buttons. Until you delete those or re-program them they will continue to send "G" to FS whenever you press them. It seems you aren't reading my replies. I don't see any point in you showing me log files if you don't read my analysis of them. And what do you think that should show? You don't even say what the log is of. You still haven't bothered to enable Event logging as I suggested. All I can see from this log is that you appear to have reprogrammed one of the affected button (0,5) to send "Shift+2" instead of "G": There's no "G" being sent in this log, whilst there was last time. I'm not sure what you are asking of me now. I think I've helped all I can. If you still don't know what you are doing, why not simply start again, delete your FSUIPC INI file, as I suggested? If you want anything else from me please enable the logging options I suggest and tell me exactly what your logs are supposed to show you doing. Regards Pete

Thanks for the information. That reference was from another user and is about 5 years old now. However, I'll add a note to the WideFS documentation. Note that a much easier way to enable or disable Services, and set their loading modes, is to use the Services section of your computer’s "Manage” facility—right click on “My Computer” and select “Manage”. Regards Pete

This is with FS already running and ready to fly? If so you have something wrong. What do the logs say? Even 40 seconds for the "window" to appear makes no sense -- it's the first thing it does, so it must be taking that long to load from your disk. And it is only a small programme! Check the Log files, both Server and Client. That's what they are for. Pete

What I don't understand is that you claim to have tested without FSUIPC and still had this "ghost" GEAR operation. Yet clearly you have at least two FSUIPC assignments of buttons to send a "G" keypress, the one I already pointed out: 6=P0,8,K71,8 (keycode 71 is 'G'). and the one operated here at the end of the Log extract you posted You have evidently made these aircraft-specific assignments and then forgotten them? If your FSUIPC assignments are all in a mess and you cannot work out what you've done, I recommend you delete the whole INI file and start again. Regards Pete

Please update your copy of FSUIPC. See the Updates and other goodies announcement above. Pete

First, version 3.82 is very very much out of date. I cannot support old versions. Current is 3.96, and there's a 3.962 in the Updates Announcement above. Please read the Announcements some time -- there's one which lists supported versions. Always make sure you are up to date before asking for support. This line: 36223 6=P0,8,K71,8 shows button 8 on Joystick 0 is assigned to the "G" key. Is that your so-called rogue key? You need to enable Event logging to see the controls being sent. Please make sure yto update to a supported version before coming back. Pete

My name is actually Dowson, not Dawson, as shown in the name of this forum. You need to find a GPS program to put on your other PC. If it interfaces to FSUIPC you don't need to use GPSout in any case, and WideFS normally needs no configuring to extend the FSUIPC interface to another PC, so no explanation of that is really necessary. At most there might be a few lines in the User Guide to read, the bit that says it is important to read. The name "GPSout" is intended to mean "output data from FS just as if it is a GPS". In other words it makes the FS PC look like a GPS to an external program running, for example, a moving map program, just as you might drive a moving map program from a real GPS. i'm afraid I do not know of any GPS emulations which run separately from FS. They all seem to be FS gauges, which have to be run inside FS. The best you could do with those is undock them and drag them onto a separate screen on the same PC. None of my software has anything to do with that. Pete

Really? After all I've changed in FSUIPC 3.962? I will certainly need more information. i see no way for that to occur now! Pete