Hi,

Does anyone have that same sight texture? I have my sight distance set to maximum but I don't know if there's more to it. As you see this square surrounding above water or land, in my case here it's water. If you also fly high altitude you will notice it. I'm wondering is there a fix for it? Or disable such thing, anything...

Here's a picture...

https://www.mediafire.com/view/jzkabjb6c3gqdzs/untitled.jpg/file

I have seen similar symptoms ... I've found that changing aircraft can cause the problem to disappear, but what causes it initially, I don't know.

How do you mean by changing aircraft? Any aircraft I load happens like that.

That's why I'm wondering if all FS2004 users have that same view and if it is a default thing within the sim. Not sure if FSX has it too.

Do you see this blurry square following your aircraft where ever you fly?

2 hours ago, AC799 said:

How do you mean by changing aircraft? Any aircraft I load happens like that.

That's why I'm wondering if all FS2004 users have that same view and if it is a default thing within the sim. Not sure if FSX has it too.

Well, when I load your map references from the image my default FS9 looks "normal", so there's "something" at your end causing the symptom.

FS9 test.jpg

Yes it's blurry wherever I go it follows, I'm flying above water so it can be easily viewed. It's like is that the maximum sight distance in the sim or range of view?

Because I have this on 3 different machines. I've tested it before any addons or anything, just sim installation then a quick flight and it's there.

No matter what I change in settings it's always there that's why I'm wondering if all FS2004 users have that as well.

Here's more pictures at high altitude this time... By the way I don't think it has to do with hardware specs, I have more than enough power to handle FS9.

https://www.mediafire.com/view/t7ne0tl0pas0dtw/fs1.jpg/file

https://www.mediafire.com/view/uuzu7qpzsel7fmn/fs2.jpg/file

https://www.mediafire.com/view/lgbusrgerxdp8py/fs3.jpg/file

https://www.mediafire.com/view/kmkbhp5h1vtyufo/fs4.jpg/file

https://www.mediafire.com/view/o0r6f92b1adtbhr/fs5.jpg/file

Edited April 11Apr 11 by AC799

Well, you've obviously got a problem!

I've got two installations of FS9 on my "main" computer and three other installations on different computers and don't see this problem on any of them.

FWIW ... I don't see the problem in FSX either.

I even tried loading the default "Global" 747 that you're using, but still no problem ... maybe it's a choice of screen resolution?

Well then I’m out of ideas what’s causing this. I don’t know about resolution because whatever one I set I still get it. I’ve always had that square even before other operating systems like windows xp times. This is very confusing, I don’t know what or where to look for answers as it just stood up on instant default installation.

Please let me pitch in my theory.

When any flight is initiated anywhere in the world, only those sceneries in the direct surroundings become active and visible, simply because there's no technical point in opening any sceneries/objects outside such surroundings.

This is also true while you are flying at any altitude inside of a (so to speak) moving "circular glass cage", where in front of you, new sceneries become actived/visible, while those behind you become de-activated. I believe the standard diameter of this "glass cage" is around 40 nautical miles. It moves along with you as you fly in it's center and it also activates/de-activates AI activities.

In your case however, the texture(s) at the bottom of your "glass cage" seem to display incorrectly and it just COULD be a question of some default texture not having an alfa channel.

Maybe and hopefully this theory will cause some technical experts out there to be able to point more precisely to a solution to your problem.

Good luck.

Hans

P.S. I do not see your problem in my FS9 either.

If you and chris_eve don't have this in your sims then you must have changed something somewhere in directory settings or in game menus to disable it or something because for sure this is somehow someway set as visible/enabled, something, as I have had this with default installation on various systems like I've previously said. I also don't have a lot of addons but again this happens before any addons. If you make another installation and leave everything by default original and load a flight, will it still not show?

If it's really something regarding alpha channel therefore all default textures need to be revised? We can't be sure obviously.

Also the way you described it makes a lot of sense but doesn't make sense that you guys don't have this while I do. I'm really curious how many FS9 users have this in theirs as there are not much FS9 users left. This is a mystery lol, I've had this square ever since day 1 but never looked much into it till now. Here's another image with traced edges.

https://www.mediafire.com/view/65b7jkeqr83bl88/fs.jpg/file

By the way, if this "glass cage active area" can be edited to a range bigger than 40 nautical miles then that could help.

 

Edited April 15Apr 15 by AC799

I keep a default installation with no add-ons or modifications (except for the usual update to FS9.1 and the no-CD hack) purely for checking anomalies ... this is what I used to generate my above screen-cap.

Admittedly, FS9 does use a common FS9.CFG, so any in-game fine tuning from my main installation will be reflected in my default installation ... not a lot I can do about that I'm afraid, but, as I wrote, I see no problem on two other machines, and I don't remember copying my FS9.CFG from one machine to another.

