I just tried viewports for the first time and I noticed that the dotmap feature (Ctrl-X to show, Alt-X to modify) wasn't working. Is this a known issue?
While were at it is it known that after playing a while on Viewports you will have a bunch of flashing dots on the minimap, which were from previous happenings but haven't gone away? It isn't a big deal, but it is kinda annoying.
Yes, that's known but not understood. I've tried to eliminate it but not got anywhere at least so far.
There are no rings showing that mark rallypoints, what tiles are worked in the city screen or other stuff with viewports on.
Also I was trying bigger ports for convenience since my machine can handle it and viewports over 100x100 don't seem to work properly. For example 120x120 or 150x150 port won't move and graphics get weird. This was on perfectmongoose size gigantic which seems to be around 120 in Y direction so maybe the port was too big in Y direction which causes problems?
V25. I guess I'm not really up to date with the viewports because I had no need to activate them until yesterday.I thought the lack of rings etc was fixed a few weeks ago. Are you talking about the SVN version or about v25?
V25. I guess I'm not really up to date with the viewports because I had no need to activate them until yesterday.
Fun fact: if you go into the Mil Advisor in windowed mode with Viewports you will get a MAF on exiting.
Reposting this here because this is making debugging a major pain for me atm.
I always run windowed, and this has never happened to me, so the must be more to it than that.
if ((iX == INVALID_PLOT_COORD) || (iY == INVALID_PLOT_COORD))
{
return NULL;
}
I'll see if I can narrow down the circumstances more. It happens almost every time for me, so I don't know what I'm doing differently.
Edit:
OK, more details on what is happening. First, it only happens with JosEPh's save here, and what happens is this. The function plotINLINE() has a routine
PHP:if ((iX == INVALID_PLOT_COORD) || (iY == INVALID_PLOT_COORD)) { return NULL; }
around line 258 or so, whose function I don't quite understand. When I left the Mil Advisor, it got into an infinite loop here, adding a little memory each time. Eventually, this leads to the MAF. It is repeatable for me from that save.
When you say 'loop' do you know what code is looping, Or do you just mean it iterates infinitely without knowing about any specific loop per se? Do you know what is allocate memory each time?
The NULL return clause toy quoted above is saying 'you asked me what plot is at some invalid coordinates, s I'm telling you that none is'. Do you know what makes the call with the invalid coordinates? Does it matter how you exit the advisor? (escape, press exit, click on map)
It happens whether or not I click on the minimap or hit the exit button. I don't know if it actually is a loop or if that clause just iterates infinitely, but either way, it adds a bit of memory each time, which means that eventually it MAFs. The call stack is attached as a pic, occasionally it will call for the m_bWrapX and m_bWrapY, other times it doesn't.
+1 to this! My major reluctance to USE viewports much is the idea of having to go into the military adviser to change the center of the focus.Proposition:
It would be awesome if you could center the viewport by clicking on a tile with the mouse wheel button.
Make this +2. Due to hardware restrictions I got no choice but to use viewports on the larger maps ( and Iam very thankfull for them.)+1 to this! My major reluctance to USE viewports much is the idea of having to go into the military adviser to change the center of the focus.