Slitherine

Dear tech support,

I installed BA on a Macbook with OS X Lion on it, using filesystem with case sensitive enabled.
Now BA does not run, cannot find the file CONFIG/SYSTEM.TXT, actually this is called Config/system.txt on my filesystem. In past i had a filesystem without case sensitive, that worked.


So i thing you guys made an error, should be easily correctible i hope.
Can you help me fix my game so in can play it?

Kind regards

Have you tried to a Permissions repair?

Restart with the command-r to perform a disk repair on the main HD?

I can not find the file you mentioned. Where is it?

Have you tried to rename "My Games" in ~/Documents and re-install the application and start over?

Hello pk867,

Permission repairs does not solve anything, i, the user logged on, have full read/write permissions. Also the OS is new installed and clean.

First of al the file i mentioned is is the right place. The installation seem
Main location /Application/BA.app
Within this directory resides the file /Application/BA.app/Content/Resources/Config/system.txt .

I have other games installed, they work and give me no problems.

My work around, use usb drive formatted Mac OS Extended (Journaled). Install the game and it works.
Maybe i might create a virtual image/drive and that wil work too. I also found on the forum of Steam (https://support.steampowered.com/kb_cat.php?id=81) this work around (http://forums.steampowered.com/forums/s ... st14944714)

Just check it, simply creating an new blank disk image, formatting it with Mac OS Extended (Journaled), mount it, then copy BA onto it, start BA and it works. Enjoy.

So although i used a work around to get the game up an running, i think the developers have to fix this issue the right way.

But, yes there is a but. Should we use a case sensitive file system? By default Apple ships there computers with drives formatted as Mac OS Extended (Journaled), so this is probably the best choice to use for the main OS partition. Poor judgement for Apple i mean, it's more a choice Microsoft likes to make, opt the easy way out, instead of fixing it. But that's another discussion too be held some place else.

Sheers and thanks for the input.

Hmmm - From my point of view, I would prefer for the developers to work on ensuring that the software works with the OS as shipped from the manufacturer rather than having to accommodate for non-standard use cases. By the way, Another way to solve your dilemma would be to repartition your drive so that you have a standard partition on it to store all software that does not like case sensitive names (and that includes most of Adobe software) - However, the only thing that matters is that tomorrow is Christmas so;

Merry X-Mas

I'm afraid that the OSX version doesn't support case sensitive filenames. Some of the pipeline tools for the iOS version have to deal with case sensitive filenames, but I don't really want to add more steps to the OSX mastering process to support it. As you say, you have to deliberately alter the install settings to force the OS to use them.

To speak to your question, personally I can't see any advantage to file sensitivity in a file system. There is almost never going to be a case where text.txt, Text.txt and text.TXT are desired to be different files, where the filenames in some way give useful information through their caseness. But it's something of an religious argument I think.

I am glad you are up and running anyway!

Cheers

Pip

Yeh it's trivial for normal use indeed. Maybe add this to your system requirements to prevent mishaps like these from happening to other people.

Wish you all a merry christmas and a happy new year.