Andydigital

When you unplug a device and plug it back in again into a different port FS automatically generates defaults settings for the device again, even if you don't want it to, so if I were you I would check that the assignments really have been removed in FS.

Your welcome, thanks for the update.

The PIC737XHelper section is corrupted, its also stopping FSUIPC from being listed properly. I've removed the offending PIC737X section and fixed the rest of the dll.xml it should be fine now. I would have fixed the PIC737 section as well but I have no idea what the name of the dll is or where its located, you will have to either reinstall that or see if you can find out what the info should be from somewhere else. [Later] I've fixed the 737 section now as well just copy and paste the whole lot to your dll.xml and it should be all working now. <?xml version="1.0" encoding="Windows-1252"?> Launch dll.xml False False Object Placement Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll Traffic Toolbox True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll Visual Effects Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll Level-D Simulations False False Modules\LVLD.dll FSWidgets EFBFSX False False Modules\FSWidgets\EFBFSX\EFBFSX.dll FeelThere PIC737X Helper False FeelThere\B737\PIC737XH.dll FSUIPC 4 False Modules\FSUIPC4.dll

I beta test for HIFI and I've never had any reconnecting problems in any build of ASX, ASA or ASE after shutting down FSX and restarting it (well not attributable to VRInsight stuff anyway, it was a problem in early ASA testing but we squished that bug a long long time ago and there was no error message, it just wouldn't connect until you restarted ASA), even with all my VRInsight gear going at once, I would guess its something specific to guenseli's PC.

1. First go to here and download the updated installer; http://www.schiratti.com/dowson 2. Then go to the thread shown below and download the latest interim update for FSUIPC3 or FSUIPC4 depending on which version of FS you are using. viewtopic.php?f=54&t=74352 3. The FSUIPC.dll or FSUIPC4.dll interim update needs placing in the "Modules" folder which is inside your main Flight Simulator program folder. Do make sure you update with the installer from step 1 before follow step 3 though.

If you want any form of support then Pete will insist that you update to the latest versions anyway. I don't see the problem with updating, its not like it is going to cost you anything anyway, all future (type i.e. 3 or 4) updates are free once you have initially purchased a licence for FSUIPC.

That probably true Pete but I doubt it would make much difference with views, its not like the user would be furiously changing views 10's of times a second. Least the OP knows what to look for now anyway :wink:

EZdok does now allow you to use the default S and Shift + S commands to move through different view categories and A and Shift + A sub views. Just make sure you have version 1.14 I believe its called and you also have to remove those key definitions from the FS control menus. Hopefully that will make your code a little simpler. Also to work with Track IR and EZdok why don't you just send two commands with one joy button press, you can either do this by using the two options within the FSUIPC GUI i.e. one command (key press) on press of the joy button and the other command (key press) on release of the joy button. You could also edit the FSUIPC ini directly to send two commands (key presses) just on a press of the joy button if you wish.

Just program the buttons to send key presses. "S" and "Shift + S" is what you require I think as this changes view categories. "A" and "Shift + A" changes to different views within a category.

Off topic, but get 'Foxit Reader' instead, its free and loads in a fraction of the time Adobe does, and it can do everything Adobe reader does, I was so impressed with it that I bought the pro version to say thanks even though I didn't really need it.

I presume if you press shift R with the keyboard it doesn't work either? If not then you have a couple of options at least, I think; 1. Use the FSUIPC mouse macro facility if Wilco's 737 panels are amenable to them, see the manual for details, its in the FS Modules/documents folder. 2. Wilco should have supplied a key to trigger this simple task surely, maybe it would be better to find out if it is possible to assign a key or not to this function, I'd be surprised if you cant, but then again it is Wilco we are talking about here.

I've no idea what corrupted it, but if you are saying that you used some utility to try to repair it and that the zip you uploaded was the result of the repair, then I would say stay well away from that utility as it's useless and doesn't work at all, lol.

Hi Bruce, OK I think the attached should be fine now, there were at least 4 errors in it. RepairedDLLxml.zip

The forum does allow .zip attachments I've just tested it, so please use that method in the first instance its easier all round.

No the best thing to do is zip up the dll.XML that doesn't work and attach it to your next post, then I or someone else in the know will take a look at it for you.

No you do not have to do it all again, the file FSUIPC.ini is where all your settings are stored and it will remain unchanged when you upgrade versions. If you want to don your tin foil hat and be absolutely certain that you don't loose your settings you can make a back up of the ini file and store it in another location for safe keeping if you wish, it really isn't necessary though.

Sorry I've just realised what you really meant, I thought you were talking about the FSUIPC message window, when in fact you were talking about the FSUIPC GUI. All you need to do is download the latest version and this problem will go away, Pete fixed this quite some time ago now so you must be using an unsupported version. Download links for the latest version are in the announcement posts at the top of this forum area, the post is called 'Updates and other goodies'.

Click and drag on the edge of the window to make it bigger, that works for all the FSUIPC windows I've ever used in FS9/X

I assume you missed the part where I said you only have to go through this large setup process once, then its just a case of saving the controls setting file for future use so that you do not have to go through this whole process again. And I'll repeat it yet again just in case you missed it the second time, I was offering an alternative method to Cathy, and she had clearly removed the hat switch as an assignment from within FS and I was telling Cathy how she may find it easier to just reassign it again rather than having to use your overly complex method for a beginner.

I hope you didn't think I was calling you insane, what I meant was that it would drive me insane having to set my hat switch up like that when there was no need to :)

I've no idea why you find it necessary to use such a condescending tone with me, its not appreciated, some of my comments were made tongue in cheek and I was trying to help. When is a hat switch not a hat switch? when it appears as four separate buttons instead, Saitek hat switches can be setup via its drivers/software to appear as a 4 or 8 way hat and even as separate buttons instead if you so wish. Some really cheap joysticks and game-pads don't even have a true hat switch, its just 4 separate buttons arranged in a cross shape. I see no reason at all to disable joysticks completely in FS, it always makes sense to at least leave the HAT switch assigned in FS and I'm sure Pete will agree with me on this point. You only need to assign everything once in FS and this includes removing the assignments you do not want for other devices (don't forget slew mode too), once you are happy with it make a safe backup of the controls setting file for future use after a reinstall or after FS decides that it knows better than the user and reassigns everything back to default again for a newly connected device. If it does this simply copy the file back again and you are back to the way you like it. I think you may even be able to mark the file as read-only which should stop FS making a mess of things but I've never needed to try this for myself. I was offering Cathy a simpler alternate and you seem to concur as you made the point that Cathy appears to be a newbie (your words) and I'm pretty certain everything you said went completely over her head, no offence meant Cathy.

I was only talking about assigning the Hat Switch on the Saitek yoke from within FS, if it really appears as a hat switch in windows then it is a simple matter of assigning it in the FS controls interface which takes about 10 seconds to achieve if you have hands and eyes. If the hat switch appears as just 4 buttons then its not so simple as you have pointed out. Assigning the Saitek throttle quadrant to send F2 when the levers are pulled to the reverse detent (which is a switch not an axis) is also very easy to assign in FS or FSUIPC, and also only takes a very short time to achieve.

Or just assigned it in FS like any normal sane person does, which will take all of about 10 seconds :D

Hi Steve, Yes that's correct. And yes you are correct again.

This is resolved now Pete :wink: