Patch 3 crash

[Yakface]

I went back to the old problematic settings. Saw no bouncing

[michaelm75au]

ORIGINAL: Nikel

bouncing happens here with ships animations when you maximize the window and disappears when you restore down, is reproducible

Correct.
It is caused by using full screen px,py when the using the '-w' switch at the same time. Remove the '-w' and it works properly

[castor troy]

ORIGINAL: michaelm

Question:
when playing window mode with wide screen, does the animations bounce up and down?

not sure what you mean by animations bouncing up and down, I haven´t seen anything strange in my animations so I guess the answer would be, no, I haven´t seen them bouncing up and down. [:)]

Have been playing in full screen now and had one crash when I tried to leave the unit menu of a CV. This is one of the things where I´ve often saw the game crashing already, usually I do a save before going into the CVs and their squadrons.

In full screen I don´t have the pause though.

[michaelm75au]

The switching to the base screen when picking from the group or TF list is related to time lag between drawing the group/TF screen and checking the mouse location for an airfield/port.
I just recently managed to repeat this and actually catch it as it was happening.
Briefly, you click on the airfield icon.
The game checks what is located at that position and opens a list of groups (if more than one).
At the same time, the position of the mouse is being checked to see what sort of hex it is over.
Now if the timing is off, the group screen is draw. Plus the game engine sees that there is no AF in hex under the mouse and issues a 'draw base' command which replaces the group screen.
The same thing can happen with TFs and ports.

I have added another test to the 'draw base' command. It wont issue that command if the top window on the map is a Group, TF screen.
Hopefully this will fix the problem.

The reason it is happening more often on the wide screen is because it does take longer to refresh the screen, and this opens the window on the timing difference between the screen draw and the mouse check.
Also, I notice that I have a tendency to pick an item off the list and then move the mouse to the left into the ocean where there is no AF symbol.[:D]
This is how I could make it happen fairly regularly. Moving the mouse back to a land base seemed to stop it from occurring SOMETIMES.

[witpqs]

ORIGINAL: michaelm

Question:
when playing window mode with wide screen, does the animations bounce up and down?

Yes. I presume it's because my graphics card or built-in chipset is slow.

[witpqs]

ORIGINAL: michaelm

ORIGINAL: Nikel

bouncing happens here with ships animations when you maximize the window and disappears when you restore down, is reproducible

Correct.
It is caused by using full screen px,py when the using the '-w' switch at the same time. Remove the '-w' and it works properly

I'm playing in windowed mode and I see that too.

[michaelm75au]

ORIGINAL: witpqs

ORIGINAL: michaelm

ORIGINAL: Nikel

bouncing happens here with ships animations when you maximize the window and disappears when you restore down, is reproducible

Correct.
It is caused by using full screen px,py when the using the '-w' switch at the same time. Remove the '-w' and it works properly

I'm playing in windowed mode and I see that too.

The problem is a conflict within how animations are shown between 'full screen' and 'window' mode, where both are using the same resolution.
There is a switch '-noFire' that can be added to the command line to stop the animation so you don't get sea-sick watching the bouncing screen.

I haven't had time to come up with a permanent fix, but I expect one will show up in the future.

[witpqs]

ORIGINAL: michaelm

The problem is a conflict within how animations are shown between 'full screen' and 'window' mode, where both are using the same resolution.
There is a switch '-noFire' that can be added to the command line to stop the animation so you don't get sea-sick watching the bouncing screen.

I haven't had time to come up with a permanent fix, but I expect one will show up in the future.

That's good enough for me, I don't care about animations.

BTW, I forgot to mention that I also get crashes while giving orders since Patch 3 Official. Despite around a dozen or more, I can't pin down any specific actions or sequence of actions. I have the feeling that its graphics related for the following reason. As I enter orders, there are times when I click on something and it doesn't register. It looks as if the click is instead consumed by bringing focus back to AE. Although, the window banner at the top of AE had not grayed out as is the case when you fully switch focus to another application.

I should mention that I have all sounds down to 0 and I have the sound folder renamed to "nosound".

As far as crashes during the replay, none in recently weeks. Back in January I had a couple or three but they were clearly related to pressing escape (maybe more than once) during surface battles that had lots of action. Being careful about doing so now, I never have crashes during animations.

