zooming out

[Idanwin]

How can you see the whole map?
If I zoom out everything beyond a certain distance becomes black.
Why is this and how can it be solved?

[mictes]

which tileset do you use ?
You have to disable Fog in the Tileset and Fog-of-War in the glestadv.ini

[Idanwin]

Fog of war disabled.

Every things at a certain distance disapears into a black hole...

[mictes]

UFF. Ah that was what you pointing off...
Yes of course, that is the "Sky".

You have to navigate with your mouse.
In this example: go down with your mouse / scroll down !

[Idanwin]

I don't really understand, if I scroll that's what I get (scroll=zoom?).

[mictes]

No, it's just named "scrolling" - look at this site, you just scrolled down to read this text.
As I described: Move your mouse to the bottom of your screen. Your position on the "map" will change.
Then you can see more of the map.

[Idanwin]

um, I have to see the whole map, not just a part...

Or do you think I'm at the top of the screen? Well, I'm not.

[mictes]

I had just again a look onto the screenshot you posted.
You didn't have enabled Photomode in your glestadv.ini !

[Idanwin]

Ah, now it works, but it goes terribly sloooooow!
How can you make the quality lower/what things can be changed to make it render faster.
Disabling Shadows does a lot but it still is a pain to get to full map...

[daniel.santos]

Neither Glest nor GAE implements level of detail attenuation (see http://bugs.codemonger.org/show_bug.cgi?id=20), thus there is currently no way to improve performance when viewing large areas.  Also, I haven't actually tried to view an entire map, so I'm not certain if there may be other things that cause some tiles to not be rendered, but possibly disabling the fog would do it as previously suggested.

[modman]

When I do it, there's this zigzag pattern along the edges of my viewable area, then there's just black outside that.  The zigzags are at 90 degrees from each other so it looks kind of like a step pyramid.  Apparently I cannot link an image from Mediafire, so the image download is here, for those who wish to help.

The ini file looks like this:

Code: [Select]

; === propertyMap File ===

AiLog=0
AiRedir=0
CameraMaxDistance=1000
CheckGlCaps=1
ColorBits=32
ConsoleMaxLines=10
ConsoleTimeout=20
DayTime=1000.00
DebugMode=0
DepthBits=32
FactoryGraphics=OpenGL
FactorySound=DirectSound8
FastestSpeed=2.00
Filter=Bilinear
FilterMaxAnisotropy=1
FirstTime=0
FocusArrows=1
FogOfWar=0
FogOfWarSmoothing=1
FogOfWarSmoothingFrameSkip=3
FontConsole=Verdana
FontDisplay=Verdana
FontMenu=Verdana
Lang=english.lng
MaxLights=1
NetworkConsistencyChecks=1
PhotoMode=1
Platform=Windows
RandStartLocs=1
RefreshFrequency=75
ScreenHeight=768
ScreenWidth=1024
ServerIp=192.168.1.100
ServerPort=6666
ShadowAlpha=0.20
ShadowFrameSkip=2
ShadowTextureSize=512
Shadows=Projected
SlowestSpeed=0.25
SoundStaticBuffers=16
SoundStreamingBuffers=4
SoundVolumeAmbient=80
SoundVolumeFx=80
SoundVolumeMusic=90
StencilBits=0
Textures3D=1
Windowed=0

[daniel.santos]

yea, that's just the way it behaves when attempting to view very far distances, the engine was never designed to view large landscapes.  Not that it can't be modified, but it hasn't been done yet.

[mictes]

I think that wasn't the goal of Idawin.
I thought he wants to make a photo of his new map.

There won't be big performance-problems if he zoom out when the game is paused ("p").

[modman]

But you see there is no "Max distance" variable, and I promise the engine works fine.  And in this image: you can see they got their entire map.  Why can't I?

[daniel.santos]

But you see there is no "Max distance" variable, and I promise the engine works fine.

from source/glest_game/graphics/renderer.cpp:

Code: [Select]

//perspective values
const float Renderer::perspFov= 60.f;
const float Renderer::perspNearPlane= 1.f;
const float Renderer::perspFarPlane= 50.f;
.
.
.
clipping= photoMode ? perspFarPlane*100 : perspFarPlane;
 
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
gluPerspective(perspFov, metrics.getAspectRatio(), perspNearPlane, clipping);
So yes, there is a variable, it is not exposed.  Apparently, if you go into "photo mode", it is multiplied by 100, just like mictes told you already.

[@kukac@]

Modman, I'm still quite sure that you are still trying edit the original Glest files. Try glestadv.ini and glestadv-sse2.exe or glestadv-i686.exe!

[modman]

I think I have the wrong engine.  Is 1.03 too "primitive"?  

[daniel.santos]

*chokes and dies*

[modman]

I think I was using an old engine, so I think it's problem solved.

[mictes]

ok ^^

Idawin wrote:
Ah, now it works, but it goes terribly sloooooow!
How can you make the quality lower/what things can be changed to make it render faster.
Disabling Shadows does a lot but it still is a pain to get to full map...

Hi again. Cause it could be that my message have lost between all the other posts ^^, again:
You have to zoom out and take the photo when the game is paused, that will solve mostly the performance problem, too.

[daniel.santos]

yea, I didn't even know photomode did that until I saw it in the code (I never experimented with it much).