Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. I set the sensitivty for the axes within FS2020. My values are Joystick -- (Pitch & Roll) L AXIS X -70% L AXIS Y -70% Throttle -- L AXIS X 1% ( I Do not use this - It is the mini joystick at the back of the throttle) L AXIS Y 1% ( Not used ) L AXIS Z 1% ( Left Throttle - I leave this to the default set by FS2020 ) R AXIS Z 1% (Right Throttle ) SLIDER X -25% (The Slider - I use this for Elevator Trim) Note that the Dead Zone is set to 2% everywhere. My Warthog is about 8 years old so I am making sure that any 'noise' generated does not impact the simulator. My Rudder and Toe brakes are controlled by a CH ProPedals device. I am still experimenting with the settings on this and have not yet come to my optimum settings for it.
  2. I have taken a different approach to using FSUIPC. I use the TARGET Software and have created a profile which is very similar to the one I used for FSX. By doing this I have not had to totally re-learn the button presses. HOWEVER - FS2020 does not fully recognise the 'Thrustmaster Combined' device created when Target is run. To get round this problem I ran FS2020 WITHOUT Target runnng so that FS2020 saw the separate Throttle and Joystick devices. Initially I copied the default profiles for these devices. Next I completely removed all settings within these profiles so that now I have clean profiles to work with. I then set the assignments for Axes and Camera Views using FS2020 in the blank Throttle and Joystick profiles. (I had found that FS2020 would not react to the hat switch for panning, nor the axes in the 'Combined' device.) Save all the profiles with their changes. Stop FS2020. Now run Target with the FS2020 target script followed by FS2020. Check that the 3 devices Throttle, Joystick, and Combined are all there and with the correct profiles. FLY ! and check that the controls work as hoped.
  3. The list of possible places to find the file to be modified is missing one option. I chose to put the files for the simulator during installation on my G: drive in a folder FS2020 and this is where the file to be modified is stored. I look in G:\FS2020\Official\OneStore\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\BaseInstrument.js
  4. Just checked my settings for these pedals in P3D V4 and the axes assigned to brakes have the reverse option ticked. Trevor
  5. I had a similar problem recently. In my case when I pressed a key on my Hotas Warthog which was set as a 'Shift' key, the elevator trim would go to fully up. I traced it to the keyboard settings in P3D. I found that 'Button 3' and 'Button 4' were assigned by default to be ones which controlled elevator trim. These were in addition to the other keys assigned on the keyboard for the same trim. Solution was to delete the settings assigned to Buttons 3 and 4. I have just reinstalled P3D from scratch and I normally delete all default button assignments but I missed these 2.
  6. For solution 1 - Called Storage Spaces - please fully backup the data from your P3D drive before creating a space. The process of creating a space destroys the data on the drives. During creation give the space the same letter as the P3D drive. Afterwards copy the backed up P3D data back to the new space. Once a space is created disks can be added as needed. Individual drives within a space do not have to be the same size. You can add a normal hard drive to a space but I don't know how any defrag software would deal with a mixture. I have done this with 2 SSDs, one is a SATA drive and the other is NVMe storage neither of which should be defragged. I suspect that using solution 2 - RAID setup - may give better overall performance but I personally found it easier to go for solution 1.
  7. There is a facility in Windows 10 called something like - Storage Pools. With it you can put multiple hard drives together in a pool and Windows treats the pool as a single drive with just a single access letter. I had your problem recently so I bought a new SSD and made a pool of my current FlightSim SSD and the new one. Because I am ultra cautious I backed up my original G Drive (FlightSim) to an external drive before creating the pool. Drives do not have to be the same capacity or even type. There are also several types of pool you can create. The help information is good and of course you can search the internet fot guides. After creating the pool and giving it letter G I restored the data from my backup. Window manages where data is physically stored. The other thing worth noting is that additional drives can be added to a pool without the need to back up the existing data. If you have room physically for an extra drive this may be an option for you.
  8. Windows.old is needed if you want to roll back to your previous level. If you are happy with the new version then the folder can be removed. The best way to remove it is use the disk clean up facility provided in the system. There may be other ways to get at it but I use the right mouse on the C: drive in explorer and select properties. Disk clean up can be found in there. You must select the option for System Files. This will give a set of tick boxes one of which is to remone the old release. I can't give you the exact wording as I am away from my system for a few days. When you tell it to execute your command you will be prompted to confirm the removal of old releases and installation files as an added safety precaution. After execution is finished - no more Windows.old !! And 25gb freed.
  9. The update is out. Some of the planned changes have missed this fix pack. Details can be found by reviewing the news item about FSW on Steam.
  10. A couple of other checks for you .... Make sure that the module has not been disabled in the DLL.XML settings file. (This is where I turn RAAS off !!). If you have modified your scenery and possibly any airports then you may need to run the MakeRwys program to update some data RAAS uses. My copy of MakeRwys is in the folder where I save the Pete Dowson FSUIPC4 files.
  11. I would also like to add my thanks. Although I did not have the exact same problem it pointed me to the solution. My solution was to search the following folder. "C:\ProgramData\Microsoft\Windows\Start Menu\Programs" for the "TODO" folder. You will need to unhide "C:\ProgramData" to search down this path.
  12. I too am running Windows 10 with Fsx (non Steam) and I don't have the stutters. The sytem was set up from scratch rather than by upgrading. FSX was installed on a separate partition away from the 'Program Files' folders. Tweaks to the FSX.cfg file were copied from the Win 7 install. The NVIDIA drivers are the latest and Inspector was used to tune Nvidia. Some of the things I have done may be worth considering. --- Win 10 come with loads of bloatware. Do you really need a Camera app on a Desktop? I removed all unwanted apps. Check the internet for the powershell scripts which do this For wanted apps turn OFF the live tiles. Run a virus scan on your FSX folder then turn off runtime scanning of that folder. You must rescan manually for each new addon or update. Keep the FSX drive defragmented. If the drive is an SSD then this is not advised.
  • Create New...