[Nomad]

ORIGINAL: witpqs

ORIGINAL: michaelm

The problem is a conflict within how animations are shown between 'full screen' and 'window' mode, where both are using the same resolution.
There is a switch '-noFire' that can be added to the command line to stop the animation so you don't get sea-sick watching the bouncing screen.

I haven't had time to come up with a permanent fix, but I expect one will show up in the future.

That's good enough for me, I don't care about animations.

BTW, I forgot to mention that I also get crashes while giving orders since Patch 3 Official. Despite around a dozen or more, I can't pin down any specific actions or sequence of actions. I have the feeling that its graphics related for the following reason. As I enter orders, there are times when I click on something and it doesn't register. It looks as if the click is instead consumed by bringing focus back to AE. Although, the window banner at the top of AE had not grayed out as is the case when you fully switch focus to another application.

I should mention that I have all sounds down to 0 and I have the sound folder renamed to "nosound".

As far as crashes during the replay, none in recently weeks. Back in January I had a couple or three but they were clearly related to pressing escape (maybe more than once) during surface battles that had lots of action. Being careful about doing so now, I never have crashes during animations.

I have the locup/crash problem during order input too, but it seems to be only in windowed mode. I do have sounds on but music is at 0. I have given up using windowed mode and only use full screen now and I haven't seen a lock up yet. Like witpqs says, I would click on a button and I would not get the sound of the click nor would anything happen. The WitP window would then go white and I would get the Windows error screen. I have never had a crash during turn execution.

[michaelm75au]

I have noticed some funny things during debugging when music is 0, but I thought that was just with debugging as no one else was having any issues.
I now always run with music set to '1' and I don't experience my problems anymore.

Maybe you might want to try that.

[Nomad]

I'll try it and see what happens. It always seems to be a long time into doing orders, 20-30 minutes. I need to look around a lot in one game and I will see if it happens. These non-repeatable problems are hard to figure out.

[witpqs]

ORIGINAL: michaelm

I have noticed some funny things during debugging when music is 0, but I thought that was just with debugging as no one else was having any issues.
I now always run with music set to '1' and I don't experience my problems anymore.

Maybe you might want to try that.

Thanks, I will. BTW, in case I was unclear I am using windowed mode.

[Nomad]

That didn't cure it. I had the game open in windowed mode, I brought up the TF list in the East Coast USA incoming hex. I was looking at one and clicked on the next one at the bottom of the window and I got the dreaded hourglass for about 15 seconds, then the window went white and the Windows error message box showed up. That was with music set to 1 instead of 0. So to me there was no change.

[Runyon]

My game crashed on me this evening for the first time ever. Very annoying after two hours of inputting orders and getting ready to end the turn. I have never played in windows mode, and have had the music turned down to zero. I am running patch 3. I'm using -cpu4 -multiaudio -fw, the same as I always have.

[michaelm75au]

I find occasionally making a save is useful when dealing with any Window application. Just in case.

I follow this principal at work and in my gaming experience.

[Runyon]

Yes, I normally always save. Of course, it's when I don't that something like this happens.

I posted this to confirm that something is causing a crash that I never saw before. It occurs when using the interface during the orders phase, like the OP said. At the time of the crash I was clicking through the 'air groups to withdraw' menu, if that helps.

[Nomad]

michaelm, the one thing I did notice is that I do not get the click sound when it locks up. I click on the icon and there is no sound and an hourglass shows up. Maybe that will help you.

[michaelm75au]

Common thread seems to be the mouse click/action.
Most likely if you just let  the game run it wouldn't lock up by itself. [;)]

I think the consensus is that this happens in wide-screen, window-mode?

[Nomad]

So far for me, I don't remember it happening in wide screen, full screen mode. It has happened in wide screen, windowed mode.

[witpqs]

ORIGINAL: michaelm

I think the consensus is that this happens in wide-screen, window-mode?

Yes, the crashes started after I began playing in wide-screen windowed mode.

Although since sorting out command line switches to suit my screen, I've only been playing that way. So, I'm unable to say that it wouldn't be crashing for me in wide-screen full-screen.