-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
FSUIPC und externe dlls
Pete Dowson replied to BlueLiquidCell's topic in FSUIPC Support Pete Dowson Modules
If you are using the static FSUIPC interface library, you'd need to export the variables and procedures defined there so that the DLL can call them. If you combined the library in both the main EXE and the DLL, you have two separate copies of everything, and the one won't have the connection made by the other. The easiest way out of this is to only have the library bound into the DLL, and add functions in the DLL to do your FSUIPC Open and Close calls which you then call from the EXE. If you don't do this you'll need to take the source of the library and work out your own way of exporting the needed variables. You cannot have two separate copies and expect them to operate together, they don't know each other. Regards Pete -
FSUIPC und externe dlls
Pete Dowson replied to BlueLiquidCell's topic in FSUIPC Support Pete Dowson Modules
I'm assuming this is a DLL loaded by your main program, not an FS loaded DLL? If so I have no idea how you've organised everything, so I can't really comment, but it sounds as if the DLL isn't accessing the same variables defining the link as the main program. It is probably best, in any case, do put all of the FSUIPC access code in one place, in the DLL presumably, including the static library if you are using it. Why not use the Debugger which comes with whatever development system you are using? All the code is in your program, so you should easily be able to track the problem down. And even if you are using the pre-compiled LIB files from the FSUIPC SDK the full source is also provided, so you can trace through that too if you wish to compile it in debug mode. Regards Pete -
Key assignments aren't any problem, and optional in any case. What I find more difficult is simply setting all the cameras up in the first place. I keep forgetting to turn off editing mode before moving the mouse back to save a view -- so destroying what I just set up! But once everything is set and working, it's a dream. Regards Pete
-
No. Sorry. I use EZCA (http://simflight.com/2010/03/18/ezdok-camera-ezca-for-fsx/) for such things. Else you could risk re-enabling the controllers but making sure nothing is assigned in the lists. The only problem really then is sometimes FS can unaccountably reassign things automatically. I think it main does that when it thinks the device is a new connection. You might be able to stop it auto-assigning by removing or editing its Devices CFG file. Regards Pete
-
This looks like the well-known SimConnect validation check bug. It is not that frequent but it is very difficult to get around when it happens. It seems to be timing dependent, but once you have it one a PC it tends to be the same on that PC unless you change the SimConnect configuration around. FSUIPC4 really hasn't got much say in it because it happens before it is even running. Microsoft did try to fix it, but only succeeded in making it less common than it used to be. Once FSUIPC4 is actually loaded and listed in FSX.CFG as 'trusted' then you don't get the problem any more because SimConnect doesn't repeat the same clashing validation calls into Windows. There are two things you can try, in either order. First is to see if the very latest FSUIPC (4.634 from the Download Links sub-forum) has sufficiently different timings to get around the problem. This is rather unlikely as it would only be the size which made a difference there. The other is to temporarily stop all other SimConnect clients from loading at the same time, This only needs doing once, to get FSUIPC4 loaded and trusted. To do this find the EXE.XML (if there is one) and DLL.XML files -- in the same folder as your FSX.CFG file. Rename them, say as My EXE.XML and My DLL.XML. Then run the latest FSUIPC4 installer, which you can download from this link: Install_FSUIPC4634.zip and run FSX. When that proves okay, close FSX and go back to delete the new DLL.XML which would have been generated, and rename your copies back. Note: if you don't know where to look for the XML files, look in the FSUIPC install log in your FSX Modules folder. It will tell you where it found the FSX.CFG file. That's where you'll find the XMLs. Regards Pete
-
No, they just reload the settings -- so you can make manual changes to the settings file (FSUIPC INI file) and have them take effect without having to reload FS. To delete all your settings and start again simply delete the FSUIPC INI file from the FS modules folder. Do this before loading FS and FSUIPC will general a new, default, settings file. Your registration will remain intact. Regards Pete
-
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
Good! That's really pleasing. I have no idea what the original problem was on your system, but this is the best all round solution in any case, and I think it is what I intended in the first place. That was a few years ago now and it's all a blur! ;-) Thanks for testing and confirming. Best Regards Pete -
PFC Throttle Qaudrant and Wilco A380 V2
Pete Dowson replied to phil mitchell's topic in FSUIPC Support Pete Dowson Modules
The "ThrottlleNSet" controls are probably being ignored by the add-on Airbus. Try assigning to the Axis ThrottleN set controls, as I suggested! Sorry, what is this part about? You seem to have changed the subject. And I don't understand why you are using "ignore axis" nor what "level" means in this context. Pete -
FSUIPC crashes in MP but is fine in SP
Pete Dowson replied to Ace927's topic in FSUIPC Support Pete Dowson Modules
FSUIPC is in no way related to anything to do with multiplayer. It sounds like a SimConnect problem -- both use SimConnect quite extensively. Without any information, and you supply none, I can't even really hazard a guess as to what is happening. You don't give any details of which module is actually crashing, or the address, or the Windows crash code, though even with all those I am unlikely to be able to fix things for you. Re-installing FSX appears to be the worst possible thing you can do to FSX, mainly because the Side-by-Side installation of SimConnect appears not to be de-installable tidily, and re-installation corrupts things. I have no answer -- I spent many hours trying to trace through the assorted links through the registry and other files to work out whether I could write a program to rectify SimConnect installation errors, but it was far too tangled, especially on Vista and Win7 (with XP I would have stood a good chance). In the end often the only way is a Windows re-installation, unless you can roll back to a good restore point before the first FSX installation. Regards Pete -
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
I'm not doing any changes at all till I learn of your results with the correct Installer. Regards Pete -
Over writing Acceleration body?
Pete Dowson replied to sparouty's topic in FSUIPC Support Pete Dowson Modules
Well your value is most certainly written to Simconnect: 88172 WRITE0 3070, 8 bytes: 95 77 E6 9D 79 67 30 C0 .w..yg0. 88172 SimWrite[812]: 3070="ACCELERATION BODY Z", DDef=0000000E, Ref=2359, Size=8 [dbl=-16.404199] but it isn't used, or is immediately overridden: 88203 Monitor IPC:3070 (FLT64) = 0.54204174 88203 SimRead: 3070="ACCELERATION BODY Z" FLT64: 0.492239709921 Seems that something changed by SP2 version of Simconnect, because I think folks confirmed it worked in the original. Seems I'll need to change my documentation to reflect what SimConnect now does (or rather doesn't do. Sorry. I've not better news. Pete -
You've probably got the options to to avoid system and hidden files and folders. Not directly. It depends on your operating system, your logged in name and the way you installed FSX. But if you can locate the FSUIPC4 Install log in the FSX Modules folder, look in there. It tells you where it found FSX.CFG. You know the path to your FSX folder? If not take a look to see where it was installed. If you know it, put it into the file where it says -- that's what "replace" means -- change one thing for another. I don't know how else to express it. Like changing the t in "Pete" to an 'r'' making "Pere". See -- replace? In that case just check that it does the same as the one I ask for and if not replace it or edit it to do so. Pete
-
Okay. I don't know what TrafficX is doing, but it seems top clobber SimConnect good and proper. Maybe it is just a clash of two heavy Simconnect users trying to do things at the same time. But it's horrible, whatever. The problem is much more than the simple thing of WideFS not getting started. FSUIPC is not getting wads of data that it needs. It could affect all sorts of FSUIPC client applications. I think I need a little more information. Remove those lines in the FSUIPC4.INI file, but please get me a SimConnect log. See the FAQ subforum here -- there's a thread which shows you how to do that. Again, just run things up to the point you are sure WideServer won't start, then Zip the resulting SimConnect log file and email it to me, please. One more thing. Do you think you could find the DLL.XML file and paste it here, please? It's in the same folder as your FSX.CFG file. Thanks, Pete
-
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
Ooops! This isn't the Installer I wanted you to try. It's the original one for 4.60a. The new one installs 4.634. I'll check out wwhat went wrong with the link and let you know. Sorry for wasting your time! [LATER] Okay. It's this damned new Forum software. I don'yt think I'll ever get used to it. No matter what you do to links you have to invoke a special facility which changes the ACTUAL link data hidden underneath. I keep stumbling over this. Try this one (I fixed the previous one too): http://fsuipc.simflight.com/beta/Install_FSUIPC4634.zip Regards Pete -
Flap settings w/detentes
Pete Dowson replied to bradrcfii's topic in FSUIPC Support Pete Dowson Modules
You probably need to calibrate each detente a little more generously. Give the earlier detentes more space on the axis than the later ones. Regards Pete -
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
Yes please. Not PM, please. Just drop me a line at petedowson@btconnect.com. Regards Pete -
Over writing Acceleration body?
Pete Dowson replied to sparouty's topic in FSUIPC Support Pete Dowson Modules
I don't know. Could you enable IPC write logging, and also add 3070 as a double to the Monitor (right-hand-side of the Logging tab -- check 'normal log'), then reproduce the problem and show me the log? As far as I know those variables are writeable via SimConnect, though I don't know if they actually take effect as you might desire. Regards Pete -
Perhaps you are picking up the wrong file, or in the wrong folder? Check the date/time on the file, in Explorer, before picking them. There may also be older copies of the log with a "0" appended, like "wideclient0.log". But those would be properly finished, not like the WideClient log you showed. Maybe, if WideServer isn't getting started, it isn't creating a log either, and so you are never finding one which is applicable. If so this is a clue in itself. WideServer only starts when FSUIPC knows for sure that FSX is "ready to fly". For that to happen SimConnect has to have sent certain events to FSUIPC. Could you please set FSUIPC to do some extra logging. This should show me what is happening, assuming it is never "ready to fly". In the FSUIPC4.INI file add the follwing to the [General] section: Debug=Please LogExtras=1025 This will Log a huge amount of stuff, so just run FSX long enough to be sure WideServer isn't going to start. Then Zip the FSUIPC4 log (only -- don't bother with the others) and send to petedowson@btconnect.com. Thanks! Don't forget to remove those lines afterwards or you'll get really huge log files being produced! Regards Pete
-
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
You didn't need to delete anything. You can run the Installer as often as you like. It will not overwrite anything timestamped later, but does check that everything is correct. Well, I'm completely at a loss. It seems Windows is actually somehow capable of lying about the current user! That's incredible! You'd think that loads of things would go wrong! :-( If and when you have time, could you download and try the new installer version, which tries to install for all users. The link is: http://fsuipc.simflight.com/beta/Install_FSUIPC4634.zip Hopefully this will work properly and I can forget about your Win7's deceitfulness ;-) . Otherwise I shall have to add some code to get more information. Thanks for helping! Pete -
I thought the problem was that the Server didn't appear to start? It's the log of that I really need to see. In this batch of files you have a WideClient session running on the 17th which, as you say, did not connect -- at least in the time before you grabbed the log. Unfortunately you didn't close WideClient beforehand, so it isn't complete. But, and here's the problem and why I'm not getting anything useful, the WideServer log is from the 20th, not the 17th like the WideClient log, and most certainly does show a successful connection: So, still no progress I'm afraid. :-( Regards Pete
-
Flap settings w/detentes
Pete Dowson replied to bradrcfii's topic in FSUIPC Support Pete Dowson Modules
You are using the flap lever in reverse. The minimum IN value needs to be lower than the maximum. That's what minimum/maximum mean -- smallest and biggest. If you want to use the lever the other way round, as on a real aircraft (where max flaps is full back), and not like, say, a throttle (where max is full forward) you need to reverse the axis BEFORE you calibrate. You can do that in the calibration section by checking the "REV" check box. In fact that is exactly what it is for. Regards Pete -
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
That's not really the point. I need to understand what is going on. That cannot be so. The installer obtains the current user name from Windows using a specific call to get it, and it got 'admin' as shown here: I've checked the call used and it is explicitly specified, in Microsoft documentation, as obtaining the current user's AppData folder path (CSIDL_APPDATA). I think it gets this from the CURRENT_USER sections of the Registry. If it did not do this I would have by now been inundated with support requests because it wouldn't have installed correctly on anyone's PC. As it is it works here on XP, Vista, Win732-bit and Win7 64-bit. No. I have tested on Win7. My main development system is Win7, as is my main Simulator PC. No. The installer automatically gets "elevated administrator" rights by virtue of being an installer. That cannot change the current user. It operates like all other installers, and I don't know any which get the current user wrong. Regards Pete -
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
Yes, that would be the reason. It can happen. I've added a fix for that in a later version of the Installer, but that version isn't released yet. Sorry, I don't know how that's possible, as it picks up the current user's name -- it doesn't invent the name "admin" to find. Please show me the installer log illustrating this peculiar behaviour, as it makes no sense to me. I install as user 'Pete' and the current installer (the same one you have, before I apply the change I mentioned in the message above after [LATER]), that's all it looks at. There's no way it knows about "Admin", nor looks for it -- at least not until i release the next version which will find both "admin" and "jacob". There's only one version. Registration buys you the user facilities. All of the application facilities are licensed to the respective applications, and free for access by freeware. Regards Pete -
FSUIPC doesn't install correctly
Pete Dowson replied to jakoby84's topic in FSUIPC Support Pete Dowson Modules
You don't need to purchase FSUIPC4 to use FSCommander -- FSCommander is a licensed FSUIPC client program. So, either FSUIPC4 is not being loaded by SimConnect, in which case it is a faulty DLL.XML file -- possibly corrupted by something else you've previously installed, OR you have a broken SimConnect installation. The quick way to determine which is the case is to look in the FSX Modules folder and see if there's an FSUIPC4.LOG file, and an FSUIPC4.INI file present. If so, then FSUIPC4 has been loaded and there's some sort of SimConnect installation problem. In this case please paste the Log file into a message here. If that's all, if there's no FSUIPC4.log and no FSUIPC4.ini file, then it is your DLL.XML file which is corrupted. Please go to this folder C:\Users\admin\AppData\Roaming\Microsoft\FSX and get the DLL.XML file, then paste it into a message here. Please be sure to use the CODE button (the one looking like <>) with the XML text selected so that it's format is preserved. It did find FSX.CFG, as it says: Maybe you installed FSUIPC when logged in as "Admin", but you are now trying to run FSX as User "jakob"? You have evidently installed FSX under "Admin" in any case, as else there'd be no FSX.CFG there. Try running FSX as the same user you install things for, or else install again for the correct user. [LATER] This problem got me thinking. As you will see from the Install log, the installer examines, uselessly, all of the other current User folders as well as "AppData". Looking at my code I think I intended it to, instead, look in all of the AppData folders for all users. In fact one of the lines in the Log does imply that. So, I am changing the installer now, ready for the next main update, so that it does just that -- install for all users which have an FSX.CFG file, not only the current user. Meanwhile, you can log in to the user which will be flying FSX and rerun the installer. That's the work-around. Regards Pete -
Oddities from my TQ
Pete Dowson replied to richard hutchinson's topic in FSUIPC Support Pete Dowson Modules
That is VERY much out of date and unsupportable. Before we continue please update to a supported version -- 4.60 or later! I am talking about disabling the controller in FSX! That's a darn sight easier than deleting all the assignments, and prevents FSX automatically re-assigning things, as it will do if it thinks it's a new attachment at any time. Regards Pete