Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Radar contact atis incorrect

Featured Replies

  • Commercial Member

out of curiosity were you talking about the below line as I still use this in my old profile.

 

Yes, that's the parameter, though I'd recommend it simply be deleted. The "UseASEweather=Yes" setting forces FSUIPC to use ASE/AS2012 weather in all modes, not just DWC, which is really unnecessary. If the parameter is omitted it does the correct thing automaticaly. Only setting it to "No" will make FSUIPC ignore the presence of ASE/AS2012.

 

I suppose moving forward i need to be careful using an old FSUIPC.ini incase there is a value change or addition added in a new version.

 

I try very hard to maintain compatibility, and really nothing serious has changed in years. Where a function is changed so that older parameters could cause problems i invent a new parameter instead and either ignore or auto-delete the old one, so no harm is done. I really cannot expect folks to deelte and re-build their settings for each upgrade, even major ones, as many users have built up very complex and comprehensive assignment/programming settings.

 

I have about 7 different FSUIPC.ini files that are swapped out based on the hardware configuration needed for different aircraft,

 

Why not just use the aircraft profiles facility and let FSUIPC do the job for you automaticaly as you load different aircraft? That's what the facilities are for. Even the original aircraft-specific facilities which have been there for many years would also do that job.

 

Regards

Pete

Win10: 22H2 19045.2728
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3800 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 25Hz onto 200 FOV curved screen

  • Author

Pete

 

Many thanks next time I rebuild I will look at utilising FSUIPC for the profiles, hopefully that wont be for a while take ages to get the dam thing right so complex, seem to spend so much time fixing as opposed to flying, cheers again

 

Regards

Wayne

Wayne such

Asus Hero Z690, Gigabyte Aorus Master 5080, I914900K, Kraken 360 AIO CPU Cooled, 96 GIGS Corsair DDR5, 32 Inch 4K by 3

  • Commercial Member

Many thanks next time I rebuild I will look at utilising FSUIPC for the profiles, hopefully that wont be for a while take ages to get the dam thing right so complex, seem to spend so much time fixing as opposed to flying,

 

Don't tell anyone else, as I don't want to be inundated, but if you'd like to ZIP up the 7 different INI files I'll make a merged one with each set of different assignments and calibrations as separate named profiles. Just give me a suitable profile name for each one (not too long, but meaningful), and also at least one aircraft name (or part of the name sufficient to match it) for each one. It is easy enough to do -- just a matter of cut and paste mainly.

 

Then for any aircraft not already covered by the names you provide, when you load it next you simply assign the relevant profile. And that's it.

 

Send ZIPped files to [email protected]

 

Regards

Pete

Win10: 22H2 19045.2728
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3800 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 25Hz onto 200 FOV curved screen

  • Commercial Member

"Send ZIPped files to [email protected]" make that [email protected] .

 

Oops. thanks Ronzie! (Corrected original now).

Pete

Win10: 22H2 19045.2728
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3800 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 25Hz onto 200 FOV curved screen

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.