Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Native Mac Testing Build (Mojave and lower)
#11
(05-23-2020, 09:33 AM)Quenz Wrote: Here you are. The other logs (dev8null.log, FWnull.log, USBnull.log) are empty, and padLog.txt simply contains "PADinit"
Hmm sadly it doesn't seem to have managed to get the crash info into there
BTW not sure if you noticed but there's a new release up that should fix the graphics glitching (mostly at least, shadows were still a bit funny on my 6770m)


(05-25-2020, 11:04 AM)Behodar Wrote: With that said... is there a fullscreen option that I haven't discovered yet, or is that still on the to-do list?
Does the green window button not work?
Reply

Sponsored links

#12
(05-24-2020, 09:24 PM)Behodar Wrote: Just to keep you on your toes, here's an interesting one:

I originally had my game images sitting on my desktop. Using 'Boot ISO (fast)', I could select an image and it'd run. Then I tidied things up a bit, and put the images on a different drive. Now when I select an image, PCSX2 immediately crashes (report attached). If I move them back to the desktop then they work again.

The full path to the images is /Volumes/Data/PS2 Games. I thought it might be the space, but removing it didn't help. I also wondered whether it might be the path length, but running from the root of /Volumes/Data also crashes. My desktop is on an APFS drive while Data is HFS+.

Any ideas what's causing this one?

Edit: Forgot to say that there's nothing added to emuLog.txt; it has the usual startup stuff up to 'plugins loaded successfully' but nothing else.

Edit #2: I did 'reset all settings' (or whatever it's called) and it's working now... including Kingdom Hearts! Strange, but resolved.

Okay I'm getting crashes whenever PCSX2 tries to add a 5th item to the ISO list, that's probably your issue. Will hopefully be fixed soon™
Reply
#13
(05-25-2020, 11:25 AM)TellowKrinkle Wrote: Does the green window button not work?

Not the way that I'd expect. This moves the ~640x480 game into the top-left corner and turns the rest of the screen black. Double-clicking the window does the same thing. Unfortunately my other machine is running 10.15 so I can't test it there.

(05-25-2020, 11:38 AM)TellowKrinkle Wrote: Okay I'm getting crashes whenever PCSX2 tries to add a 5th item to the ISO list, that's probably your issue.

That would explain it Smile
Reply
#14
I am—by choice—running the very old OS X 10.9, so the amount you care may vary. However, I wanted to report that the GS, PAD, and SPU2 plugins are apparently unable to load on this system.

In the log:

Code:
[wx] dlopen(/Applications/PCSX2.app/Contents/MacOS/plugins/libGSdx.dylib, 2): Symbol not found: _mkostemp
  Referenced from: /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
  Expected in: /usr/lib/libSystem.B.dylib
in /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
[wx] dlopen(/Applications/PCSX2.app/Contents/MacOS/plugins/libonepad.dylib, 2): Symbol not found: _mkostemp
  Referenced from: /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
  Expected in: /usr/lib/libSystem.B.dylib
in /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
Plugin Enumeration Thread complete!
[wx] dlopen(/Applications/PCSX2.app/Contents/MacOS/plugins/libspu2x-2.0.0.dylib, 2): Symbol not found: _AudioComponentFindNext
  Referenced from: /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libportaudio.2.dylib
  Expected in: /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
in /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libportaudio.2.dylib

This results in me being unable to select those plugins in the configuration page, and—by extension—use the emulator.
[Image: Screen-Shot-2020-05-27-at-1-22-38-PM.png]

Again, I'm on 10.9, so you may not care—but the app currently lists 10.9 as supported, and it would be super cool if it could run! Smile Hopefully it just needs the deployment target to be changed, or some such?
Reply
#15
(05-27-2020, 07:26 PM)Wowfunhappy Wrote: I am—by choice—running the very old OS X 10.9, so the amount you care may vary. However, I wanted to report that the GS, PAD, and SPU2 plugins are apparently unable to load on this system.

In the log:

Code:
[wx] dlopen(/Applications/PCSX2.app/Contents/MacOS/plugins/libGSdx.dylib, 2): Symbol not found: _mkostemp
  Referenced from: /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
  Expected in: /usr/lib/libSystem.B.dylib
in /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
[wx] dlopen(/Applications/PCSX2.app/Contents/MacOS/plugins/libonepad.dylib, 2): Symbol not found: _mkostemp
  Referenced from: /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
  Expected in: /usr/lib/libSystem.B.dylib
in /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libffi.6.dylib
Plugin Enumeration Thread complete!
[wx] dlopen(/Applications/PCSX2.app/Contents/MacOS/plugins/libspu2x-2.0.0.dylib, 2): Symbol not found: _AudioComponentFindNext
  Referenced from: /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libportaudio.2.dylib
  Expected in: /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
in /Applications/PCSX2.app/Contents/MacOS/../Frameworks/libportaudio.2.dylib

This results in me being unable to select those plugins in the configuration page, and—by extension—use the emulator.
Yeah the issue is that while the app is compiled with 10.9 as the deployment target, the libraries it included (supplied by MacPorts) were compiled for the version of macOS on the computer I was running (10.12)
If you want, you can try installing libffi and portaudio with MacPorts (include +universal for 32-bit support) and then replace the dylibs in PCSX2.app/Contents/Frameworks with the ones from your MacPorts and hopefully it'll work
Edit: It looks like MacPorts has a macosx_deployment_target flag so I can try setting it to 10.9 on my computer for the next build and see if it helps
Reply




Users browsing this thread: 1 Guest(s)