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.

The FSX SP2/Acceleration incompatibilities thread

Featured Replies

  • Author

>>So far I found the T34-B Mentor aircraft from Carenado not to>work right in SP2. The cockpit panel in the Virtual Cockpit is>all gooey grey. Probably a victim of dropping some backwards>compatibility.>>If anyone knows how to fix this beautiful payware for SP2, let>me know.>>Any other incompatibilities found? Report them here.>cloud9 mco scenery does not seem to work:( keith

  • Replies 57
  • Views 16.2k
  • Created
  • Last Reply

Top Posters In This Topic

I'd like to know if all these reported problems are encountered with the "DirectX 10 Preview" checked under display settings. I didn't notice any major issues if I left that unchecked.I am assuming this is the problem causing a lot of the reports in this thread. Of course, I bought Acceleration to check that option, but then I had all these problems with my add-ons....:-roll

Scott

Actually, if you go the word from Aces then, yes, they have continuously claimed that backwards compatibility was a major show stopper in moving forward. However, fact is that the majority of FS9 add-ons are NOT compatible with FSX, which kind of invalidated every statement that Aces has ever made about backwards compatibility. Where? I have paid almost the same retail price TWICE for add-ons that do not offer one bit or very marginal improvements in terms of performance and feature enhancements.DX10 for FSX was never advertised as a "preview", but as a DX10 update. That update just somehow got forgotten, same as with the Vista DX10 for Aero update that was supposed to be available this summer.Of course, a break in compatibility is necessary, but I find this codebreak completely unnecessary at this very point in between releases, because with the current state of affairs, DX10 does not improve one bit of anything in FSX - not performance-wise, not in terms of feature enhancements. Sure, now you have cockpit shadows and bloom - for a price tag of $300-$400, but you have virtually no DX10-compatible addons. I don't see the benefit unless you are happy to fly the default aircraft.The is no risk in being an early adopter, if things are done right. There are plenty of DX10 games out there and coming that do not show any of the symptoms as described by Aces. Sure, I will sacrifice backwards-compatibility for a significant gain either in performance, graphical goodies or feature enhancements. DX10 for FSX does not feature neither. It is merely a technology preview for Aces to see that FSX can be rendered with DX10. For the end-user this "milestone" can be easily shrugged off - and ignored.From a developers point of view, this must be how #### must feel like. Not only were they plagues to port their add-ons to FSX, but the add-ons needed to be made compatible with Vista, with 64-Bit and now with SP2 and eventually with DX10.Pat

>When you check/uncheck the DX10 Preview box, you need to exit>and restart FSX to change from DX10-DX9 or vice versa.>>Once you re-exit and re-start, does that not revert you?There is no DX10 Preview Box.Jeff

To "see" the DX10 preview box you need:1)Vista2)DX10 hw ( nV 8xxx series, ATI 2xxx series )3)Accel or SP2 ( when it comes out )if you dont have all 3 of those, you wont get the preview checkbox because it cannot be enabled.you can validate DX10 is enabled by turning on aircraft self-shadowing and you should see the VC shadows.

ex-Aces Lead PM, FSX SP1 and SP2
ex-Intel LRB native title enablement, ex Intel Gaming and Graphics Samples PM

now Graphics and Multicore PM in Visual Computing Software Enabling.

Well I for one lose about half my total framerate going from dx9 to dx10 with the same saved game and leaving the options the same. Sitting at the f16 hangar at edwards i went from 39fps in dx9 to 16.5fps in dx10 without adding any options. Dx10 is a disaster for me. Drivers also make no difference. I thought dx10 was supposed to give me 20% better frames with bloom AND water 2high enabled? I really don't mind the addon incompatibilities because i expected that, but i sure didn't expect to halve my framerate with the same graphics options. Let's not even get into the cockpit shadows that make the sim lag and stutter when enabled and are full of stair step jaggy lines. I bought this stuff to run fsx in dx10 based on all the early promises and to say i am disappointed now would be an understatement.

So, briefly stating: The SP2 is pretty much incompatible with YOU ;)

No, actually its pretty great overall. The best $17 anyone could spend as long as they don't plan to run dx10. Edwards alone is worth $17! I am just trying to figure out how they said dx10 was going to add more framerate with the same options or allow me to increase options and keep the same framerate but in reality i lose 100-200% of my framerate with the same options checked. The big question is what did they see during the beta test? Dx9 runs smooth as silk but dx10 is just a debacle.

Well some future nVidia drivers will sort that out for you, I am sure. Myself, I still have to get Vista and a DX10 graphics card. But it is not not particularly urgent - For now, DX9 seems to fulfill most of my wishes and there appear to be LESS rendering issues with addon aircraft using the DX9 code path.

"Anyone else see the white texture problem on the outside of fs9 planes or know of a solution?"- yes, after installing Acceleration + SP2, about 90% of all my aircraft, including most of the Flight One Ultimate Traffic X AI aircraft appeared as white models with no texturing at all. The problem seems to be DX10 related. Switching to DX9 mode the aircraft mostly looked OK. It was mainly the older FS9/FS8 aircraft that had problems, but some of the FSX compatible aircraft had issues too.- a further DX10 bug that I noticed is that airport boundary fences get drawn IN FRONT of clouds! So when approaching an airport at high altitude in a situation where there were clouds between the airport and my aircraft, I couldn't see the airport but there was a boundary fence apparently sitting across the cloud surface!- yet another issue I noticed when using the top-down view at YBAF airport, at a certain zoom level, the scenery went all spastic with random flat coloured polygons splaying out everywhere.

Hello,Apart from the random ctd when accessing the menu with the alt key, Megascenery Hawaii has about 100 yards of sea around it and then the rest of the Pacific is covered in land textures. I also have a problem with SoCal-runway textures appear currupted and there also seems to be land masses over the sea. I'm using XP and a 7900Gt graphics card. RegardsChrisS

I assume some of those running Vista with a 8800 card or one that can handle Direct X 10, have noticed some textures for acft be they add on or payware, Wilco pub or Commercial Level Sim's DC-10 or FLight one Ultimate traffic, will of noticed that outside afact textures are displaying all white with Direct X 10 preview turned on.Why has this happened.

That is the 64 million questionMS has left it to add on devlopers to fix the problemBut by the time they do, we'll almost be close to FS11 coming outWhy not leave things as they are while some devlopers are still designer there add on's using XPsp2 and Direct X 9This is apparently what UT designers used to Beta test Uiltimate Traffic, if that is true, why did they bother beta testing using a soon to be obsolete Operating system

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.