In Loving Memory Of
Founder of AVSIM Online
Hot Spots:Latest News & Homepage
File Library - What's New
Latest Product Reviews
NEW Prepar3D Guide v1
FS9/FSX/P3D CTD Guide v3
FSX / P3D Config Guide
Bargain Hunters Forum
Classified, Want, Swap Ads
News (1999 to 2012)
Product Reviews (2006-2012)
Advertise on AVSIM!
Sim Site Rankings
The AVSIM Staff
AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!
34 replies to this topic
Posted 26 September 2009 - 05:52 AM
Hello,Many of you will know me as the developer of the Texture Max Load Editor (TMLE) and that I am currently working on a LOD Radius Editor for FSX. This has been requested by many people and I have completed the main application.My main question is this: If you change your LOD Radius in your fsx.cfg file, what do you change it to?Basically, I want to know which value to set as the maximum allowed or if it would be a good idea to let people enter a custom value in a textbox so they can have any value they want. I know that many people set it to 8 or even 12 but does anyone have any higher values that they use?At the moment, the application has a slider with a minimum of one and a maximum of twelve. The user can drag the slider to set any value between 1 and 12.I would like to hear your ideas on this one :)Thanks,Steve
Posted 26 September 2009 - 09:17 AM
I normally use 5.5, 6.0 or 6.5.I know a few people with high end systems using 8.5 but not anything beyond.I didn't realise that anything over 8.5 worked anyway.Higher values reallly cane the system and result in long load times.IAN
Posted 26 September 2009 - 09:46 AM
I use LOD 8.0Never tried anything higher. 8.0 pretty much gives me all the distance I need for clear eye candy.This would be awesome. I hate having to go into the fsx.cfg file everytime I change something.
That's for sure!That's where 6 Gb of really fast memory comes in. My Total Commit Charge reached 3.9 Gb the other day with 8.0, that's 1Gb more than without it!-jk
Higher values reallly cane the system and result in long load times.IAN
Posted 26 September 2009 - 10:34 AM
I run default (I think 4.5) because my system can't handle much moreI'd love to run 6.5 though
| i5 2500K@4GHz | 8GB RAM | EVGA GTX 970 | GB P67A-UD4-B3 | 500GB Samsung 840 Evo | 120GB Mushkin | 1TB Samsung Spinpoint | Seasonic X750W |
-Beta with Milviz and Realair-
Posted 26 September 2009 - 12:38 PM
I use 6.5 which is recommended for CHProXbut maybe 5.5 and 7.5 would be nice too.Harry
Win10 - firstname.lastname@example.org - 16G RAM - SSDs - GTX1070 - 3440x1440 curved - SaitekX52 || P3D v3.3.5: AS16+ASCA, MyTrafficX, PMDG birds, Majestic DH8D, A2A C172, FSGlobal(U), UTXv2, ORBX Gobal + Landclass + Regions + Airports, P3D3v3 compatible Airports from FlyTampa, FSBeam, FSDT, T2G and Aerosoft.
Posted 26 September 2009 - 01:06 PM
I use 6.5: to me that's perfect with VFR GenX (no obvious low res textures in sight). I did use 7.5 for a while but it was too much (loading times and strain on system).And er... if I may share some thoughts... ;P I think it would be nice if you would just have to run the app you are making and that the setting you used previously is applied automatically. Some sort of memory option. So for instance, when I normally use 6.5, it would be nice that, after changing some settings which reset the radius in the cfg, I can run your app and it automatically changes the radius to 6.5 (instead of simply reading the default from the cfg) and after that I can start FSX. Only if you want another setting, then you would use the slider. It would be a pity if you have to set the slider manually everytime. Just a thought. ;) And I don't know if you are thinking about a button that launches FSX from within your app: if so, it might be a nice idea (just thinking along here ) to make that button editable, meaning the user can redirect it to anything he wants (for instance to the Limiter which I use to sart FSX with: other people may have other programs they may wish to start first). Just some thoughts. ;) It seems more logical to think along BEFORE the app is actually finished.
Posted 26 September 2009 - 05:28 PM
Thanks for the information guys :).@J van E, Thanks for your ideas, I might use some of them :).@witlzei, I have a major tweak utility planned so that will be on the list of tweaks to be tweaked in that application :)
Posted 26 September 2009 - 11:11 PM
I use 8.0 for photoscenery.
Posted 27 September 2009 - 02:29 AM
LOD = Level Of Detail. Put your aircraft in the very center of a large imaginary cylinder. The radius is measured from your aircraft to the edge of the cylinder. Any scenery within this radius gets full graphical detail. Anything outside, well, doesn't. What I think would be cool would be a dynamically variable LOD radius. Instead of a cylinder, say a cone or a sphere. That way, the radius would change in relation to altitude. You generally don't need a huge radius on the ground or at high altitude. Those would be great places to save on frame rates. It's an idea that had been thrown around for a possible FS-Next, but I don't know if it's possible for FSX. Jeff ShylukSenior Staff ReviewerAVSIM
Posted 27 September 2009 - 06:11 AM
What I would like to see is the plane NOT being in the very center of the circle, but a bit more to the back. Usually you look forward or to the sides: I hardly look (completely) to the back. (But I always fly in the VC and never outside of the plane.) This would mean you can see more crispy textures in front of you without any loss in fps or loading times.
LOD = Level Of Detail. Put your aircraft in the very center of a large imaginary cylinder. The radius is measured from your aircraft to the edge of the cylinder. Any scenery within this radius gets full graphical detail. Anything outside, well, doesn't. What I think would be cool would be a dynamically variable LOD radius. Instead of a cylinder, say a cone or a sphere. That way, the radius would change in relation to altitude. You generally don't need a huge radius on the ground or at high altitude. Those would be great places to save on frame rates. It's an idea that had been thrown around for a possible FS-Next, but I don't know if it's possible for FSX.