Jump to content
The simFlight Network Forums


  • Posts

  • Joined

  • Last visited

About Noel

  • Birthday 01/01/1970

Contact Methods

  • Website URL

Noel's Achievements


Newbie (1/14)



  1. OK thanks, was guessing maybe this was figured out since the post was back in Oct but apparently not. I assume it's just a case of executing the .msi? Then do I reinstall FSUIPC4 again? Maybe just try re-loading P3D... Thanks as you would know--all's well ;o)
  2. Hi Pete, I installed and registered FSUIPC and it created the Modules folder and I think is everything that is supposed to be in it including SimConnectP3D2.dll which the log file says it can't find. So far P3D 3.1 has been a royal PITA so may get my money back and continue w/ 2.3 which was flawless and I adjusted fine to its VAS limits for 2.7y. The Saitek Cessna Trim wheel conflicts w/ 3.1 and never did w/ 2.3. FWIW and maybe this is material when I wiped my drive and started w/ a fresh Win 7 SP1 install I decided not to install any Windows Updates whatsoever as this is how I had 2.3 installed for 2.7y. This drive is isolated from web surfing or other use beyond P3D so didn't find a need for A/V software or other. Anyway, what next please and thanks in advance. ********* FSUIPC4, Version 4.949f by Pete Dowson ********* Prepar3D.exe version = Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 7 Module base=60F70000 User Name="Noel Phares" User Addr="ncp10@pacbell.net" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 04/03/2016 07:33:53 0 FLT path = "C:\Users\NoelPhares\Documents\Prepar3D v3 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 0 api.dll: 0 controls.dll: 0 fs-traffic.dll: 0 G3D.dll: 0 language.dll: 0 sim1.dll: 0 visualfx.dll: 0 weather.dll: 0 window.dll: 0 ---------------------------------- 0 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 16 !!! Error 126: The specified module could not be found. 328 NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed. 359 NOTE: SimConnect SP1 May07 is supported, but it isn't installed. 374 NOTE: SimConnect Original is supported, but it isn't installed. 374 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect! 390 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\" 686 ---------------------- Joystick Device Scan ----------------------- 686 Product= Pro Flight Cessna Yoke 686 Manufacturer= Saitek 686 Vendor=06A3, Product=0BD3 (Version 1.22) 686 Serial Number= RD002340 686 ------------------------------------------------------------------- 702 LogOptions=00000000 00000001 702 ------------------------------------------------------------------- 702 ------ Setting the hooks and direct calls into the simulator ------ 702 --- CONTROLS timer memory location obtained ok 702 --- SIM1 Frictions access gained 702 --- FS Controls Table located ok 702 --- Installed Mouse Macro hooks ok. 702 --- Wind smoothing fix is installed 702 --- All links okay (except older global weather setting method) 702 ------------------------------------------------------------------- 702 Could not link to all needed SimConnect facilities 702 Trying to use SimConnect Original 15740 ... Now trying to connect to another version of SimConnect ... 15740 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 15740 !!! Error 126: The specified module could not be found. 30779 ... Now trying to connect to another version of SimConnect ... 30779 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll 30779 !!! Error 126: The specified module could not be found. 50669 System time = 04/03/2016 07:34:44 50669 *** FSUIPC log file being closedMinimum frame rate was 32768.0 fps, Maximum was 0.0 fpsMinimum available memory recorded was 32768MbMemory managed: 4 Allocs, 4 Freed********* FSUIPC Log file closed *********** <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon></SimBase.Document>
  3. That's funny Pete. No, the idea is not to make it more complicated, it would be well, you know. Thanks, I found a more elegant solution in the built in calibration routine. Cheers
  4. Yes, maybe directly editing will be the path, as I don't see anything in the interface to do it. Here it is in the adv user guide: Additional parameters to scale input axis values Axis values assigned in FSUIPC4 can be arithmetically adjusted before being passed onto FSUIPC4 calibration (or to FS via FS controls). To do this you assign the axis as normal, then edit the FSUIPC4.INI file. Find the axis assignment there, in the relevant [Axes] section, and add one or both of these parameters to the end: ,*<number> to multiply the axis value by <number>. This can be a fraction, such as 0.5 (to divide by 2), and it can be negative, to reverse the axis direction. ,+<number> or -<number> to add or subtract a number (an integer, no fractions) to or from the value. If both parameters are given, the multiplication must come first, and is performed first. The resulting value is constrained to be in the range -16384 to +16383. As an example, if the normal input range of an axis is -16384 to + 16383 and you only want the positive half, but need to still use the whole of the lever movement: ,*0.5,+8192 would be added to the assignment. The *0.5 changes the range to -8192 to +8191, and then adding 8192 gives 0 to +16383. After editing, just tell FSUIPC to reload the axis assignments (a button on the Axes page). You won't see the results there, but you will in the calibrations. A bit of a puzzle why this wasn't added to the user interface as to me it does seem like it might be quite useful, but a least it's possible to do. BTW, it looks like one get get their PhD in FSUIPC digesting the Adv User Guide--lots of technical detail there! Thanks, Noel
  5. I've assigned one of the Saitek throttle quad levers to a mixture axis control. I'm trying to figure out how to configure it in AXIS ASSIGNMENTS if when the lever is physically in the lowest position it will not activate a cutoff to kill the engines but I can't seem to figure out how if that's possible. I have looked at the FSUIPC owner .pdf and couldn't see instruction on how to do that or even if it's possible. Thanks in advance, Noel
  6. Thanks guys I had actually done this, copy/pasted from my key, and kept getting the Sorry message. However, when I rebooted and opened up a new flight in P3D V2 FSUIPC now say's I'm registered! Anyway, thanks a lot I think we're good now. Cheers, Noel
  7. My current one isn't activating the new version compatible w/ P3DV2. The executable installs fine but the registration dialogue says Sorry this key is not valid. I used this very key a few weeks ago and it worked fine, but needed to reinstall P3DV2 so had to reinstalled FSUIPC. When the check current registration option failed I selected 'delete current registration', then tried to use the new registration but this failed. Help please! My name is Noel Phares, and I had a valid key after purchasing the full version some years ago. Thank you!
  8. Geez! I posed the same question on the Avsim forum and YOU asked me to install the latest version then send you the log file when it crashed. Why there? Because all crashes cite FSUIPC.dll. I didn't understand its role in the game, Pete, which is why I asked. Why did I purchase it? Because I thought it's user controlled features might be of value. And having experimented w/ some in particular the wind smoothing effects, found them not to be useful, that's all! So what you are saying is that a corrupted scenery or object file triggered the crash, and FSUIPC.dll contains a feature which can report on the error. Fine, thanks for the explanation--I has assumed the error WAS IN FSUIPC.dll, since it references this w/ each crash.
  9. As requested, here is the .log file that may help determine what is happening. Since I don't use many of the user customizable features in FSUIPC, what would happen if I just removed it? I asked this in the MS FSX Forum on Avsim. Thanks in advance, Noel ********* FSUIPC4, Version 4.86 by Pete Dowson ********* Running inside FSX on Windows Vista Module base=69FC0000 User Name="Noel P" User Addr="ncp10@pacbell.net" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 26/02/2013 19:18:59 0 FLT path = "C:\Users\Noel\Documents\Flight Simulator X Files\" 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 47 FS path = "F:\Microsoft Flight Simulator X\" 546 LogOptions=00000000 00000001 546 SIM1 Frictions access gained 546 Wind smoothing fix is fully installed 546 G3D.DLL fix attempt installed ok 546 SimConnect_Open succeeded: waiting to check version okay 546 Trying to use SimConnect Acc/SP2 Oct07 4977 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 4977 Initialising SimConnect data requests now 4977 FSUIPC Menu entry added 5024 C:\Users\Noel\Documents\Flight Simulator X Files\1.FLT 5024 F:\Microsoft Flight Simulator X\SimObjects\Airplanes\F1_Cessna_441\F1_C441.AIR 83945 F:\Microsoft Flight Simulator X\SimObjects\Airplanes\QualityWings 752 Passenger\QWSim Boeing 757-200WL Pratt & Whitney PW2043.AIR 123366 C:\Users\Noel\Documents\Flight Simulator X Files\KPHX-KSAN FL400.266M 211741 Weather Mode now = Theme 211741 Weather Mode now = Custom 216733 System time = 26/02/2013 19:22:36, Simulator time = 19:19:05 (02:19Z) 216748 Aircraft="QWSim Boeing 757-200 United NC WV" 218183 Starting everything now ... 219275 Advanced Weather Interface Enabled 601540 Sim stopped: average frame rate for last 384 secs = 21.8 fps 2459294 *** G3D bad pointer trapped and crash prevented ***
  10. Hello, I find myself occasionally needing to stop the flight in dense areas when I have BLOOM on. I really like the BLOOM feature, so I"m willing to use it where I can, and disable it when scenery and conditions get very strong. I am able to retain smooth landings in dense terminals with Bloom on about 70% of the time, but occasionally it's nice to pick up that huge perf increase by disabling Bloom. Having to stop the flight as it is now kind of hampers the experience. So, since switching between Bloom on or off DOES NOT result in a scenery refresh, it seems possible one could turn it off in real time, with a brief hiccough or so, with perhaps a programmed keypress. What do you know Peter? It could be a REALLY useful feature to allow bloom to be used more often so long as it can be toggled on and off ease with this type of feature. Thanks for your time, Noel
  11. to the top of the visibility layer, such that you no longer get that "sharp edge" where the top of the vis layer intersects with terrain elevations (eg, in moutainous areas)? It would seem to me all visibility layers have a top, so couldnt you program FSUIPC to tell FS9 to change the value of the top 50 pixels to go from 100% to 0%, versus have whatever visibility density is at the top of any layer go from 100% (of the existing density) to 0% from one pixel to the next one up? Or something like that?! Noel
  12. Pete, now that is not true. I have tried them. But my goal was to get rid of the ice rink effect, which as you explained, is not going away anytime soon. You should take note Pete that others find some of the visibility elements to be not good in FS9, though you continue to speak highly of FS9''s visibility implementation. Anyway, it sounds like you already tried to do what I asked, so thanks for trying . . . Noel
  13. Somewhere in FS9, code tells the sim to open the ATC window in the same position each time. Seems like you might be able to find it and tell it to look at the last position it was in, and use that position next time, no? I'm not a programmer like you are. See what you can do. If it's too much time for too little benefit, I will just keep doing it every time up. Again, FSUIPC doesn't seem to offer too much for me this time out. In FS2002 I used the visibility smoothing etc and really liked it. It really don't help the situation in FS9. Often the default handling of visibility is better than what FSUIPC can do. So again, the $20 really didn't get me anything personally. It doesn't hurt to ask for something of practical value for me personally, eh? I know you're doing the best you can with FSUIPC, so I ask this as a favor. I'm sure there are others who do not like the default positioning of the ATC window so it may appeal to others as well. Didn't know about the show windows while dragging issue. Thanks. Noel
  14. Unfortunately, for those of us who do not like to call up saved flights, the problem of the ATC window showing up in its default mid screen position with all new flight plans remains. I don't like to load memory up with a saved flight anyway, since I almost always fly new ones with new real weather. So there is no fix if you like to start FS9, then create or load a flight plan, then take off. In this situtation you have to resize/reposition the ATC window as I had mentioned before. Please do consider, if possible, adding a "Fix ATC window size and position" in the Technical tab of FSUIPC. I don't know how many others like to move the ATC window off to an upper side corner, but I do on every single flight. I would very much appreciate this facility. Also, I have the checkbox activated that is supposed to fix cockpit window positions and size, etc. Didn't this imply one could not resize/repos the windows without unchecking this box, or no? I thought the purpose of it was to prevent inadvertent resizing (i do this by accident sometimes when I'm resizing and reposition the semitransparent ATC window hint hint . . .) Noel
  15. I am an amateur VBA programmer and I have a definite feel for the idea of spending hours with little to show for it (except of course what you have ruled out . . .). Well, I hope you can somehow figure out how to have less of a delineation--a "softer" edge if you will. If that were the case I'd be very grateful, as this, and sometimes when the bottoms of clouds contact the tops of mountains there is, again, to distinct a line. I think its a case of the cloud just being to uniformly low in density, so the sharp edge of the mountain bleeds through to much. It needs to be such that you really never see that completely sharp line. I think in the real world clouds scatter the light too much, and perhaps darken light reflected off mountains behind such that you just don't have the hard edge. Looks fake is the issue. BTW, sometimes the blurring looks very good . . . Good luck! Noel
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.