Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Thanks! re: the crash - does your mac have an intel GPU? I've noticed on my HD4000 (mac mini) that there's a very specific bug which causes the game to crash when it tries to display tool tips. I've had people test it on other mac hardware without problems, so I think it's a niche Apple aren't going to fix (they're trying to steer everyone towards using their proprietry graphics APIs, and would rather sell you a new mac than fix an old one ๐Ÿ™„) which is unfortunate. Best I can do is isolate tool tips in the next update and, as ridiculous as it sounds, ask people to navigate menus by keyboard (or controller) rather than mouse for now - sorry!๐Ÿ˜… To address your other points:

  • There's a hard limit on the physical size of the holes in the game engine, so par 5s tend to be a bit too easy because they're too short. However you can edit the hole files by exploring the app bundle and going to Contents/Resources/assets/golf/courses/ where you'll find the course data. The files ending in .hole are simply text files in which you can edit the par. Make sure to back these up before editing though, as it'll cause problems if you try playing a network game and they don't match the other player's version.
  • The club limit is a side effect caused by the game trying to guess your club set based on the distance to the pin. This was introduced with the Pitch n Putt to prevent players being able to drive the ball 200m on a 70m hole ๐Ÿคฆโ€โ™€๏ธ. I'll look into adjusting this.
  • This is very true. I will endeavour to add it in the next update ๐Ÿ˜

Thanks for all the feedback, I really appreciate it. It's what keeps me motivated and the game improving!

Thanks! Yes it's an old imac with an i7 processor. I tried just now using the keyboard and it still crashed. Also I didn't experience the crash with previous versions.  Just let me know if you want me to do any further tests.

Oh, hum. Sounds like you've found a new bug ๐Ÿ˜ฅ If you could tell me exactly the steps you do to cause it to crash, that would be awesome, so I can try and reproduce it myself. Also, if it's possible, if there's a message which says 'vga_golf quit unexpectedly', could you click on the button that says 'Report' and then from the new window copy paste the text between 'Thread 0 crashed' and 'Thread 1' and send it to me? You should be able to paste it here. I'd really appreciate it, thanks! ๐Ÿ˜ (You don't need to send it to Apple, I doubt they'd do much lol)

(+1)

Oops I read CPU, not GPU. The video card in this thing is a GeForce GTX 680MX

The steps to reproduce are just to run the programme then select Practice and then Driving Range with the keyboard. The game shuts down at that point. Here's the error report:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   libsystem_platform.dylib      0x00007fff73bfce52 _platform_strlen + 18

1   libcrogine.dylib              0x000000010bac7869 cro::ConfigObject::loadFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool) + 713

2   vga_golf                      0x000000010b65fa5a DrivingState::createScene() + 9242

3   libcrogine.dylib              0x000000010baf8f45 cro::Window::loadResources(std::__1::function<void ()> const&) + 149

4   vga_golf                      0x000000010b65476b DrivingState::DrivingState(cro::StateStack&, cro::State::Context, SharedStateData&) + 2187

5   vga_golf                      0x000000010b5b2ab7 std::__1::__function::__func<void cro::StateStack::registerState<DrivingState, SharedStateData&>(int, SharedStateData&)::'lambda'(), std::__1::allocator<void cro::StateStack::registerState<DrivingState, SharedStateData&>(int, SharedStateData&)::'lambda'()>, std::__1::unique_ptr<cro::State, std::__1::default_delete<cro::State> > ()>::operator()() + 71

6   libcrogine.dylib              0x000000010badac80 cro::StateStack::applyPendingChanges() + 944

7   libcrogine.dylib              0x000000010bada898 cro::StateStack::simulate(float) + 24

8   vga_golf                      0x000000010b5aa7e6 GolfGame::simulate(float) + 118

9   libcrogine.dylib              0x000000010bac0aa3 cro::App::run() + 1587

10  vga_golf                      0x000000010b84d471 main + 49

11  libdyld.dylib                  0x00007fff73a02cc9 start + 1

Thread 1:: SDLTimer

Awesome, thanks. This looks unrelated to the other crash, in fact I'm pretty sure I know what this is, and it should be an easy fix. FWIW the other crash happens if you hover the mouse over an option in the option menu, or over the Add Player icon - it *should* have a little tool tip/bit of text which tells you what the option does, but on intel graphics cards it just crashes ๐Ÿ˜ฅ This crash on the other hand is just me being forgetful (not setting the file path correctly to load something on the driving range) ๐Ÿ˜ณ Thanks again for the help, I'll have an update uploaded ASAP!

I've uploaded version 1.6.1 which should fix this now, thanks!

(+1)

Great, it works! :)