Author Topic: Eufloria Classic on OS X  (Read 17793 times)

0 Members and 1 Guest are viewing this topic.

kvikvi

  • Guest
Re: Dyson on OS X
« Reply #15 on: April 08, 2009, 08:09:45 PM »
you're release works perfecty, thanks so much, im such a happy person now
 ;D

Rudolf

  • Administrator
  • Old Oak
  • *****
  • Thank You
  • -Given: 4
  • -Receive: 13
  • Posts: 635
  • Euflorian Ambassador
    • Omni Systems Limited
  • Eufloria: Yes
Re: Dyson on OS X
« Reply #16 on: April 08, 2009, 11:12:50 PM »
Brilliant!
-----------------------------------------------------
Rudolf Kremers - Grand Poobah

http://www.omni-labs.com
http://www.rudolfkremers.com
http://rudolfkremers.tumblr.com/

d0k

  • Guest
Re: Dyson on OS X
« Reply #17 on: April 17, 2009, 02:33:28 PM »
I've updated my bundle with the patch.

Download patched 1.20

redliner

  • Guest
Re: Dyson on OS X
« Reply #18 on: April 20, 2009, 10:23:38 PM »
hi :D

i registered to say that Dyson works perfectly fine on OS X however, im running os x on an Acer Aspire One A150  ;)

specs:
Intel Atom 1.6Ghz single core+ hyperthreaded core
1 Gb ram
integrated GMA950 graphics
standard hard drive (not a flash type)


i copied the framwork files, and installed mono, however i installed the latest version: "2.4_7"

and i used d0k's bundle.


oh, and here's my guide for installing os x on the acer aspire one:
http://www.insanelymac.com/forum/index.php?showtopic=149173

laters!

jmiahb

  • Guest
Re: Dyson on OS X
« Reply #19 on: June 08, 2009, 04:35:18 PM »
Phiu... Dyson now works with my OS X 10.4 as well, if anybody else is interested, I linked the files:

  • 1. Install Mono for OS X.
  • 2. Copy the SDL.framework for OS X into your /Library/Frameworks directory.
  • 3. Copy SDL_mixer.framework into /Library/Frameworks directory.
  • 4. Copy SDL_image.framework into /Library/Frameworks directory.
  • 5. Copy SDL_gfx.framework into /Library/Frameworks directory.
  • 6. In Terminal, go to the directory where you un-tarred the linux build. In the directory with the executable, type: mono Dyson.exe

Thank you so much for that short overview maledyris. I had trouble finding the SDL_gfx.framework first and tried to build it myself from the source. Which I never did before and consequently failed. Anyways. Now it works, although with >60 seeds smooth playing is only possible when zoomed out max (on MacbookPro 2.2 Duo / 2GB DDR2).

Yay. :D

To get the Menu working hold mouse down and drag to see your position, no big deal, pop-ups are worse. However, the "Color-Change-Seed" is not visible.






Thanks Cem..... With your info and links......I had Dyson running on my new mac book pro in 1 min. 10.5.7



cem

  • Guest
Re: Dyson on OS X
« Reply #20 on: June 29, 2009, 09:51:12 PM »
cheers! Do you (or anyone for that matter) have the same problems with the MBP slowing down drastically with medium/big numbers of seeds? Or when zoomed out?

arhu

  • Guest
Re: Dyson on OS X
« Reply #21 on: July 14, 2009, 10:22:40 AM »
i am totally noob at os x so can you please help me and say what is exаctly i need to write in step 6
.( In Terminal, go to the directory where you un-tarred the linux build. In the directory with the executable, type: mono Dyson.exe)
of course i know how to run Terminal =) but what to do next ?

cem

  • Guest
Re: Dyson on OS X
« Reply #22 on: July 15, 2009, 07:22:06 PM »
This what you need?

Then open Terminal (OS X's command line interface), it should be located in /Applications/Utilities, and navigate to your Dyson Folder. This would look like this, if you had Dyson on your Desktop:

localhost:~ user$ cd desktop
localhost:~/desktop user$ cd dyson
localhost:~/desktop/dyson user$ mono dyson.exe

The commands are almost similar to DOS. To navigate you will need cd FOLDER or cd .. To view the content of a folder type ls

arhu

  • Guest
Re: Dyson on OS X
« Reply #23 on: July 16, 2009, 01:47:48 AM »
oh , really it is not that i was seeking =) but i already win in fight with this game XD on the other hand ty , for trying to help me

nautillus

  • Guest
Re: Dyson on OS X
« Reply #24 on: August 13, 2009, 06:10:33 PM »
cheers! Do you (or anyone for that matter) have the same problems with the MBP slowing down drastically with medium/big numbers of seeds? Or when zoomed out?

Yes I have this problem too -- I have a macbook.

Alex

  • Administrator
  • Ent
  • *****
  • Thank You
  • -Given: 3
  • -Receive: 13
  • Posts: 1,035
