camadidu

Well, it happens that the error was not located in the fsx.cfg file! I replaced the new file with the old one I had, and the simulator doesn't crash. So, the error is probably in the dll.xml file. When I say "tweak FSX", I mean this very lines of code that make FSX perform better in my computer and reduce the horrible balloon effect that comes with the default FSX lights. [BUFFERPOOLS] Usepools=0 [Display] RUNWAY_LIGHTS_APPROACH_SCALAR=0.65 RUNWAY_LIGHTS_STROBE_SCALAR=0.7 RUNWAY_LIGHTS_SURFACE_SCALAR=0.75 RUNWAY_LIGHTS_VASI_SCALAR=0.5 WideViewAspect=True TEXTURE_BANDWIDTH_MULT=80 [GRAPHICS] HIGHMEMFIX=1 [JOBSCHEDULER] AffinityMask=14 [Main] DisablePreload=1 HideInfoText=1 [TERRAIN] TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=2000 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800

Ok, I read the CTD guide. I let FSX bulid a new fsx.cfg, dll.xml and exe.xml and now there are no more CTDs. Now, I'll have to tweak the fsx.cfg file to get the simulator to perform better; with the default file, it runs very poorly. I'm glad I didn't have to reinstall FSX.

Well, two things. First, FSX was working wonderfully before I installed the two aircraft I mentioned, which are not from P3D. I hadn't had a CTD for over a year! It used to be a very stable simulator. Secondly, I can't tell if the error was caused by the two aircraft mentioned, but, really, there's no error report relating to FSX. Probably the simulator is not crashing per se, but there is something forcing it to close unexpectedly. I'll read the AVSIM CTD guide and let FSX build a new fsx.cfg, dll.xml, exe.xml and scenery.cfg to see if the problem gets solved (which I don't quite think it will).

Hi guys. I really need your help. FSX was performing well on my system until I installed that freeware Lockheed Constellation that is so popular, I 'll get the name for the next post. Lh, and a DC-4 from the same website. After I uninstalled these two add-ons, FSX was getting a CTD with the weather.dll file. Then, with the api.dll file. So, I repaired FSX and now I was getting an FS_Recorder.dll-related CTD. So, I uninstalled FS Recorder v2.18a. But then, FSX will load with nk errors, and I can set up and launch my flight. A few seconds after the flight is loaded, the simulator crashes to desktop, nut there is no message of any error whatsoever. I've tried to see in the AppCrashViewer and in the Windows Event Viewer if there is any error report, but there isn't any. Is there anything I can do to fix this issue? Thanks.

I can't say which one is better or worse because I've only tried IVAO—and I've liked it so far. I don't quite yet understand the argument IVAO ATC is not very professional. Rubbish! While it's true that any controller can log in to IVAO on a TWR or GND frequency, there are theoretical and practical exams you need to pass in order to control the APP and CTR frequencies. And the ATC has sounded very professional to me at IVAO. Yes, IVAO doesn't support (yet) VHF simulation as it uses TeamSpeak 2 for radio communications, but that doesn't matter to me. Something that is definitely better on IVAO is the quality of the AI traffic. It's simple, IVAO wins over VATSIM on this. The last point I'd probably like to mention is coverage and events. Again, I can't speak about VATSIM because I've never used it, but I mostly fly in Colombia, Brazil, and Europe. IVAO has good coverage in these areas. Of course, there will always be far less ATC and traffic if its working time where you want to fly, but in the off-work hours and Sundays, there are plenty of options for me to fly. However, if you mostly fly in the USA, go with VATSIM. IVAO is starting to get a grip on the USA, but VATSIM is still far more popular over there. IVAO has a lot of events. There are at least one or two events per week—often, there are three or four, or even five! Most of them are held during the weekends, as this is the time when most people have spare time for flight simulation. I don't know about VATSIM events, so I can't speak about them. _________ Well, this is my opinion about IVAO. I decided to give it a try and I've enjoyed it a lot! The same thing at this end. Most of the fun part of flying occurs close to the airports, so I don't like doing flights longer than 3 hours ETE.

Your standard recipe did not work with my rig. Ugh, I'll have to stick with DX9.

I'll try that. Let's see how it works. Thanks for your help. :-)

I give up . No matter what I try, I can't get the ATI Radeon HD 7670M SSAA to work with FSX DX10. I will try again, but I don't think it will work. It seems I will have to run DX9 until I change to a new computer with a Nvidia card--and it won't be any time soon.

