Pete Dowson

Following on from my last reply, I see that HiFi Simulations says that the BETA release of ASN for P3D 2.5 should work fine with the "hotfixes" (it doesn't number them). See this thread: http://www.hifitechi...22370#post22370 If you are, indeed, using that Beta, then something else is odd. Please check that the version numbers of the three DLLs I mentioned are, indeed, 12944. (Right-click on the DLL and select Properties). Pete

Please do NOT post temporary support requests to the FAQ subforum! That's a forum for permanent helpful ANSWERS to Frequently Asked Questions. If you want to talk to me privately I need a reason first, please. Pete

These two errors: 1919 Hook Error: can't find .42 in SIM1.dll 1919 Hook Error: can't find .42 in VISUALFX.dll indicate an error trying to install the FSUIPC4 wind smoothing facility. This either means your WEATHER, SIM1 and/or VISUALFX.DLL are not correct, i.e. not the version 12944 builds I have here, OR possibly attempting to use ASN (which uses the same hooking methods) before ASN has been updated for 12944 is causing the conflict. doesn't ASN report an error? I does for others with 12944. They only recently updated for the original 2.5 release. Additionally, this line 1919 ASN active function link set is odd. That shouldn't occur if ASN is working correctly. I think it is something fixed by ASN automatically when you first load it -- it then says you need to close P3D/FSX and restart it. As you say, it'll probably do no harm. It's just that neither FSUIPC's wind smoothing, nor ASN's smoothing or direct cloud control, will work. In fact I'm surprised ASN carries on regardless -- did you ignore the error message box it produced? If you OK it ASN will terminate. Pete

Okay. I found the problem in any case. Please try the installer for FSUIPC 4.938e, use this link: Install_FSUIPC4939e.zip Pete

Okay. I found the problem. Please try the installer for FSUIPC 4.938e, use this link: Install_FSUIPC4939e.zip Pete

What radar in what aircraft in FSX itself? If you mean FSInn's injected traffic being seen outside, that's all to do with FSInn. This is really nothing to do with FSUIPC, so I'm not sure why you are posting here. Maybe you are talking about an add-on aircraft which isn't compatible? Or maybe FSInn isn't compatible? Pete

Can you tell me exactly what happened on screen? The Install log is incomplete, as if the install was aborted. Wasn't there a message box appearing to tell you it was installed okay? What did you then do? FSX-SE installed with no prior FSX looks exactly like FSX -- that's intentional by DoveTail, so that installers like this will think it is FSX. But in the FSUIPC installer there's no way out at the end without going through the Registration screen UNLESS something odd happened. I need to know what that something is, please. Exactly what did you see and do? Did the installer crash? Are there any errors for it in the Windows error log (enter Event Viewer is the Start-Run box)? Pete

I have seen recently folks use a utility to specifically assign joysticks to numerical IDs in the REgistry. Look at this thread: http://forum.simflig...ids#entry476819 Pete

If you want to test the Beta of their next version, to make sure they've fixed this, send me an email and I'll give you the details. Apparently I'm allowed to do this, but only for specific purposes like this. petedowson@btconnect.com Pete

Shame. You could have retrieved the details from your SimMarket account. Well, some folks say this, but I really don't understand why it should make any difference, as FSUIPC uses similar methods, via DirectInput, as FSX and P3D. In theory they should both get the same results. Sorry, I don't know what TARGET software is. FSUIPC doesn't know or care about what sort of device it is, as long as it looks like a joystick with buttons and/or axes to Windows and therefore DirectInput. I don't know Thrustmaster MFDs. Pete

Hmm. it is as I feared. I'm tackling the symptom, not the cause.. All I've succeeded in doing is moving the site of the crash. Without being able to reproduce it here, I've really got no way of tracking the bad pointer back up the chain to tackle the source. I definitely think these crashes (G3D and Terrain ones) are down to sceneries or aircraft graphics which are slightly bending the rules, taking advantage of things not documented for normal FS use. I have lots of add-on sceneries (but Europe only, I don't fly long distance), and no aircraft panels, and have never had either G3D or Terrain crashes in either FSX-MS or FSX-SE. Your crash at 5hours 32mins must be really the same one as this: 20605689 *** TERRAIN bad pointer trapped and crash prevented *** That time on the left is 5hours 43mins from FSUIPC starting up. DoveTail are definitely working on all this. I will be leaving out both G3D and Terrain fixes in the FSUIPC4 version aimed at the next FSX-SE update, as they should have "fixed" both. We'll see. Won't be long now. Pete

