Pete Dowson

1. Why are you looking in the Log in the first place? What is prompting you to do so? What is not working? 2. It actually states very clearly that is DOES find the CFG file, here: Looking in "C:\Users\James\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\James\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG" So, I repeat, WHAT is the problem? Why aren't you going flying instead? Pete

Sorry, but you misunderstand completely! First off the range of a signed short integer (16 bit) is -32768 to +32767. The range of a normal 32-bit integer is -2147483648 to +2147483647. The problem is that you are writing 4 bytes (=32 bits) to a value which is only 2 bytes (16-bits) long. Therefore you are writing the upper 16-bits of your value to the address of the Prop Pitch value! It wouldn't matter what number you wrote to the throttle, you are also writing to the prop pitch!!! You need to understand data types and their lengths! I don't know the programming language you are using but I think you should refer to is documentation or manual and learn a bit more about data types. Regards Pete

Those offsets are 16-bit (short) signed integers, not 32-bit "int"s! You are writing 32 bits, so overwriting 088C to 088F, which obviously includes 088E-F, the prop. ALWAYS take note of the sizes and types of the data. Pete

Hmm. I think that, unless I can reproduce the problem here, I'll have to give up. If anyone has a sure-fire way of making this happen within a reasonable time (I'm not willing to fly it for hours, it needs to happen quickly, like 30 mins or less, please, because I'll need to do it several times and I do have other things to do) then perhaps they'd describe it. I'd need their main FSX or FSX-SE CFG file because I'm pretty sure it's going to also depend on settings. And hopefully it will not involve any payware add-on I'm unlikely to have -- like PMDG, iFly etc etc. Pete

Well it certainly sounds like you did all the right things! It's because the FSX-SE installer obviously thought you still had FSX installed. Why, I've no idea. Sorry. I certainly think you should report it on the FSX-SE forum on Steam though. Pete

I've made some small changes, and, though I don't think they'll really help, it's worth replacing your FSUIPC 4.938g with this one: FSUIPC4938hTEST.zip Pete

What error do you think you are getting? The log shows it all went perfectly! Pete

This one is a real puzzler! This logged line: 328 TERRAIN.DLL fix attempt installed ok means the patch location has been verified, and patched. Yet this: Fault Module Name: terrain.dll Fault Module Version: 10.0.62608.0 Fault Module Timestamp: 54abe5e1 Exception Code: c0000005 Exception Offset: 00059be8 is a crash in exactly the place being protected. I can understand it maybe moving on, but this is odd. I'll have to think about this one. Pete

Yes, it confirms 100% that the FSX-SE you have installed is installed in exactly the same way as if you also had FSX still installed. Here's the evidence: The pointer to FSX-SE is found in a Registry Key specifially for Steam Edition. When FSX-SE is installed on its own, this doesn't happen. it looks exactly like FSX. Installers unaware of FSX-SE will not find your installation. Further, you have separate FSX-SE folders in your AppData and ProgramData folders. In a proper FSX-SE sole install you'd only get the normal FSX folders: I think that if you want to fix this you would have to uninstall FSX-SE, delete the FSX and FSX-SE folders in ProgramData and AppData (both in Roaming and in Local) and then try installing again. I might have forgotten something you should also delete, but if so, sorry, it's gone. Pete

Rather than takes pictures and place them in your messages it would be far better just to open the relevant files in an editor, like Notepad, then cut and paste the text into your message. In particular, I would like to see the complete FSUIPC4 Install log rather than the partial picture you've shown. From the little I can see, and the error in the previous message, I think you have a bit of a mess there, with the FSX-SE installation in the state it would be in if FSX was still also installed. This will not make it easy to install other add-ons UNTIL they've had their installers updated to deal with the different folders used by FSX-SE compared to FSX, so you'd be losing the main advantage of having FSX-SE installed without FSX. I can check this and tell you for sure if you will show me the Install log file. Pete

No, I've got 8 PCs on a hub, no router necessary. A router's only needed for Internet access and there's no internet stuff built into Wideclient or FSUIPC. None at all. Sorry, I really don't know why using the correct IP address doesn't work. You say that even if you specify the correct address it is trying to use the other. How are you checking this? Are you sure it isn't just a firewall problem? Pete

