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.

Paul J

Members
  • Joined

  • Last visited

Everything posted by Paul J

  1. Hi Sambo: One man's experience, FWIW - an easier way to achieve that 30 frames+, with much greater immersion and without the connectivity, cost and space issues would be to make use of Nvidia's "Surround" function, along with NaturalPoint's "TrackIR" viewing system. The TrackIR reflector can be attached to the band of a headset with a couple of screws, rivets, w.h.y, in a minute or two, and Surround can be setup within ten minutes. Your 980 is more than capable of running three monitors at a pretty high resolution. I ran 3840 x 1024 for several years (three 19" @1280 x 1024 Viewsonics), and a friend of mine is running 5760 x 1080 (three 27" @1920 x 1080) on a pair of GTX 580's. If you then want to lessen the load with a second PC - get one and run your secondary FSX software on it. pj
  2. Yeah - I hear you Jose'. RC is a great way of pursuing "hobby aviation" without the cost of licenses, instructors, hourly rental prices - and then, what do you do once you have a PPL? It's fine for the more wealthy folks among us, but I'm an "average joe", (retired now) and a normal life takes up most of the income of most of the rest of us. RC has many other benefits, too - it's an outdoor sport - healthy; it satisfies the creative urges in us; we meet lots of folks who share this same crazy passion - and we get to stretch our imaginations, as we do in the flight sim: we are in the cockpit: it becomes "real"! I don't fly RC anymore, either, (the sim got in the way) but here's some old pics.. All the Best!
  3. I'm afraid I can't help you with Fixer settings anymore, Jose' - it's all gone out of my head! FSX is still on my machine, but I took all the cockpit hardware, pedals, yoke, etc., out, and it's now languishing in the back of my garage gathering dust. I haven't used FSX for over a year and I see that Steve has changed it so many times since then I wouldn't even begin to know where to start! I can only suggest you try ploughing through Steve's Wordpress achive: I think Steve will respond if you log in there and ask him - but you might be faster by doing the same here on the official DX10 support site here at Avsim. Sorry, my friend, Id love to help again, but the sands of time have shifted! All the Best, pj
  4. Hey Ric! Thank you for the post! It's nice to know the you're still around too! Yup - still get emails, and still visit here occasionally. There's a lot of folks that I really enjoyed conversing with - the list is too long, but you know them all. I miss everyone. All the Best! pj
  5. Hi Jim: The rule of thumb is that if you only have a single monitor - then set the Multi-display/mixed-GPU acceleration to Single-display performance mode. My setup (TH2G) was quite often set to "Multi", but I'd be pretty sure the GPU sees TH2G as a single monitor, TH2G having it's own independent control system, so it should probably be "Single". In any event - try each setting, recording your fps and simply set it accordingly - you're not going to hurt anything! pj
  6. Absolutely: dhc11.air is the final version of the modified airfile, Holland, and is included, along with a couple of other sounds sets. Hope you get as much enjoyment out of her as I and hundreds of others have! pj
  7. Very old member here, Holland... saw your post and went digging... Here she is... some pics... haven't flown her in a while, though.. may be a few rusty parts and a flat battery... fine in DX10. If you have problems ask back here - I'll watch for a day or two; All the Best, pj
  8. Nice of you to inquire JH - thank you - and all is well, but no, I'm not back; one can't recapture the past: people grow; lives change and folks move on to other interests. Too much water under the bridge, I'm afraid. Steve's Fixer has "fixed" most all of the DX10 issues that existed three years ago, and much of what remains is largely cosmetic. Also there is a large enough knowledgebase here - and on other sites - to help newcomers convert as they wish, and so the demand for whatever skills I may have had are not there any more - but I do like to drop in from time to time! Anyway - All the Best, pj
  9. You have a normal user on both machines, and are using that user to map the drive: After you've entered the mapping address - you are presented with a login interface. Is that user the owner of the folder, and does it have full permission granted? Some pics of this process are here. How much of this do you see? Another note: (sorry!) Here's a series of pics to show the process of changing network permissions on the pc. I've removed the "Everybody" user, and replaced it with "pj"., as "Everybody" includes the whole world...... Capture 9 shows some system items that should be checked, too. While you're about it - take a look at the "HomeGroup" sharing system of W7. It may work a little easier maybe?
  10. As quick addon to the above - a good move would also be to put your desired shared folders on a different drive completely, and share it - not the C drive. That way you will have access to all of the drive - you being the owner/creator. In the case of sharing the C drive - the system's hidden users will not permit "easy" sharing of most of the C drive folders. pj
  11. Windows Explorer -> Tools -> Map Network Drive: Accept the offered drive letter - usually "Z", and type in the next line (without the quotes - and POGO is the name of my wife's machine - yours will be something different) "\\POGO\C$" You may also want to log in using a normal username to the other machine - not the Administrator name...
  12. Hi Ezio: Check this link here. Adamski_NZ now has the Guide, and you'll find all of the new links inside - ok! All the Best, pj
  13. Naah... Good suggestion, Spirit, but I'll pass on it. I've thought about the move many times, but Steve's DX10 Fixer was always of greater importance. To be honest - I haven't flown in several weeks. I built an MD-80 TQ over the summer - and with most of the right functionality, too (Desktop Aviator USB cards) but have yet to use it. Also over the spring and summer - we had to re-lay the pipe from our house to the sewage disposal bed: take down a few trees, build a retaining wall, install three new windows, seal and insulate the crawl area under the kitchen and bedrooms, re-do our heating system, plus build a new shed to take the lawn mowers and garden equipment as well, and - being a couple of months shy of being 70 - I'm running out of steam. Arthritis is playing some part, too, and I just can't seem to get the interest back. On top of that I had to get some new bits and pieces for this black box under the desk...... (Aaaargh... if you know what I mean <_< ) I suppose it's called "life"! All the Best, mate! pj
  14. Neither pic is adequate to demonstrate blurring, Yildrim. It is not apparent in night shots, nor in a top-down pic. Blurring happens when looking out of the cockpit/flight deck window, toward the ground, in the area around and under the aircraft.: the houses and buildings will appear normal, but the streets and general ground area will become a mauve/purple-ish looking "mud", with no definition at all. pj
  15. Um.. yes, Rod. MSAA. I became "somewhat heated" (again) when I read the post, as the subject has been done to death over hundreds of posts. Hmmm. Maybe.. It would seem akin to the application's (FSX) AA control, but I think in SFX's case, it would still be a post process, and still similar to the NI FXAA. Thank you, Spirit, but no - I'm not active in DX10 any more. "Life" got in the way over this last year, and testing, reading, learning, communicating, forum work - became almost a full-time job. ???????? Aaaarghh!! My friend - how could you have missed this - the most important piece of information in the DX10 How-To Guide!!! These two lines are automagically plonked into your cfg file when you set the AA in the retail Fixer setup screens. They are also DX10-specific, and - as P3D uses DX11 (DX10 on steroids) - I'm pretty sure that LM will have worked around the issue of driver-controlled AA. (I don't have P3D) Here's a shot of the page taken from some updating which I did to my old guide, earlier in the year - but bear in mind - this may be different from Adam's How-To, as it's his guide now, and I don't wish to be seen as telling him how to write it. I also didn't pursue the technical reason for the "ground shadow anomaly", other than finding what appeared to be a fix for it, but Steve may well have an explanation. I'm not sure how may users experienced this, either: whether it was a general issue, or specific to some drivers, or what. Anyway - from the Old Fart - all the Best to everyone! pj
  16. SweetFX provides FXAA - POST PROCESSING. NI will do the same. this IS NOT SMAA - which is what FSX uses. . Neither the driver, nor NI can force FSX to use SMAA. pj
  17. Yes, Wanthuyr - neither the Nvidia driver, nor NI cannot force AA on FSX when using DX10: it must be done by using Steve's DX10 Fixer, through the two extra lines in the [Display] section of the fsx.cfg, like so:- [GRAPHICS] MultiSamplesPerPixel=4 MultiSampleQuality=8 This will give you 8x CSAA, for example. To set this all up it is essential that you read the DX10 "How-To" Guide, originally published by me, but now owned by Adamski_NZ, over here - ok! Also - both RodO and DJJose are very expert at using and setting up DX10, using both patch and retail Fixer. I've pretty much retired now, and only drop in from time to time. All the Best, pj
  18. Hi Yildim: All I see which you might change, at this moment, in order to alleviate load issues, are the settings below. You can always move them up, once this blurring is fixed. I (and others!) would like to see a screenshot or two, as well. 8xCSAA in the Fixer, I normally run 4x, and recommend changing to that. Maximized=2, under [Main] instead of 1, WideViewAspect should equal "True", as 1920 x 1080 is wide-view. WATER_EFFECTS=6, under [TERRAIN], ought to be a 5. You might add SmallPartRejectRadius=4 under [scenery] CLOUD_DRAW_DISTANCE=6, under [Weather], should not be greater than 3 for most systems. You could also drop MESH_RESOLUTION=24 down to 23. When you're trying to fix an issue like this one, where it may well be a graphics load which is causing it - one should always reduce settings to the very minimum. If that fixes the issue, then you can raise the ones you like to see, a touch at a time. If everything is high, how can you possibly know which one has the bad effect? At this moment your FSX should not have blurries, and as Greg suggested - you might have hardware problems. How old is the monitor? Is it a TV or a PC monitor? Is it running at it's native resolution? Lastly - check with Nick's 4790K Overclocking guide, (link in my sig) with the aim of seeing where you might improve a bios setting. Memory has much more impact than it did on the older processors - it's also very much more configrable. too - ok? All the best, pj
  19. I think you need to follow post # 6, yildrim. I can't help you if you don't. Here's a slightly revised Inspector, as the one I posted lacked any SGSS Texture Filtering - LOD Bias(DX) All the best, pj
  20. "procspeed" is set by FSX on its first startup. It is its base perception of "how strong is this system?", and was used by the Microsoft dev team as a rough measure of that. It serves no other purpose in FSX - it doesn't get used at all, except by a few folks who use it in that manner. A number above the 14000's indicates the user has "HT OFF", while a number below that approximate number - indicates "HT is ON". A high number for HT ON would be 12000 or so: HT OFF on a hot system will show as 20000 - 22000. If erased - FSX will remake it - it will be close to the previous number most of the time. Here are examples from mine:- //ProcSpeed=20814 - taken when using the GTX 580 //ProcSpeed=21141 - taken when using the GTX 780 //ProcSpeed=20657 //ProcSpeed=11673 // HT ON //ProcSpeed=19708 // HT OFF //ProcSpeed=20266 - last one using the 2600K/780 Re-post the new config, yildrim - let's take a look - and post a pic of your Inspector settings too. pj
  21. [JOBSCHEDULER] AffinityMask=14 // Turn HT >OFF [Display] TEXTURE_BANDWIDTH_MULT=120 // 80 UPPER_FRAMERATE_LIMIT=32 // 0 WideViewAspect=True // False [Graphics] TEXTURE_MAX_LOAD=2048 // 4096 MultiSamplesPerPixel=4 MultiSampleQuality=8 // 24 8xCSAA set in the Fixer. It's more than adequate, given your issue. [TERRAIN] LOD_RADIUS=4.5 // 6.500000 [Weather] CLOUD_COVERAGE_DENSITY=7 // 8 CLOUD_DRAW_DISTANCE=4 // 6 Your killers:- [TrafficManager] AIRPORT_SCENERY_DENSITY=1 // 3 FreewayDensity=12 // 72 LeisureBoatsDensity=0 c // 77 ShipsAndFerriesDensity=0 // 74 Set Inspector to this one. OK! pj
  22. Just checking in... - gotta keep an eye on you and Rod! - yes - DSR is ideal for a 1080p monitor! All the Best, pj (Hi Rod!)
  23. Perhaps Mr Daxroth should stop quoting from old documentation as "proof" that I (and Steve Parsons - and countless others) was wrong in suggesting the Inspector cannot force AA in FSX. At the date of that publication - Inspector most definitely could NOT force AA into FSX. My Guide was given over to Adamski_NZ back in May, 2014 (approx date), and both drivers and Inspector have undergone changes since then. My current (unpublished, but nonetheless is kept up to date) has this (4th pic down, "Current Guide" (the rest are Inspector DSR, etc.. testing)) to say about that AA as it may apply at this time. This excerpt is taken from page 15 of the (my) DX10 Guide, dated Sept. 14, so it's fairly recent. As Jose suggests - you may want to slide this past Steve himeself, either here or via his blogsite. All the Best! pj (Hi Jose!)
  24. Check your pm's Vaughan. pj

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.