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.

Anti Aliasing not broken but Model related?

Featured Replies

I have noted the repeated concerns a lot of people have about the state of the Anti Aliasing in XP12. I have to confess I have never noticed it as an issue for most of the aircraft models I fly and the scenery (including shadows) so shadow lines and lines in general were always crisp and not blurred or feathered for me - until today. What changed? I am trying out a new model (well focus has been on model functioning not its overall appearance given it is an XP11 rebuilt for XP12) so now with this model I see all the anti aliaising issues, blurry lines, strange feathering here and there etc. So my conclusion it has to be the quality of the model its component parts and textures that is to say they are not good fits or clean lines etc and all the light engine of XP12 is doing is magnifying those otherwise unseen faults or issues. The only conclusion I can draw never seen it before or noticed until with this model (probably there are others) back to another model no anti aliaising issue at all. 

Yes or No? Seems that way to me!

59 minutes ago, coastaldriver said:

Yes or No? Seems that way to me!

this will possibly be the vram/screen space related issues - first batch of fixes due to drop in 12.06

not so much the model as certain material settings set it off.

the default MD wings are an example.

Edited by mSparks

AutoATC Developer

  • Author

Ok, yes first time I had seen this so distinctly but then again after a few bad experiences with XP11 models that could not be ported to XP12 (Still waiting on supposed updates on these payware items) I have avoided anything really that was not XP12 - this latest model is XP12 but a private effort bringing what was an still is an excellent XP11 model into the XP12 world. Still a lot of work to do it seems! Though basically it is now performing very well. 

And if anybody is curious it is the old Riviere Dash 8 (100, 200, 300 and 400) now being reworked by Manky1. As I used to fly the Dash for real I have been helping out where I can with data etc. Still have issues with the way turboprops and their props are modelled in XP12m specifically Beta Range means that but not very well handled in XP at all. 

FMOD of course is another bone of contention - come on LM lets get the manual updated (SDK) to relate to both the latest FMOD and XP12!!!

The AA issue people complain about refer to the flickering that occurs in the distance on scenery items, not aircraft. 

Setup: RX6800 | 5800X3D + B450 | 32GB 3200MHz | X-Plane 12

4 hours ago, bogdansrb said:

flickering that occurs in the distance

thats also believed to be a vram (paging aiui) issue.

first fixes due to drop in 12.06, but afaik you dont get that one with orthophoto

AutoATC Developer

Night-time gives nicer results I find. 

Jude Bradley
Beech Baron: Uh, Tower, verify you want me to taxi in front of the 747?
ATC: Yeah, it's OK. He's not hungry.

X-Plane 12 and MSFS2020  🙂

System specs: Windows 11  Pro 64-bit, Ubuntu Linux 20.04 i7-13700KF  Gigabyte Z790 RTX-4060-Ti , 32GB RAM  1X 2TB M2 for X-Plane 12,  1x256GB SSD for OS. 1TB drive MSFS2020

Archived

This topic is now archived and is closed to further replies.

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.