peterhayes
-
Posts
898 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by peterhayes
-
-
John
If you are using FSUIPC4 with FSX you should not need the SST software for something like the Baron.
You have checked your senitivities and null zone in FSX (Sensitivity full right/null zone full left)
Regards
PeterH
-
Hi John
It should be in the Program Folder (maybe x86) - I haven't installed it for years so my memory is hazy. But there should be a shortcut to it (probably on the start menu too) and it only affects FSX if you initiated it to do so. You could use Belarc adviser to see what software is installed and it would show up there. If you have win XP 7/vista it will be listed in the "all programs" button. You would remember if you installed it because you have to assign axes and buttons before you can use it.
I would say that you do NOT have the SST software installed.
Regards
PeterH
-
John
Saitek have 2 pieces of software: 1) Drivers (see Ian P's reply above) [in Win 7 I have found these to be unnecessary]
2) SST programming software - when I wrote the appendix I found thet there seemed to be issues if used with FSX and FSUIPC4 and as the latter is excellent at assigning and calibrating axes etc, I uninstalled the SST programming software.
I didn't notice any issues with the drivers. However the SST P S is now a later version so things may have changed.
Regards
PeterH
-
Yes, they are assigned as Mixture 1 and Mixture 2.
I 'appear' to have them calibrated correctly, by which I mean that within the calibration window each lever when moved shows full movement from +16320 to -16320 (plus/minus). I then click on the <Set> button for each position - Max- Min - just as I do for the throttle and prop control levers. I have the <No Reverse> selection ticked.
John
John
Are you assigning in FSX or FSUIPC4? Just make sure in either case that the axes are not assigned (duplicate) in both FSX and FSUIPC4 and if you are running the SST software (not drivers) that can interact with FSX/FSUIPC4 wrt to duplicate assignments. In fact, always check for duplicate axes as FSX can be sneaky and assign axes in any of your controllers including the mouse.
PeterH
-
Park
That's excellent news - I had assumed when you moved to a 64-bit OS you would have applied that uiauto. . . .dll, which if you don't install it FSX usually reports the reason for a crash being that dll and gives a locale id.
I'm glad you got it solved! :grin:
PeterH
-
Hi Park
This is all that I can think of:
I sympathise with this issue.
I guess that you have checked all of your hardware - memory ie physical RAM, mobo, HDDs etc.
It does look like a memory leak BUT if the system does NOT crash only FSX then it points to an OOM (VAS)error within FSX.
Can you run eventvwr.msc (Windows+R) key and find the point that FSX crashes to see if there is an event id?
Does the crash produce any error message? eg the process or a locale ID?
In Win 7 via the control panel there is a little know feature called "ACTION Centre" are there any error messages in that? Just open control panel and in the search window type in Action Centre. (or Center) Best straight after the FSX crash.
Have you tried a clean fsx.cfg without any tweaks and tried flights only using the default planes. Then introduce one plane at at a time to see what may be the cause.
After that you may need to research Performance Monitor "PERFMON" as that has the capability of detecting vitual address leaks and in some case faults with physical RAM. In Perfmon you also get the reliability monitor (see http://www.sevenforums.com/tutorials/2270-reliabilty-monitor.html) and that can be useful in diagnosing faults since the day that you installed Windows.
If this fails it may mean that you some faulty hardware but that's unlikely unless it is intermittent as it would usually crash the whole system.
Regards
PeterH
-
Akila
Not sure what you mean here: "very good info , however this is not the case here.
I have 64Bit OS with 6GB of RAM and I had the same issue, it is how windows7 dll is called out"
The OP has a 32-bit OS see above (32 w7) and uiautomationcore.dll will not help with a 32-bit OS OOM (random shut downs)issue. Can you expand on why my information was NOT relevant to a 32-bit OS? :lol:
Thanks
PeterH
-
Park86
The OOM issue is probably due to your 32-bit OS and it could be made worse with your new GTX560 card which has 1GB of VRAM. On a 32-bit OS FSX has a "shared" virtual address space (VAS) with the OS taking up to 2GB and the VRAM taking up 512 or 1024MB dependant on the size onboard. You can get more of the Virtual address space for FSX (SP2/Accel/Gold not SP1) by using the Userva=2560 (+/-128 blocks) switch using bcedit in Win 7.
IMHO You would be much better switching to a 64-bit OS where FSX gets the whole 4GB VAS to itself (less about 256Mb for the VRAM). You can still see OOMs with a 64-bit OS but they are much less likely (usually due to complex poorly scripted 3rd party addon software) than using a 32-bit system. One simmer described the difference between the two, saying a 32-bit OS is like a garden hose and a 64-bit OS is like a Fire Fighting Hose. :lol:
BTW this has NOTHING to do with Physical RAM. :-P
Regards
PeterH
-
1
-
-
MM
Thanks again very useful link.
pH
-
MM
Tried that and it works! Thanks!
It would be nice to be able to start bat files as well as exe files within Xtreme FSX because when you've got ASE and REX and a few others it starts to get a little complicated.
Peter
-
Hi
I use FPS Limiter to control Frame rate fluctuations (FPS unilimited is set in FSX) so 2 questions:
1) Do I still need to use FPS Limiter if I am using Xtreme FSX?
2) If yes how do I start a "BAT" (FPS_Limiter.bat starts FSX) file within Xtreme FSX? as only provisions for starting "EXE" files are given in the addon sec
tion.
Thanks
PeterH
-
Pete
Thanks for taking the time to reply.
Regards
PeterH
-
Hi Pete
Hope you are well - just a question:
Just a thought on the updating of your various modules. You, quite rightly, extol us to use the latest versions of your software but the actual process of seeing if there is an update can be quite confusing.
On the modules sub-forums tab: the "Download links" shows a date of 17 January 2011 for FSUIP client dll for .NET.
Click on download links and under 'Updated Modules' the date is 25 January 2011for FSUIPC 4.657 and 3.989 w . . . , but on the 'Last Post Info' the date is Oct 19 2010. Is there any easy way to flag on the modules sub-forum download links a date that is for the latest of any download?
With regard to the 'Updated Modules' tab could this be changed to 'Updated FSUIPC/4, Wide Client, PFC /FSX Modules'?
Just a thought these changes might make it easier to update the module at the correct time.
I fully understand if this is quite difficult to achieve under the new system. :???:
Regards
PeterH
-
Malleman
What HDD are you using and how is FSX installed - in its own directory or on a separate HDD.
Have you used disk cleanup in Accessories and then defragged the disk (if a conventional HDD)
I have an i7 860 and rarely see any stutters so its either hardware, cpu ram gpu HDD or a setting.
Is the gpu seated correctly with the correct power supply?
Is the RAM in 2 x 4GB or 4 x 2GB and if the former in the correct slots and seated well?
That's all I can think of! :wink:
(if you don't get a message about refreshing scenery or textures FSUIPC is not an issue)
PeterH
-
Malleeman
Which Operating system 32 or 64-bit?
You may need to turn of hyperthreading in the BIOS - FSX usually doesn't like HT and that can cause stutters!
Make sure that 'Pause on task Switch' is not ticked in FSX.
I assume your RAM is 8GB and around 1600MHz, otherwise at 8GHz it's blazingly fast :grin: ?
Are you running FSUIPC4?
Move your FSX.cfg file to a safe location and then start FSX so it can rebuild a new fsx.cfg file - still get the problem?
Regards
PeterH
-
Pete & Andy
Thanks - I did remove the Logitech software - should have said that and rebuilt all the appropriate ini and xml files. I had to remove the G940 as I couldn't fly the VRS bug with any degree of accuracy.
PeteD - I will reinstall the G940 in the next day or so and send the logging files.
Thanks for all of your help.
Regards
PeterH
-
Pete
Recently whilst you were away I had purchased a Logitech G940 system Initially I use the Logitech software and FSX to set up the controls in FSX. However, I experienced a lot of issues in terms of controller settings and sensitivities, so I decided not to use the Logitech software (disabled it) but instead use a mixture of FSX and FSUIPC 4 (4626) to assign and calibrate the various axes, keys and buttons. No problems in any of this in FSX. I then started FSX and then opened FSUIPC4 and went to "Axis Assignment" just to make sure that I hadn't any duplicate assignments. However, when I moved any of the G940 axes (eg ailerons, elevator, rudder, throttle) it changed the FSUIPC4 menus ie it moved randomly away from "Axis assignment" to another menu: eg it moved to "Winds" or "Visibility" in fact any of the menu choices but it would not stay on the Assignment page and show any details. No matter how many times that I re-chose axis assignment and "rescan", any axis movement changed the FSUIPC4 menu. (Rebuilding the FSX.cfg, standard.xml or FSUIPC.ini made no difference). In FSUIPC 4 calibration the axes assigned in FSX were recognised and I could set all the 'normal' calibration values and movement of the axis did not change the menu.
As you were away and I had a lot of other issues with the G940, I removed it from my system and reverted back to my Saitek X-52 joystick which performs flawlessly and doesn't change the menus in "Axis Assignment" in FSUIPC4. Unfortunately, I did not keep any log files, etc.
Really my question is - Have you seen behaviour like this before? Is there a simple explanation as to why it might have happened?
Thanks
PeterH
-
Brad
You do NOT need to use the SST (programming) software just FSX, and FSUIPC(4) if you need the extra extensive commands.
The Saitek driver software is useful to have as it gives quite a bit of info if you want to initially calibrate in Windows.
If you do use the SST programming software try to make sure that you do not have any duplicate assignments in it and FSUIPC.
I just use the driver software, FSX and FSUIPC4.
Regards
PeterH :rolleyes:
-
BA1
Just a thought Pete is NOT the trusted publisher it's actually "Simflight", so you usually check that to get rid of that error.
viewtopic.php?f=54&t=78080&p=475732&hilit=PeterH#p475732
Regards
PeterH
-
Garry
One thing that I forgot is that you may have an overwritten and now corrupt dll.xml file due to installed software. Pete Dowson can help you with that.
Regards
Peter
-
Thank you for your reply .The FSUIPC 4 in the module file appears to be okay,copied
FSUIPC4.dll to the add on, but still not working.The programming for dll.xml is there,
my IBM 2.1gb is where I start, adjusting the explorer would be the wrong thing to do.
Regards GarryR FTG CX268.
Garry
It should work OK but it might be worthwhile posting on Pete Dowson's (the developer of FSUIPC4) forum. viewforum.php?f=54 You may have a "simconnect" issue.
Regards
PeterH
-
Gary
You may need a little more info,
FSUIPC X when it installs into FSX it installs a FSUIPC4.dll in the main Microsoft Flight Simulator X\Modules folder
You will also find there: FSUIPC4.ini, FSUIPC4.key, FSUIPC4.log, FSUIPC4 Install.log plus FSUIPC documents.
If the FSUIPC4.dll is present and it has installed correctly then it should show as an addon in the FSX menus.
As Burkhard says the dll.xml file in the System drive C:\Yourusername\Appdata\Roaming\Microsoft\FSX\dll.xml
It should have a fairly recent date.
It should have an entry similar to:
-
FSUIPC4
False
Modules\FSUIPC4.dll
The dll.xml will be in a different directory and folder to the FSUIPC4.dll
As Far as I understand it neither the dll.xml and FSUIPC4.dll have anything to do with DIRECTX
Good luck :D
PeterH
-
CB
The same thing happened toumpy Tales!! IanP is to blame!!
pH
-
CB
Breaker One. (Ah, breaker one-nine, this here's the Rubber Duck) with apologies to CWMcCall!
For a minute I thought that I was the last person left standing!
Your response restored my faith in human nature! I am not alone!
Regards
pH
Sticky/Jerky Controls
in FSUIPC Support Pete Dowson Modules
Posted
Hi Jahman
I see that you are having issues with your CH controller and assignments.
I wrote the appendix (which PeteD generously added to the manual) as a step by step guide to a particular option in FSUIPC4, that a "newbie" could follow - it was really just to enhance and expand in a step-wise fashion PeteD's instructions in the manual. :razz:
I myself have a CH Yoke plus pedals and have no problems in FSX/FSUIPC4/CHCM.
This is what I do:
I do not use CHCM in "MAPPED" mode as I believe that there are some interactions between that and Win 7 calibration and may be with FSUIPC (BobC disagrees with me on that latter point). If I use CHCM I use it in "DIRECT" mode so that I can set the null zone exactly at the detente on the TQ6 and that corresponds nicely with the calibration settings in FSUIPC4 and so you get the reverse thrust occurring exactly at the start of the detente down to the minimum setting, and vice versa.
I know that you have said that you did not use the windows calibration - but I would still follow BobC's advice and use the "reset to default" (or the Logitech cleaner) option in FSX joystick calibration, so that all calibration settings in Windows are reset.
I would also back up both my fsx.cfg file and the fsuipc.ini file and remove them one by one and then let FSX re-build a new cfg file and FSUIPC re-create the ini file. (Yes, it is a pain but it can resolve lots of issues).
I would also check the current in-use standard.xml (in the system disk\user\username\appdata usually) just to make sure there are no issues there?
Sometimes you get "greyed out" buttons in FSUIPC when you are not expecting them, so if I see that I just "wiggle" a lever or the yoke and that can fix that problem. The CH game controllers don't alweays make themselves known when in an "idle" state and a "wiggle" wakes them up. :rolleyes:
If none of this or Pete's/BobC's advice works try changing the USB port hub (eg lots of USB issues in Win 7) or re-plugging the controllers in after turning off the computer, removing the power cord for several minutes, perhaps with a "clean boot" or suspect a hardware fault.
Regards
PeterH