Unfortunately allowed a minor (10.1->10.2) Xcode update today and now NAP projects (including demos) can compile but always crash on run.
Error is always:
error: memory read failed for 0x0 and
Thread 1: EXC_BAD_ACCESS)
Downgrading back to Xcode 10.1 “resolves” the problem. But might be good to look into this?
Yes, this is something we need to look into, haven’t encountered it before.
The move to Mojave caused a lot of issues for a lot of others that use OpenGL, we resolved those but no idea what changed from version 10.1 to 10.2
Yup, Apple officially deprecated OpenGL in Mojave:
“Apps built using OpenGL and OpenCL will continue to run in macOS 10.14, but these legacy technologies are deprecated in macOS 10.14. Games and graphics-intensive apps that use OpenGL should now adopt Metal. Similarly, apps that use OpenCL for computational tasks should now adopt Metal and Metal Performance Shaders,” the company noted.
Most modern games with 3D graphics are not hard coded using low-level OpenGL. Instead, developers make use of higher-level graphics “engine” frameworks such as Epic Games’ Unreal Engine 4; Blizzard’s WoW and SC2 Engine; or Unity Engine. Like Apple’s own higher level graphics frameworks such as SceneKit, SpriteKit and ARKit, these already make native use of Metal under the scenes.
Way to go, and Apple refuses to support the true OpenGL successor Vulkan, which we’d love to adopt, instead of writing specific render back-ends for every OS (DirectX, Vulkan and Metal), which is hard to do for a small company like us.
I recently dove into Vulkan and really like the design, more open, low level and therefore compact. Great multi-threading support and modern api design. Much more in line with DirectX, but works cross platform and has been adopted by Google to be their new back-end for their just announced streaming platform.
Apple is really making the lives more difficult for the more ‘advanced’ users, going into a direction I find more difficult to justify every single day. Also: nobody that I know uses Unreal Engine 4 on macOS, macOS has never been a gaming platform, but a creative platform.
Sorry for the rant
Rant totally and utterly justified, Coen.
Jesus H. Christ this is so idiotic. For the first time since switching to Mac I’m considering opting out again with this kind of business ethic from Apple.
Just ran into the same issue with Jerre, a new developer with 4DSOUND, who is also starting using NAP…
He will post the stack trace below!
thanks for the introduction, I’ve attached a screenshot of the stack trace, hope it helps…
This is from a freshly created project built with XCode 10.2, OSX 10.14.4
Hey, The current build of the NAP package only supports XCode 10.1
@stijnvanbeek has access to source and can build a package using XCode 10.2. I did this before and managed to successfully build and run all the demos.
I am not in a position to update the downloaded package atm.
In reply to my last reply (jaja) I’d like to add that a package using 10.2 loads perfectly fine in a 10.1 environment.
Good to know. “Forward compatibility” so to speak.
Apple, one step forward, two steps back? Also, I don’t get why XCode is updated automatically on an OSX machine, what are they thinking? The hours I have spend fixing their relentless forcing of updates. Honest aholes.