In my experience that is the case. Last version I used for AVP development was 5.4.1 (compiled from source). I want to move to 5.4.2 source.
Could you please elaborate on this? As in what kind of errors, logs… I want to test visionOS 2.0 for the improvements to RealityKit (blendshapes and low level mesh). I don’t think I will target Unreal project to visionOS 2.0 yet.
Hi! I also want to run UE5 on AVP, and I followed what you did above:
support A8;
enable simulator;
remove hand tracking code in OpenXRVisionOS plugin’s source code;
but it still crashed, is the version of my UE5.4.2 and VisionOS 1.2 not satisfy it?
could you pls tell your version of UE and VisionOS?
I have build VRTemplate with UE5.4.1 or UE5.4.2, but I cant launch the game on Vision Pro.
Got the error:
it seems that VisionOS 2.0 does not work with UE5, this combination is a disaster.
Thanks，and do you know anyway to make my Vision Pro to OS 1.2 or 1.1?
I can say 1.2 works. I will hold on for 2.0.
@Jiajiaju I get the logging error every time. It is not fatal the cause of the crash is elsewhere.
The engine does, but I don’t think visionOS offers it to engines based on Metal. Although it was announced at WWDC24 for 2.0.
Thanks，Its seems can only wait for official support
The only way to downgrade from visionOS (like from 2.0 Beta to 1.2) is with a USB-C developer strap. You will either need to buy one yourself or take your AVP into the Apple Store and ask them to use theirs to do it for you.
Thanks, I have downgraded my VisionPro from 2.0beta to 1.2 with delvelop strap.
Hi @Prince.TK , after all help you offered me last time, I was able to move forward on the set up. However, I still stuck at the following error:
[UE] [2024.07.02-11.36.52:702][ 0]LogSlate: New Slate User Created. Platform User Id 0, User Index 0, Is Virtual User: 0
[UE] [2024.07.02-11.36.52:702][ 0]LogSlate: Slate User Registered. User Index 0, Is Virtual User: 0
[UE] [2024.07.02-11.36.52:825][ 0]LogMetal: Warning: Metal MRT support requires an iOS or tvOS device with an A8 processor or later. Falling back to Metal ES 3.1.
[UE] MessageBox: Shader Platform Unavailable : Shader platform: SF_METAL_SIM was not cooked! Please enable this shader platform in the project's target settings.
so I am wondering if you might have any tip or clue o how I complete the set up.
It feels I am close to fix it, however I couldn’t find further info on the web.
Do we still need to build Unreal, or does 5.4.2 retail work with visionOS 1.2?
Nope, Source Compiling still needed.
I have compiled and followed the various tutorials, and then restarted twice from the beginning, and I still get hit with SDK for visionOS is not installed correctly. And when I try to add a new C++ class, I get a compile error.
5.4.3 source, visonOS 1.2
On Mac, correct ? What’s your Xcode Version ?
Go to Xcode, settings. Verify that :
Command Line Tool.
You should have something else. Maybe 15. Because I’m on the last bêta.
Your project folder is on the root folder of Unreal, right ?
When you go Platform button of the viewport. Is it find the vision os SDK ?
Unreal Engine 5.4 VisionOS Build on Apple Vision Pro | by SpatialBiggs | Medium thisi is the article I am following by the way.
Alright! I have things almost working. I restarted from the ground up - but when I go to package my project I am left with this error as it finishes.
UATHelper: Packaging (VisionOS): ld: warning: Could not find or use auto-linked library 'swiftCxxStdlib'
UATHelper: Packaging (VisionOS): ld: warning: Could not find or use auto-linked library 'swiftCxx'
UATHelper: Packaging (VisionOS): ld: warning: Could not find or use auto-linked framework 'CoreAudioTypes'
UATHelper: Packaging (VisionOS): Undefined symbols for architecture arm64:
PackagingResults: Warning: Could not find or use auto-linked library 'swiftCxxStdlib'
PackagingResults: Warning: Could not find or use auto-linked library 'swiftCxx'
PackagingResults: Warning: Could not find or use auto-linked framework 'CoreAudioTypes'
UATHelper: Packaging (VisionOS): "_OBJC_CLASS_$_VNDetectFaceRectanglesRequest", referenced from:
UATHelper: Packaging (VisionOS): objc-class-ref in Module.AppleVision.cpp.o
UATHelper: Packaging (VisionOS): "_OBJC_CLASS_$_VNImageRequestHandler", referenced from:
UATHelper: Packaging (VisionOS): objc-class-ref in Module.AppleVision.cpp.o
UATHelper: Packaging (VisionOS): ld: symbol(s) not found for architecture arm64
UATHelper: Packaging (VisionOS): clang: error: linker command failed with exit code 1 (use -v to see invocation)
UATHelper: Packaging (VisionOS): Total time in Parallel executor: 3.71 seconds
PackagingResults: Error: linker command failed with exit code 1 (use -v to see invocation)
UATHelper: Packaging (VisionOS): Total execution time: 14.20 seconds
UATHelper: Packaging (VisionOS): Took 14.31s to run dotnet, ExitCode=6
UATHelper: Packaging (VisionOS): UnrealBuildTool failed. See log for more details. (/Users/caseyhupke/Library/Logs/Unreal Engine/LocalBuildLogs/UBA-UnrealPak-Mac-Development.txt)
UATHelper: Packaging (VisionOS): AutomationTool executed for 0h 0m 16s
UATHelper: Packaging (VisionOS): AutomationTool exiting with ExitCode=6 (6)
UATHelper: Packaging (VisionOS): RunUAT ERROR: AutomationTool was unable to run successfully. Exited with code: 6
PackagingResults: Error: AutomationTool was unable to run successfully. Exited with code: 6
PackagingResults: Error: Unknown Error
Thanks for the reply! Double checked. Same as yours, the reason for “SF_METAL_SIM was not cooked!” seems a different one. Any other idea?
Just tried out 5.4.3, and it doesn’t build correctly, either (still can’t create the workspace, much less compile things correctly).
I’m kinda surprised that three months and four releases after supposedly adding support to Unreal Engine, that support is still not present, especially since it apparently existed months ago and just needs some already-working parts to be put in the main distribution.
I realize that Epic has lots of platforms to worry about, that Epic and Apple never quite see eye to eye, and that Vision Pro is a niche inside a niche, but at this point it’s becoming a little irritating that they can’t be bothered even to do the absolute minimum necessary to get a build that doesn’t require manual everything (and that Epic has advertised non-existent existing support for). This isn’t a “little bug,” it’s a “can’t even start “Hello World” unless you’re willing to build everything yourself.”