Rubidium wrote:

I hope you are aware that Mac OS X is not officially supported anymore and that we don't have a Mac OS X maintainer and as such the chances of this bug getting fixed in a timely matter are really small.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment7635

Chakotay wrote:

Hi Emin

Does it always happen when you try full screen? Have you tried one of the nightly builds?

At least on Mac OS X 10.6.2 I could not reproduce your error, using your save game.
It could be because of the different OS, of course.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment7647

niw3 wrote:

Hi Patrick,

I tried 1.0.0-RC2, RC3, and r19519. Still the same.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment7790

niw3 wrote:

If it helps, exactly the following happens:

When I click full screen, openttd window disappears, system mouse cursor appears, screen fades out to black, screen fades in to white with system cursor visible. Then screen makes another fade out/fade in. After that only system cursor is visible. No dock or background. Not even spaces or expose works. I have to forcefully quit the openttd executable to return to my desktop.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment7791

Chakotay wrote:

Guess someone with a 10.5 version of the OS needs to try this out.
With my Snow Leopard (10.6), it seems to work fine. Checked it again today - works for me.

Anyone else here with Mac OS 10.5 ?

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment7852

matheweis wrote:

I also am not able to reproduce this with either 1.0.1 or r19750 under 10.6.3.

If you are still able to reproduce this, please go to http://support.apple.com/kb/HT1582. When you get to the screen shown, copy and paste all the information given under the Graphics/Displays section.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment7967

TheFranz wrote:

Hi there,

I use Mac OS 10.5 and am not able to reproduce the crash either. (using the savegame)

I have however a question on the resulution you're selecting, 1920x1080: I don't have that resolution.
my max resolution is 1920x1200. 1920x1080 is not available on my machine.
any ideas how that is possible?

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment8006

matheweis wrote:

It's very possible. 1920x1080 is 1080p HDTV resolution, he probably had it hooked up to a big screen TV.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment8007

callan wrote:

I managed to reproduce this once, on the main menu before loading the game. Haven't been able to since. 1440x900, built-in MacBook Pro 15" display. Mac OS X 10.6.3. 2.66GHz Intel Core i7.

$ git rev-parse HEAD
0449d7d

$ git log -1
commit 0449d7d
Author: smatz smatz@openttd.org
Date: Tue May 18 01:10:23 2010 +0000

(svn r19850) -Codechange: move declaration of InitializeRailGUI() to rail_gu...

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment8050

urdh wrote:

Cannot reproduce this in OSX 10.6.4 using r20110.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment8295

Kiike wrote:

I cannot either reproduce this bug, trying different resolutions and switching back and forth to fullscreen mode on SVN r20500, on a MacBook Pro 3,1 with OS X 10.6.4.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment8530

niw3 wrote:

Hi,

Yes you are right. I use an external display at 1920x1080. It is a common desktop LCD. I connect it to my mbpro 17 with a DVI-VGA cable. The reason I use an external LCD is that my internal LCD's backlight isn't working. I tried to reproduce the error on mbpro's built-in display with external display disconnected, which is presumably what you folks are doing, but I couldn't. It seems that the crash only happens when using an external display and mirroring on. Anyway, I've just tested 1.0.3, and it seems to be fixing this bug. Thanks to all involved.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment8592

planetmaker wrote:

there was to my knowledge no change in the related OpenTTD code between 1.0.0-RC1 and 1.0.3...

So doing the exact same thing (using a mirror display) on the same hardware and system setup does not trigger this anymore or something else (other computer (hardware), other OS version, ...) that changed on your setup between those two versions?

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651#comment9088

planetmaker closed the ticket.

Reason for closing: Unreproducible

Not even the original author can reproduce it. Nor did I manage to reproduce it with the help of a 2nd screen.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3651