Re: Dyson on OS X
« Reply #25 on: August 14, 2009, 11:20:32 PM »
I've uploaded my bundle (from the linux 1.20 build):
Download (sorry for the hoster, don't have a real webspace at the moment)

You still need to install mono and copy all the SDL frameworks to /Library/Frameworks (as descripbed by maledyris and cem). But then you can start Dyson without even knowing what a terminal is :D

OK, for now I have hosted this at the Dyson site: http://www.dyson-game.com/files/Dyson_1.20.dmg

Although I'm mad grateful for the help given so far on this version, this act does not mean the Mac version is official or supported by us. I can't in good conscience say that yet. Thanks!

fluffy

  • Guest
Re: Dyson on OS X
« Reply #26 on: September 17, 2009, 03:47:40 AM »
Hi, has anyone gotten this working on OSX 10.6/Snow Leopard?   I'd heard good things about this game from a friend, and I followed the directions (and am no OSX/UNIX newbie) but unfortunately all that happens when I launch it is a segfault; unfortunately it's just within the mono runtime, meaning the OSX crash reporter can't really do much with it:

Code: [Select]
Process:         mono [78740]
Path:            /Users/fluffy/Games/Dyson.app/Contents/MacOS/Dyson
Identifier:      Dyson
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  sh [78721]

Date/Time:       2009-09-16 19:33:10.352 -0700
OS Version:      Mac OS X 10.6.1 (10B504)
Report Version:  6

Interval Since Last Report:          120406 sec
Crashes Since Last Report:           1
Per-App Interval Since Last Report:  5 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      5C321B07-6457-4B9C-8DA5-A704B2DFBE45

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: 0x000000000000000d, 0x0000000000000000
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib             0x949b3912 __kill + 10
1   libSystem.B.dylib             0x949b3904 kill$UNIX2003 + 32
2   libSystem.B.dylib             0x94a46b99 raise + 26
3   libSystem.B.dylib             0x94a5cc50 abort + 93
4   Dyson                         0x0001edc8 mono_handle_native_sigsegv + 215 (mini-exceptions.c:1598)
5   Dyson                         0x00139481 sigsegv_signal_handler + 172 (mini.c:4290)
6   libSystem.B.dylib             0x949b8b9b _sigtramp + 43
7   ???                           0xffffffff 0 + 4294967295
8   libclh.dylib                   0x177b5a7a clhFenceCreate + 3206842
9   libSystem.B.dylib             0x9497188f __cxa_finalize + 208
10  libSystem.B.dylib             0x949717a4 exit + 33
11  Dyson                         0x00134d45 setup_jit_tls_data + 0 (mini.c:2158)
12  Dyson                         0x0001e6d4 mono_handle_exception_internal + 3380 (mini-exceptions.c:1099)
13  Dyson                         0x0003cfe6 throw_exception + 212 (exceptions-x86.c:414)
14  ???                           0x00899b0d 0 + 9018125
15  Dyson                         0x000ad584 mono_runtime_class_init + 25 (object.c:228)
16  Dyson                         0x001388f0 mono_jit_compile_method + 1590 (mini.c:3972)
17  Dyson                         0x0001f275 mono_magic_trampoline + 224 (mini-trampolines.c:292)
18  ???                           0x00899066 0 + 9015398
19  ???                           0x00e716d6 0 + 15144662
20  ???                           0x00e7115f 0 + 15143263
21  ???                           0x00e6e1fa 0 + 15131130
22  Dyson                         0x000abd5c mono_runtime_exec_main + 249 (object.c:3310)
23  Dyson                         0x000afdaf mono_runtime_run_main + 340 (object.c:3089)
24  Dyson                         0x000050f3 mono_main + 5776 (driver.c:972)
25  Dyson                         0x00003452 _start + 228 (crt.c:272)
26  Dyson                         0x0000336d start + 41

(a bunch of stuff removed for brevity)

The same thing occurs if I go into the Dyson bundle and run it with mono directly.

I have heard that there are problems with SDL on Snow Leopard as not-very-old versions of it has issues with still using old, long-since-deprecated APIs (namely QuickDraw) which Apple finally officially removed, and it's possible that the version of SDL that the Dyson OSX page linked to is still using such a version, although I don't see anything in the crash report which would indicate that.  Still, just to be sure, what version of SDL is it linked against? Apparently 1.3 (which is not yet released) should be SL-compatible already but 1.2 (i.e. the most recent stable release) is not and will likely never be.

Alex

  • Administrator
  • Ent
  • *****
  • Thank You
  • -Given: 3
  • -Receive: 13
  • Posts: 1,035
Re: Dyson on OS X
« Reply #27 on: September 18, 2009, 12:28:48 PM »
"Magic trampoline" sounds like a helpfully-named routine.  >:(


I'm really sorry  :-[  but I have absolutely no time to deal with non-Windows versions of Dyson at the moment - this will all have to wait or rely as it always has on community support.

fluffy

  • Guest
Re: Dyson on OS X
« Reply #28 on: September 18, 2009, 04:15:15 PM »
Sure, I understand.  I can wait. :)

maledyris

  • Guest
Re: Dyson on OS X
« Reply #29 on: October 21, 2009, 09:34:58 AM »
Hi, has anyone gotten this working on OSX 10.6/Snow Leopard?   I'd heard good things about this game from a friend, and I followed the directions (and am no OSX/UNIX newbie) but unfortunately all that happens when I launch it is a segfault; unfortunately it's just within the mono runtime, meaning the OSX crash reporter can't really do much with it:

Ok that's weird. I'm on OS X 10.6.1 and it works for me. We're talking about the 1.20 version right? I haven't run this version in quite awhile (and now playing Eufloria on my PC desktop -- very cool by the way) but I just started up the .dmg Alex posted, and also the version I set up myself a long time ago. Both worked, so I'm confused why it wouldn't work for you. You installed all the same version libraries as mentioned in the previous posts right?