I keep this text document for my own reference ... make of it what you will :- 

I've not got any complete reference per se, but a couple of settings I've picked up over the years that I find useful are :-

 

;#######################################

 

TERRAIN_MAX_VERTEX_LEVEL=21 ; for best detail - default = 19

[MAIN]
Display_Fractional_Minutes=0 ;set to 1 otherwise

[SCENERY]
ShowTriggers=1 ; for fuel or weather triggers to be displayed

 

;########################################

 

also :-

 

;########################################

;

The "Ten Test Tweaks" (for FS9.Cfg only !):

 [GRAPHICS]
 DETAIL_TEXTURE=2 // 1 <-- Tweak #1
 TEXTURE_MAX_LOAD=262144 // 256 <-- Tweak #2 (use calculated larger value discussed in AVSIM thread if you have more VRAM)

 [DISPLAY]
 TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3
 WideViewAspect=True // False <-- Tweak #4 (investigational only)

[TERRAIN]
 TERRAIN_ERROR_FACTOR=100.000000
 TERRAIN_MIN_DEM_AREA=100.000000 // 10.000000 <-- Tweak #5
 TERRAIN_MAX_DEM_AREA=400.000000 // 100.000000 <-- Tweak #6
 TERRAIN_MAX_VERTEX_LEVEL=21 // 18 <-- Tweak #7
 TERRAIN_TEXTURE_SIZE_EXP=8
 TERRAIN_AUTOGEN_DENSITY=5 // <-- (set to "5" if already set to any other number)
 TERRAIN_USE_GRADIENT_MAP=1 // 0 <-- Tweak #8
 TERRAIN_EXTENDED_TEXTURES=1 // 0 <-- Tweak #9
 TERRAIN_DEFAULT_RADIUS=9.500000 // 0.000000
 TERRAIN_EXTENDED_RADIUS=4.500000 // 0.000000
 TERRAIN_EXTENDED_LEVELS=1307992 // 3 <-- Tweak #10

=====================================================================

The "Twelve 'Extreme' Test Tweaks" (for FS9.Cfg only !):

 [GRAPHICS]
 DETAIL_TEXTURE=2 // 1 <-- Tweak #1
 TEXTURE_MAX_LOAD=1228800 // 256 <-- Tweak #2 (...calculated from your '1.25 GB VRAM' capacity in MB you stated above)

 [DISPLAY]
 TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3
 WideViewAspect=True // False <-- Tweak #4 (investigational only)

[TERRAIN]
 TERRAIN_ERROR_FACTOR=100.000000
 TERRAIN_MIN_DEM_AREA=150.000000 // 10.000000 <-- Tweak #5
 TERRAIN_MAX_DEM_AREA=1500.000000 // 100.000000 <-- Tweak #6
 TERRAIN_MAX_VERTEX_LEVEL=21 // 18 <-- Tweak #7
 TERRAIN_TEXTURE_SIZE_EXP=8
 TERRAIN_AUTOGEN_DENSITY=5 // <-- (set to "5" if already set to any other number)
 TERRAIN_USE_GRADIENT_MAP=1 // 0 <-- Tweak #8
 TERRAIN_EXTENDED_TEXTURES=1 // 0 <-- Tweak #9
 TERRAIN_DEFAULT_RADIUS=40.000000 // 9.500000<-- Tweak #10
 TERRAIN_EXTENDED_RADIUS=60.000000 // 4.500000<-- Tweak #11
 TERRAIN_EXTENDED_LEVELS=1307992 // 3 <-- Tweak #12

==========================================================================

Be sure to re-set the "Test Tweaks" to the numbers specified in the suggestions above every time before re-starting FS9. 😉

 The reason for doing this is that when FS9 exits any session, it writes its 'own' internal "default" parameter numbers back into the active FS9.Cfg file each time; so one would otherwise lose certain Test Tweaks without restoring them each time.

 As described in the AVSIM thread linked in my post above, to prevent this from happening:

 1.) One must "lock" the FS9.Cfg file in some way

 2.) Use a batch file to swap out backup copies of the FS9.Cfg file which have the Test Tweaks

 3.) Or simply open the active FS9.Cfg file which has the Test Tweaks in it ... in NotePad before starting FS9 and leave that NotePad session open until one's FS9 session is completely exited back to the Desktop.

The "Ten Test Tweaks" (for FS9.Cfg only !):

 [GRAPHICS]
 DETAIL_TEXTURE=2 // 1 <-- Tweak #1
 TEXTURE_MAX_LOAD=262144 // 256 <-- Tweak #2 (use calculated larger value discussed in AVSIM thread if you have more VRAM)

 [DISPLAY]
 TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3
 WideViewAspect=True // False <-- Tweak #4 (investigational only)