No, that's the run-time log from FSUIPC version 4.939d, the same one you posted before, and proving it installed fine. The install log actually has install in the name. Pete

No, don't do it manually. They are generated automatically when they are detected. If they disappear it is because they are either no longer connected or because something has gone wrong and they are not being detected. They are needed if FSUIPC is used to assign buttons and axes on them, but they are genertated by reference to the Registry entries for them which say they are there. I have seen recently folks use a utility to specifically assign joysticks to numerical IDs in the REgistry. Look at this thread: http://forum.simflight.com/topic/78693-fsuipc-fails-to-recognise-buttons-pushed-on-my-saitek-throttle-but-does-recognise-my-stick/?hl=joyids#entry476819 Pete Pete

You should consider updating to 4.939d in any case. If you have any further support needs I would ask you to make sure you are using the most recent release. Version 4.929e will be released soon, too, which will work correctly with the next FSX-SE update. Pete

You must have aborted it before it finished then and it cannot finish normally without asking this. Were there any messages? . Where is the Install log, please? Paste it here. I cannot help without any information. Pete

I've worked on this a bit more and have come up with a different work-around for that one specific Terrain.dll crash. The problem is I don't know whether it'll fix it or just move the error elsewhere. Perhaps you could test it please? Download FSUIPC4939e_test.zip and just copy the FSUIPC4.DLL into your FSX Modules folder. It doesn't need any parameters, it is just automatically applied, like the G3D fix is. If you don't get the crash, please let me see the log after you've closed FS with a successful session. If it does crash, let me see the crash details, please. I know that DoveTail are working on fixes for these crashes, so my interventions may not be needed for these much longer. We'll see ... ;-) Pete

No. Sounds like a facility on the GPS because it only has one radio changing knob? Is this an add-on GPS or a standard FS one? There are some GPS controls supported by FS, they are all in the list starting with "Gps ", but I don't see one specifically for hat function. Pete

COM/NAV toggle? Do you mean use/standby swap? There's a separate one for each radio. FS doesn't provide a toggle to swap radios completely. Pete

Never mind. I simulated your Registry mixup here, my messing mine up, and worked out what to do about it in the Installer. Download the revised FSUIPC4 installer from the Download Links subforum ("Updated Modules") and try that. It won't fix your registry (so other installers may also get confused), but at least it now doesn't stop FSUIPC4's installer working. Pete

The installer detects FSX-SE bcause your registry says it is installed, though it points to the same folder as FSX. See here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=C:\Program Files (x86)\Microsoft Games\Flight Simulator X\ This cannot get into your registry without something putting it there, so evidently someone's been at your PC without you knowing? The registry is exactly as it would be without FSX but with FSX-SE only. For the next version of the FSUIPC4 Installer I will try to deal also with this crazy case. There seems to be many ways in which folks can get their Registry in a mess! :sad: If you cannot wait for a revised installer, the only solution for you with the current installer is to use Regedit to delete the complete key (and subkeys) at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition As far as I am aware that cannot be created by anything other than using the Steam FSX-SE installer. Either way, so I can make the right changes, can please you tell me exactly what the FSUIPC Installer does -- the text file ends abruptly! There would have been a message or something, and maybe an option to do something, but the text file is still incomplete. I need to know why. What you saw, and what you did! PLEASE! Pete

Please write to me by email explaining your product and its use of FSUIPC. petedowson@btconnect.com Pete

Please do NOT post pictures of text files, but paste the entire text file instead. I need to see the entire file -- the part you captured is incomplete and shows no failure at all. Why do you think it fails? And please also explain the history which led to there being two pointers to FS, one for FSX and one for FSX-SE -- that's not possible if you never had FSX-SE at all. You can save the file using "Save" in the File menu, assuming you cannot find the FSX Modules folder where it will have been installed. Pete

You only had to search the offset listing installed in your FSUIPC Documents folder for "altimeter", to find offset 3324. This is not true altitude, but the reading on the instrument. It might be feet or metres depending on the user setting. It's a 32-bit integer. Pete

Hmm. Not sure what Linda is doing to cause a crash. I assume there's a support forum for Linda? Pete

I can only suggest you try it. The way FSUIPC applies these things tends to work with the original reasons for sudden extreme wind shifts -- errors in the interpolation between the three WX stations involved in the current triangular area, but that was with FS9. With FSX and the advent of direct and global weather control most weather programs seemed to be able to operate smoothing more subtly, within their own settings. I have not heard of any real problems with FSX winds for a long time. I have REX for cloud and wave textures,, OpusFSX for cameras, but ASN for weather and real and accurate weather radar. I pick the best bits from each program! ;-) Pete