ResidualVM Forum

@somean: Yeah, I did that for the Windows build, but forgot to disable all the stuff in the Mac version...

@ marpieters84: Oh, yeah, that's am interesting bug. I have a suspicion what is going on -- will look into it.

I don't know which is the reason for the savegame bug, but please note that the savegames are not interchangeable between the official version of ResidualVM and this mouse version.

Hmmm, I downloaded the mac dmg file and tried running it but it doesn't seem to be working :/ I get an error message.

"Process: residualvm [2278]
Path: /Users/USER/Desktop/ResidualVM.app/Contents/MacOS/residualvm
Identifier: org.residualvm.residualvm
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [252]
Responsible: residualvm [2278]
User ID: 501

Date/Time: 2014-02-24 19:26:53.319 +0000
OS Version: Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 6B43CC0C-8F82-79BF-EA75-173ED9C1EBF4

Sleep/Wake UUID: 2234DC69-06A9-4E10-9BF0-4699D5490C67

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: /usr/local/lib/libpng15.15.dylib
Referenced from: /Users/USER/Desktop/ResidualVM.app/Contents/MacOS/residualvm
Reason: image not found

Binary Images:
0x7fff66193000 - 0x7fff661c6817 dyld (239.3) <D1DFCF3F-0B0C-332A-BCC0-87A851B570FF> /usr/lib/dyld

Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core 2 Duo, 2.26 GHz, 4 GB, SMC 1.47f2
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80AD, 0x484D54313235533642465238432D47372020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: FUJITSU MJA2160BH FFS G1, 160.04 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Internal Memory Card Reader
USB Device: Built-in iSight
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
Thunderbolt Bus:"

Ok, I fixed some issues and build new binaries (they are linked to in the first post)

Changes in 0.2:
- Fixed wheelbarrow bug
- (Hopefully) fixed savegame bug
- Mac build should now run without additional libraries
- Reorganized patches

Please let me know if the fixes work -- especially the savegame bug.

Tried the new version but still having issues. Below is the current error message, I would have no idea on how to install a newer version of libpng.

Dyld Error Message:
Library not loaded: /usr/local/lib/libpng15.15.dylib
Referenced from: /Volumes/VOLUME/ResidualVM.app/Contents/MacOS/residualvm
Reason: Incompatible library version: residualvm requires version 33.0.0 or later, but libpng15.15.dylib provides version 20.0.0

Huh, that is weird, libpng really shouldn't have been included. I manually disabled it now; can you try again ?

Ok just tried it and it appears to be working now, thanks for that

I'm still having the changing hotspots locations problem when loading
If you need any details that could help you track that bug, just ask.

Bah, I thought the fix would work
Thanks for checking, though!

Ok, let's try to reproduce this save-game thing;
a) How exactly does it show? I.e. does hitting space show wrong locations for the hotspots, does the mouse-hover indicate weird positions, or does Manny walk towards the wrong position when a hotspot is clicked ?
b) What an easy way to get this error? I.e. does it happen already if you start the game, save, and load it? Or is it specific to certain scenes for saving or loading?
c) Is this Mac or Windows?

Finally, maybe it helps if I try loading one of your savegames. If you can send me one (verticalduck at gmail dot com), that'd be awesome.

Just letting you know that I also see hotspots changing when switching to fullscreen mode.

I have commented on the bug thread in github.

Thanks for any fixes!

P.S. In other news I can run Grim with Steam Home Streaming which causes it to be encoded as a video in windowed mode and streamed full screen (scaled video). That allows me to play it in full screen with working hotspots on a secondary machine! Sadly OpenGL streaming crashes after 5 minutes due to another error, but it was still an entertaining hoop to try to jump through!

Ok, I think I have some trial for you that could help. I'm in Windows 7 64 SP1. Here's what happens:

I start the game in fullscreen. The hotspots are totally perfect located and work fine:



I save the game, and hotspots keep working as expected.

If I load the game, being both from the game's menu (F1) or from ResidualVM's main screen, the hotspots get messed up. Like this:



But guess what. If I save again (even in the same slot or in any other existent or in a new one) and then load THAT last save, the hotspots are well located and work totally fine again:



So the problem is when saving. It works like this. One save saves right, and one save saves wrong. The problem is not with the save slots, but with the action of saving, I think.

I tried this, too:

- hotspots are working fine.
- save on new slot named "1".
- load slot 1, works wrong.
- save on new slot named "2".
- load slot 2, works fine.
- load slot 1, works wrong.
- load slot 2, works fine.
- save on slot 2.
- load slot 2, works wrong.
- save on slot 1.
- load slot 1, works fine.

It's one good, one bad, one good, one bad, and so on.

EDIT: Ok, just read the github and seems this was already known. It also happens when toggling between fullscreen and windowed.

Toggling between fullscreen and windowed (or software and hardware graphics) is simply implemented as:
1: Save game.
2: Restart the game with the new graphics-state.
3: Load the savegame created in 1.

From a user-perspective this should be completely transparent, but it explains why you'd see savegame-issues pop up when switching.

I already commented on the github issue. The bug is indeed in the saving/loading code.

New Mac build gives me the following error: "Illegal instruction: 4"

I have no idea how you did this, but it is seriously impressive. I'm curious why ResidualVM needed modification, rather than just the Lua bytecode... Can you explain?