[TERRAIN]
 TERRAIN_ERROR_FACTOR=100.000000
 TERRAIN_MIN_DEM_AREA=100.000000 // 10.000000 <-- Tweak #5
 TERRAIN_MAX_DEM_AREA=400.000000 // 100.000000 <-- Tweak #6
 TERRAIN_MAX_VERTEX_LEVEL=21 // 18 <-- Tweak #7
 TERRAIN_TEXTURE_SIZE_EXP=8
 TERRAIN_AUTOGEN_DENSITY=5 // <-- (set to "5" if already set to any other number)
 TERRAIN_USE_GRADIENT_MAP=1 // 0 <-- Tweak #8
 TERRAIN_EXTENDED_TEXTURES=1 // 0 <-- Tweak #9
 TERRAIN_DEFAULT_RADIUS=9.500000 // 0.000000
 TERRAIN_EXTENDED_RADIUS=4.500000 // 0.000000
 TERRAIN_EXTENDED_LEVELS=1307992 // 3 <-- Tweak #10

=====================================================================

The "Twelve 'Extreme' Test Tweaks" (for FS9.Cfg only !):

 [GRAPHICS]
 DETAIL_TEXTURE=2 // 1 <-- Tweak #1
 TEXTURE_MAX_LOAD=1228800 // 256 <-- Tweak #2 (...calculated from your '1.25 GB VRAM' capacity in MB you stated above)

 [DISPLAY]
 TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3
 WideViewAspect=True // False <-- Tweak #4 (investigational only)

[TERRAIN]
 TERRAIN_ERROR_FACTOR=100.000000
 TERRAIN_MIN_DEM_AREA=150.000000 // 10.000000 <-- Tweak #5
 TERRAIN_MAX_DEM_AREA=1500.000000 // 100.000000 <-- Tweak #6
 TERRAIN_MAX_VERTEX_LEVEL=21 // 18 <-- Tweak #7
 TERRAIN_TEXTURE_SIZE_EXP=8
 TERRAIN_AUTOGEN_DENSITY=5 // <-- (set to "5" if already set to any other number)
 TERRAIN_USE_GRADIENT_MAP=1 // 0 <-- Tweak #8
 TERRAIN_EXTENDED_TEXTURES=1 // 0 <-- Tweak #9
 TERRAIN_DEFAULT_RADIUS=40.000000 // 9.500000<-- Tweak #10
 TERRAIN_EXTENDED_RADIUS=60.000000 // 4.500000<-- Tweak #11
 TERRAIN_EXTENDED_LEVELS=1307992 // 3 <-- Tweak #12

==========================================================================

Be sure to re-set the "Test Tweaks" to the numbers specified in the suggestions above every time before re-starting FS9. 😉

 The reason for doing this is that when FS9 exits any session, it writes its 'own' internal "default" parameter numbers back into the active FS9.Cfg file each time; so one would otherwise lose certain Test Tweaks without restoring them each time.

 As described in the AVSIM thread linked in my post above, to prevent this from happening:

 1.) One must "lock" the FS9.Cfg file in some way

 2.) Use a batch file to swap out backup copies of the FS9.Cfg file which have the Test Tweaks

 3.) Or simply open the active FS9.Cfg file which has the Test Tweaks in it ... in NotePad before starting FS9 and leave that NotePad session open until one's FS9 session is completely exited back to the Desktop.

 

;########################################

 

Most of the above was found in a forum post ... unfortunately I didn't make a note of the url or the original author.

All of these are in fs9.cfg? Where is it located because I don't have anything in directory or in documents.

5 hours ago, AC799 said:

All of these are in fs9.cfg? Where is it located because I don't have anything in directory or in documents.

C:\Users\*YOUR_USER_NAME*\AppData\Roaming\Microsoft\FS9 is where mine is stores ... change *YOUR_USER_NAME* apropriately.

At least one of the folders in the tree may be hidden and/or system, so you may need to use attrib from the command prompt to un-hide it, else go directly to the address by entering it in the address line of Explorer.

AC799

If you open an on land flight or scenery anywhere in the world and you press your "Y" key, followed by selecting "top-down view" and then pressing the "-" (minus) key more than a few times, you will sooner or later always get to see your default "weird square" (= a fat cross). However, the first altitude at which you see this square/cross, should under normal circumstances be extremely high and above any normal flying altitudes.

Therefore, when I say that I do not see your problem in my FS9, I mean that I never (try to) fly at such altitudes myself and also that I do not purposely seek any of the possible FS9 scenery or hardware limits.

At what altitude does your weird square firstly become visible and is that altitude the same anywhere in your FS9 world ?

Hans