Well, sorry, but evidently CCleaner left something behind which messed up the FSX-SE installation. Maybe it doesn't delete the ProgramData, and AppData FS folders which FSX and FSX-SE both create, side-by-side -- there's three of them and they contain changing data like settings and scenery indices, so unlikely to be removed by CCleaner. I think you might want to check some other things too -- like whether there's just an FSX folder in your C:\ProgramData\Microsoft folder (as there should be), or an FSX-SE folder instead or as well, which would be wrong with a sole-install of FSX-SE. Yes, and didn't you bother to read what the Explorer-style window say in its title? "FSX or ESP not found! Please locate and 'Open' FSX.EXE or ESP.EXE"? (I must remember to update that to refer to P3D instead of ESP!) If you know how to open files in Explorer then you should know what to do with such a request. If you don't know how to find and click on files, I can only ask you to refer to Windows help. [LATER] Ouch! I only just noticed this: Installer for FSUIPC4.DLL version 4.853 4.853 is VERY VERY old and doesn't support even P3D let alone FSX-SE!!!! (That's why it referred to FSX and ESP!). ALWAYS check for updates. The current version is 4.938f. You even posted your message in a thread which has a title telling you that you need 4.938 for FSX-SE!!!! :-( Pete

FSX-SE installed without a prior installation of FSX looks EXACTLY like FSX to any installer. The registry entries pointing to the install path are the same. That is all the FSUIPC4 installer needs! On one of my PCs I have only FSX-SE installed, and this is what the Installer finds: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=E:\Steam\steamapps\common\FSX If your FSX-SE was installed correctly, it would do the same! Somehow your registry is wrong. Have you used a windows restore point and gone back to a point before you installed FSX-SE? You shouldn't do that unless you are uninstalling it. If you haven't, then something went wrong during the install and you should report this to DTG on their Steam forum. Meanwhile, when the FSUIPC4 installer asked you to find the FSX.EXE, why didn't you? If you do this, then the Installer will actually offer to fix that registry entry for you! Pete

Where on Earth are you looking? In the Lua library reference document each of those functions is described separately, and each one tells you what the data type is, clearly, in the first sentence describing the function in the right-hand column!! Pete

No, WideFS is extra. And the purchase is not version specific. You pay for FSUIPC4. You use the latest published version. If you want support you keep it updated. No. I don't know why it should be any different from what FSX is doing. Some folks report better results with FSUIPC, but I've no idea why. No idea, sorry. I don't sell FSUIPC, SimMarket does. I just do support and development. I thought bundles for FSUIPC usually refer to FSUIPC + WideFS, but I don't know what the "2" is in your "2 for 1€" Pete

The SDK contains the details of the offsets and values to be used for the New Weather Interface. If you don't want to deal with binary data you can use SimConnect style METAR strings. You can of course use SimConnect directly. That's all FSUIPC is doing. Any weather control program for FSX is going to be quite a big job. It isn't something to do lightly. There are commercial programs doing it very well, of course. I use ASN. There is a free weather read/write program provided in the SDK -- WeatherSet2. That uses the New Weather Interface. Pete Pete

Sorry, I've no idea how to force a program to use a different routing -- it uses the IP address supplied by Windows if you give it the computer name, or the one you give it directly by parameter. If neither of those methods work then there's something weird going on. WideClient can do no more that request the specific port on the specific IP address. Pete

Sorry, that sort of direct control doesn't work with FSX. It was only experimental in FS9. You'd need to use the New Weather Interface to set weather stations, or global weather, and this entails setting all of the weather, not just the rain. Pete

Do you not see the lines (I've emboldened them) clearly marked "Start .."? In this example, at least, the headings for the starts seem to be the same as the runway headings. If you cannot find one where they are different then it might not be possible for me to add it, at least not without a lot of investigation (ie BGL hacking) which I'm really not wanting to undertake. If I have the correct data already it should be easy. Pete

Ah, thanks for pointing this old statement out. I've changed it now. It was covered in the WideFS Technical guide not long after. However, your IP address doesn't look like an Internet address either. 192.168.xxx.xxx are reserved for local networks I think. It's evidently the address provided to WideFS by Windows in response to querying it about the PC called "RABBIT". Maybe thereare two LAN connections enabled on it? Have you tried setting the correct IP address explicitly, instead of using the PC name "RABBIT"? Pete

Er, if you had success without FSUIPC's patch, the patch isn't likely to do anything? Surely you need to fly flights you've not had success with, ones you previous experienced TERRAIN crashes at the most commonly reported offset, the one FSUIPC patches? Really I don't think you should worry about flying specific flights. Just do what flights you want to do, that you'd normally do. Just please check the log afterwards. Once even just one person reports that FSUIPC says it caught one, I'll know it's a success. Unfortunately I'll never be able to prove it isn't. Pete

Really? What does the Start entry for that runway show then? All the Start data appears to be listed here for all runways. If it doesn't appear at all in Runways.txt then MakeRunways cannot even provide the Start Lat/Lon information. Pete

Well, you might as well keep that existing option enabled. After any good (crashless) flight, just look at the FSUIPC4.LOG file and see if it logged any TERRAIN.DLL crashes trapped. I'm still 50:50 whether your latest one was the same one moved on or a different one. Pete

What have you actually done in FSUIPC? Why do you think FSUIPC is anything to do with this? Engaging the A/P is just one assigned control, whether in FS or in FSUIPC. Are you sure this add-on aircraft even uses the FS A/P? Best test assignments etc using a default aircraft first. Only once you have everything sorted start testing on an add-on aircraft. If you are assigning axes and buttons in FSUIPC then you should really disable controllers altogether in FS. There's an option to do this it its settings. Pete

FSUIPC4 works with FSX, FSX-SE, P3Dv1 and P3Dv2. The current version is 4.938f. FSUIPC3 works with FS9 and before, but support is limited to its use with FS9. Pete