OpenTTD OSX (Mac Port)
Moderator: OpenTTD Developers
OpenTTD OSX (Mac Port)
Now, before anyone says "there's already too many different mac ports of openttd!" or "someone's done this before" or something else, I will apologise in advance if this has been done already. As for this port, it comes pre-loaded with OpenGFX, OpenSFX and OpenMSX, so there is no need to download them. I have done this because so many other ports do not include the graphics and it is a pain to get them working. I have also made it easier to install and run OpenTTD as well.
By now you're probably thinking "What? I want to use my TTD graphics!". Well, for now, the only way to do that is to mess around with the /data directory. I am making sure that future releases will include an option to install the TTD graphics, if you have them. So far, everything seems to work fine without a problem but if there are any bugs with the port (Not the game. If it is a game bug, report it to the OpenTTD team), report them to me in this thread, on the SorceForge page or email me (bkbusters@hotmail.com).
SourceForge page
My blog (News, Updates, etc.)
------
Download (Build v1.0.0 Installer)
(May give source files download if needed)
By now you're probably thinking "What? I want to use my TTD graphics!". Well, for now, the only way to do that is to mess around with the /data directory. I am making sure that future releases will include an option to install the TTD graphics, if you have them. So far, everything seems to work fine without a problem but if there are any bugs with the port (Not the game. If it is a game bug, report it to the OpenTTD team), report them to me in this thread, on the SorceForge page or email me (bkbusters@hotmail.com).
SourceForge page
My blog (News, Updates, etc.)
------
Download (Build v1.0.0 Installer)
(May give source files download if needed)
Last edited by bkbusters on 04 Aug 2010 09:57, edited 2 times in total.
Re: OpenTTD OSX (Mac Port)
You are aware that some OpenMSX MIDIs are known to cause Mac OS X's MIDI playback to fail, and by failing I mean crash in such an extent that it crashes OpenTTD as well?
Also you're "releasing" an outdated an known vulnerable version of OpenTTD, and yes... releasing the sources (at sourceforge!) would be greatly appreciated.
Also you're "releasing" an outdated an known vulnerable version of OpenTTD, and yes... releasing the sources (at sourceforge!) would be greatly appreciated.
Luckily for us Mac OS X is not supported, so they'll just end up on the bugs-that-we-cannot-solve-because-there-is-no-Mac-OS-X-maintainer pile. But yes, please report any Mac OS X issues! The next maintainer will appreciate lots of very detailed bug reports.bkbusters wrote:If it is a game port, report it to the OpenTTD team
Re: OpenTTD OSX (Mac Port)
1. I am aware of that problem but so far I haven't had any problems when I have tested it. It would be greatly appreciated if some people could test it to see if it does in fact work on other Macs.Rubidium wrote:You are aware that some OpenMSX MIDIs are known to cause Mac OS X's MIDI playback to fail, and by failing I mean crash in such an extent that it crashes OpenTTD as well?
Also you're "releasing" an outdated an known vulnerable version of OpenTTD, and yes... releasing the sources (at sourceforge!) would be greatly appreciated.
Luckily for us Mac OS X is not supported, so they'll just end up on the bugs-that-we-cannot-solve-because-there-is-no-Mac-OS-X-maintainer pile. But yes, please report any Mac OS X issues! The next maintainer will appreciate lots of very detailed bug reports.bkbusters wrote:If it is a game port, report it to the OpenTTD team
2. I will upload the source files later today. As for the 'outdated and known vulnerable version', I got that using my SVN client so i have really no idea how to explain that one. I will probably release newer versions of this port based on the stable versions.
3. Typing error on that post, I meant to say "If it is a game bug, report it to the OpenTTD team". I have no idea why I typed 'port', but the point I was trying to make was that any in-game bugs would usually be problems the original source code, not the port.
Re: OpenTTD OSX (Mac Port)
I can also still get the source code for 0.7.3 with my svn client, that doesn't tell anything. What version is this exactly? Is this really 1.0.0 or just the latest trunk version at the time you got the source?bkbusters wrote:2. As for the 'outdated and known vulnerable version', I got that using my SVN client so i have really no idea how to explain that one.
Re: OpenTTD OSX (Mac Port)
it was the latest version of the trunk code when I got it, version r20277Yexo wrote:I can also still get the source code for 0.7.3 with my svn client, that doesn't tell anything. What version is this exactly? Is this really 1.0.0 or just the latest trunk version at the time you got the source?bkbusters wrote:2. As for the 'outdated and known vulnerable version', I got that using my SVN client so i have really no idea how to explain that one.
also, when I say this is version 1.0.0, I mean the build of the port, not the code. sorry for the misunderstanding.
Re: OpenTTD OSX (Mac Port)
You are definitely not helping Mac OS X users with that; they expect 1.0.0 to join 1.0.0 servers, but they can't join them because it isn't OpenTTD 1.0.0.bkbusters wrote:it was the latest version of the trunk code when I got it, version r20277
also, when I say this is version 1.0.0, I mean the build of the port, not the code. sorry for the misunderstanding.
Re: OpenTTD OSX (Mac Port)
Also, when you move back to using 1.0.3 instead of r20277, then savegames that your users has made will no longer load in your port. This is because r20277 has several new features that are not present in the last stable (1.0.3).
I suggest that you either stick with last stable (1.0.3) or do regularly trunk builds. Either way, be very clear what OpenTTD version you have used and label it properly so that they can join servers of that OpenTTD version. (given that you have not added any game play-changing patches)
I suggest that you either stick with last stable (1.0.3) or do regularly trunk builds. Either way, be very clear what OpenTTD version you have used and label it properly so that they can join servers of that OpenTTD version. (given that you have not added any game play-changing patches)
My OpenTTD contributions (AIs, Game Scripts, patches, OpenTTD Auto Updater, and some sprites)
Junctioneer (a traffic intersection simulator)
Junctioneer (a traffic intersection simulator)
Re: OpenTTD OSX (Mac Port)
If I install it and try to run it, I get an error "OpenTTD OSX cannot be opened because of a problem." It looks like you built your port against MacPorts, which makes it worthless for all casual users. I see non-existent libraries in /opt/local/lib/ with this command:bkbusters wrote:So far, everything seems to work fine without a problem but if there are any bugs with the port (Not the game. If it is a game bug, report it to the OpenTTD team), report them to me in this thread, on the SorceForge page or email me (bkbusters@hotmail.com).
Code: Select all
# otool -L OpenTTD\ OSX.app/Contents/MacOS/openttd
Code: Select all
# lipo -info OpenTTD\ OSX.app/Contents/MacOS/openttd
Non-fat file: OpenTTD OSX.app/Contents/MacOS/openttd is architecture: x86_64
This problem is easily replicable on at least any 10.6 or later versions of Mac OS X, and probably more... There is an error in the track "Little Blue Box Car" which has so far not been fixed by the author. It exists in the version of the file you are distributing. Simply fast-forward to that track and skip to it a few times. OpenTTD will crash. It is not something that the OpenTTD developers can fix. In any case, at best Apple will fix it, and at worst, the composer will fix his MIDI file. At present, neither has happened, thus OpenTTD will eventually crash under Mac OS X when using OpenSFX.bkbusters wrote:1. I am aware of that problem but so far I haven't had any problems when I have tested it. It would be greatly appreciated if some people could test it to see if it does in fact work on other Macs.Rubidium wrote:You are aware that some OpenMSX MIDIs are known to cause Mac OS X's MIDI playback to fail, and by failing I mean crash in such an extent that it crashes OpenTTD as well
Yes, please do not label r20277 or any other version 1.0.0 or anything else that it is not! This is extremely confusing and will only add to the Mac troubles. Please call it r20277 or 1.0.3 or whatever the OpenTTD release is.Yexo wrote:I can also still get the source code for 0.7.3 with my svn client, that doesn't tell anything. What version is this exactly? Is this really 1.0.0 or just the latest trunk version at the time you got the source?bkbusters wrote:2. As for the 'outdated and known vulnerable version', I got that using my SVN client so i have really no idea how to explain that one.
Who is online
Users browsing this forum: No registered users and 3 guests