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.

barneycanoe

Members
  • Joined

  • Last visited

Everything posted by barneycanoe

  1. Ah, I did get it working with the original fsx configuration, no aero tweak or restart, ie vsync in full screen mode and no vsync in windowed mode. Interesting side note: With FSTramp in full screen, if I enable it I lose the vsync but FSTramp works in fullscreen mode. Dave
  2. I have to run with the AERO tweak, if I try without it I get flashing and random intermittent graphics in full screen mode. I have tried the fsx.cfg vsync settings under both graphics and displays and neither works for me. Dave
  3. +100. Fabulous support and looks like the problem is sorted. One thing though, anyone have the MilViz 310 working successfully. I have a ref file for it and it won't work. Everything else is AOK! DISREGARD - 310 Now working! Dave
  4. Now, I did load up FS9 once and had no issues with default or add-on aircraft. FS9 is installed on C Drive. (Another reason I have FSX on F: is that it is a SSD drive.) So that once again points to the F: drive installation as being somehow the culprit, right? Surely the hardware if it is the issue would affect both sims? Intel Ivy Bridge Core i7 3770 Socket 1155LGA at 3.4GHz, Asus P8H77-M Motherboard Western Digital 2 TB WD2002FAEX-007BA0 ATA drive INTEL 60Gb SSDSC2CW060A ATA drive Cheers Dave
  5. Ah, I wondered what happened to them on my rig also. Dave
  6. Amazing, I can now see my Pilatus Porter (FSD), the ATR 72 (with some transparency) and my Carenado 182RG! Fabulous. Thank you Steve. Dave ps YYZ freeware airport scenery now works at night!
  7. Still trying to identify a common factor for the failures. I guess if I didn't have so many add-on aircraft it might not be so bad. Dave
  8. Well, thanks Paul. I will have to remember to read the HOW TO more frequently
  9. By Golly! This works. Here is what I did and what I think RNGR was trying to say. 1) Download ballast.txt file, rename to ballast.fx and place in FSX effects folder. 2) Make backups of fx_navred.fx, fx_navgre.fx, fx_navwhi.fx files from the same folder 3) Open ballast.fx, select everything from the [Emitter.0] to the last line, i.e. the entire rest of the file down to and including "Extrude Heading Max=0.00") 4) Open one of the three fx files and paste the copied text into the file at the END. 4) Starting with the beginning of your paste, rename your just-pasted [Emitter.0] to [Emitter.4], [Particle.0] to [Particle.4] and so on (if you are changing the fx_navred.fx for instance). The next three entries would be renamed to .5 5) Save, start up FSX and check for nav and strobe lights. Works for me! Dave
  10. Mark, any news on this problem? I'm still stuck with some a/c working, most not?
  11. I have been back and forth with MCE support for a week or so. It's very funny that it ONLY fails with add-on aircraft, and works perfectly fine with everything else though, don't you think? You can see my pc and sim specs in my profile, I was wondering if there was something we had in common. Since I NEVER fly the default a/c I'm in a bit of a pickle, though it works as advertised in the PMDG. Dave
  12. Mark, I am having the exact same issue. So far we have got nowhere with it. It fails with every add-on a/c except the PMDG. Real Air, Carenado, Digital Aviation, all no good. Failing somewhere with the aircraft recognition. When it works, as with the default Cessna, everything works perfectly. Still Stumped Dave
  13. Just remember that Addon Converter X will not change night, dusk or dawn textures for, for instance, the Flight 1 ATR. It will work for the daytime only. And Toronto CYYZ is the same. I got a refund for that program and just fly those sceneries in the day when they work fine. Dave
  14. Yeah, I'm kind of on the fence too. I am not noticing a frame rate hit. I will wait for one of the geniuses to fiddle with the settings and watch with interest. Good point about the monitor settings, too.
  15. Just Vancouver Plus and ORBX PNW demo. By the way, I have something turned on in the bios that boosts the cpu and it's showing around 4.0 GHz Dave
  16. Paul, thanks. I do have disable preload. Anyway, I removed the two force vcsync lines and got better results! I also rebooted before going back into dx10. Flew ngx yvr to Ksea in Rw weather, fps 20 to 25 but very smooth. Thanks for the tip (I always wondered about those force lines due to running 1/2 vsync in nvi) Dave
  17. Paul, this: Anisotropic=1 Here is part of the trouble, Dave: Antialiasing=1 This should be Anisotropic=1 and AntiAlias=1 is correct. I was in DX9 so copied from fsx.cfg and put in what I thought these were. I did have both aa and af ON in DX10. Procspeed=8 etc. No idea what this is, entered by fsx upon building the new fsx.cfg. I will take out the forcevsync lines but the first one I think cured by non-vsync of yesterday. LOD 4.5 is default for fsx. am doing this: Use 1/2 Refresh Rate and Standard, full screen and 30 locked in FSX Thanks for the help Dave
  18. Well half of your answer is probably like 100% of many others lol
  19. I am wondering if it is something specific to my system. I have read and re-read all the posts in this forum. I just tested again. Paul, I do not mean I always get 30 fps in every situation. What I was trying to say was that in several flight situations, I first load in DX9, then in DX10 and in these cases where I am getting 30fps in DX9 with the PMDG NGX it drops to 20-22 in DX-10. I have played around with many NVI settings. I just turned everything (aa) OFF (but checked in-game) including the SGAA and after clicking apply in NVI, i still had no shimmering in DX-10, it didn;t look any different. I think I have got my system working fairly well, just did a low level in the NGX at 250 knots and no blurring, even when changing views, 30 fps and then I loaded the ORBX weather theme #5 and it dropped to about 25 fps. That's in DX-9. For some reason, in DX10, I'm taking a hit. Also, I have the VSync problem back again. Have to see if I can fix it again. Cheers Dave. Edit, here's the relevant pieces of my fsx.cfg [bufferPools] UsePools=1 PoolSize=8388608 RejectThreshold=131072 [GRAPHICS] ForceFullScreenVSync=1 ForceWindowedVsync=1 HIGHMEMFIX=1 //MultiSamplesPerPixel=4 // 4 //MultiSampleQuality=8 // 8 D3D10=1 SHADER_CACHE_PRIMED_10=1693500672 SHADER_CACHE_PRIMED=1693500672 TEXTURE_MAX_LOAD=1024 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=1 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=1 AC_SELF_SHADOW=0 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 [Display] //ForceVSync=True ChangeTime=4.000000 TransitionTime=4.000000 ActiveWindowTitleTextColor=255,255,255 ActiveWindowTitleBackGroundColor=0,28,140,64 NonActiveWindowTitleTextColor=255,255,255 NonActiveWindowTitleBackGroundColor=24,33,87,64 InfoUpperRightTextColor=255,0,0 InfoUpperRightBackGroundColor=0,0,0,0 InfoLowerLeftTextColor=255,255,255 InfoLowerLeftBackGroundColor=255,0,0,128 InfoLowerRightTextColor=255,255,255 InfoLowerRightBackGroundColor=255,0,0,128 InfoBrakesEnable=False InfoParkingBrakesEnable=False InfoPauseEnable=True InfoSlewEnable=True InfoStallEnable=False InfoOverspeedEnable=False BLOOM_EFFECTS=1 SKINNED_ANIMATIONS=1 TEXTURE_BANDWIDTH_MULT=120 UPPER_FRAMERATE_LIMIT=31 WideViewAspect=True RUNWAY_LIGHTS_SURFACE_SCALAR=.6 //adjust values to suit your scale RUNWAY_LIGHTS_VASI_SCALAR=.6 RUNWAY_LIGHTS_APPROACH_SCALAR=.6 RUNWAY_LIGHTS_STROBE_SCALAR=.6 [TERRAIN] LOD_RADIUS=4.500000 MESH_COMPLEXITY=100 MESH_RESOLUTION=23 TEXTURE_RESOLUTION=29 AUTOGEN_DENSITY=3 DETAIL_TEXTURE=1 WATER_EFFECTS=5 [Main] FIBER_FRAME_TIME_FRACTION=.15 User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc ProcSpeed=8584 PerfBucket=7 Location=440,151,1480,929,\\.\DISPLAY1 HideMenuNormal=0 HideMenuFullscreen=1 Maximized=1 DisablePreload=1 [DISPLAY.Device.NVIDIA GeForce GTX 660 .0] Mode=1920x1080x32 Anisotropic=1 Antialiasing=1 [DISPLAY.Device.NVIDIA GeForce GTX 660 .1] Mode=1280x1024x32
  20. Need some help here. I have followed all the advice in the doc. In dx10 with pmdg ngx i get steady 30 fps in all outside views and about 20-22 in VC. Dx9 I get locked 30 fps everywhere even with better aa set. All my other a/c are faster than the ngx so that is why I use it for testing. There is something specifically slowing it down as even if I pull all the sliders back to mins I still can't. Get 30 fps in the VC. Dave
  21. I solved my no vsync problem. Spent about 6 hours on this yesterday and after having the "force v sync " line in my configuration, at some point I moved it to the (display) section, with the slightly different terminology (ie true instead of 1). At some point I moved it back under graphics and "poof " vsync was working again. Don't know if that was the fix, but it is working now.
  22. Thanks Paul, I'mgoing to revert back, I thought the same, there was just something not as good about the graphics although the frames seemed a bit better. By the way, I'm in Stouffville, ON. (actually, Altona) Cheers! Dave
  23. On a slightly different topic, was reading the post elsewhere about using Vsync in windowed mode (as I have the NGX and need to read the tutorial step by step) and I now have lost the fullscreen Vsync in DX10 - using 1/2Vsync setting in Inspector. I did download the latest Nvidia driver this am (306.97). COuld a driver break the Vsync? Dave

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.