Even though FSX only recognises the Intel Card, that doesn't seem to be an issue because 1) the activity of the Radeon card increases when I'm using FSX, while the Intel GPU's activity remains rather constant. 2) when FSX is set at CCC to run in the power-saving mode, it is extremely laggy and such, but when it is set to run at high-performance (like I always do), it works way better. 3) RadeonPro settings affect FSX's graphics.

RadeonPro. I have a laptop. There is no way I can remove the ATI Radeon 7670M and install a Nvidia GPU without possibly breaking something.

And how on Earth can I do that in my ATI/AMD card? I can't believe FSX DX10 looks at least decent in my laptop but planes are unflyable because there is no way to read their gauges.

Somebody please shed some light to me. Seeing the two pictures above of the A320's VC (and doing another FSX DX10 test), I have noticed something very weird. Everything but the PFD, the ND and the ECAMs 1 and 2 are affected by the antialiasing options. Their "readability" does not improve with AA activated. Nevertheless, everything else gets better (or is good already). Any ideas on why does that happen?

I want to share some advances with you guys. 1. I still cannot understand why full-screen FSX is black. I (tried to) click where Ron says but it made FSX no better. Windowed mode works perfectly. :blink: One thing I did notice was that after I click "Fly Now!", but before the loading dialogue appears, the screen flashes and goes black and on again like if it was doing a driver installation or update. The same happens when changing from full-screen to windowed mode and vice versa. (I have an Intel Graphics HD 3000 and an ATI Radeon HD 7670M with switchable graphics. FSX is set to run at high performance in the CCC settings.) 2. I let FSX build a new fsx.CFG file and then I applied the following tweaks: [GRAPHICS] HIGHMEMFIX=1 MultiSamplesPerPixel=4 [Display] WideViewAspect=True RUNWAY_LIGHTS_APPROACH_SCALAR=0.65 RUNWAY_LIGHTS_STROBE_SCALAR=0.7 RUNWAY_LIGHTS_SURFACE_SCALAR=0.75 RUNWAY_LIGHTS_VASI_SCALAR=0.5 [bufferPools] UsePools=0 [JOBSCHEDULER] AffinityMask=14 [Main] DisablePreload=1 FIBER_FRAME_TIME_FRACTION=0.18 Location=-4,-4,1370,744,\\.\DISPLAY1 Maximized=0 // The last two entries appeared by themselves after the first FSX run with DX10. I have no idea what they are. [TERRAIN] TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=2000//1000 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800//700 [DISPLAY.Device.Intel® HD Graphics 3000.0] Mode=1366x768x32 Anisotropic=1 AntiAlias=1 [DISPLAY.Device.Intel® HD Graphics 3000.0.0] Mode=1366x768x32 Anisotropic=1 AntiAlias=1 // [DISPLAY.Device.etc] was set by FSX itself. 3. Here are some comparison shots, with FSX-AA disabled and FSX-AA enabled. I still did not get the best AA ever (I have very good AA in DX9), but better something than nothing. ^_^ (Real images resolution is 1366x768. Please click to enlarge them or open them in a new tab.) AA disabled AA enabled ___ AA disabled AA enabled I think that, perhaps, increasing the MultiSamplesPerPixel from =4 to =8 should help to improve AA in FSX DX10. P.S.: The aircraft is Project Airbus A320 FD-FMC version and the scenery is VirtualCol Colombia Virtual Xtreme Edition 2011 (SKCL airport). Here I add a picture of GPU-Z 0.7.7 showing the Radeon 7670M's performance during the FSX DX10 test.

It doesn't matter if you are using his fixer or not. If you can't run AA properly without the fix, AA will be no better with Steve's fix (or so I think). Of course, you need to add the MultiSamplesPerPixel=# tweak to make AA work in DX10, but you can add it anyway without Steve's fix, which is mostly for the shaders, effects and some textures. But isn't Optimus for nVidia graphics? I have an ATI Radeon.

Hello. Let me start with my system settings. HP Pavilion g4-2064la Intel Core i3 @ 2,3GHz 4Gb RAM Intel HD Graphics 3000 (integrated) ATI Radeon HD 7670M (dedicated) - Switchable graphics FSX with SP1 and SP2 I've forever used FSX in DX9 mode, but recently wanted to try DX10 and see how it works. Even though the FPS have never been so good in my computer and I have applied the fixes, antialiasing is terribly bad. I have already applied the MultiSamplesPerPixel=4 in the fsx.CFG [GRAPHICS] section and the "Use application settings" in RadeonPro's AA options (I also selected Multisampling (Box)). Anyway, the AA should work, but it does not function very well. I also get a black full-screen view, but I can see everything if FSX is running in windowed mode. Thanks for your help. I suppose I should start by letting FSX build a new fsx.CFG file, shouldn't I?