Post not yet marked as solved
When setting ARView's environment camera feed exposure to a negative value to make the camera feed dimmer, for example
arView.environment.background = .cameraFeed(exposureCompensation: -3)
can this negatively affect ARKit's ability to track the device's localization and mapping capability?
That is, is the device's use of the camera for SLAM purposes independent of the exposureCompensation value?
Post not yet marked as solved
Reviewing Apple's AnchorEntity documentation, I see that an AnchorEntity can be a child of an Entity in the RealityKit hierarchy.
Has it always been this way?
In my memory, an AnchorEntity was always just the base element in a Scene.
If this was a change by Apple at some point, has Apple given examples where making an AnchorEntity a child of an Entity lets you do cool things you couldn't do before?
Post not yet marked as solved
I'm sharing this in case someone else wants to use Apple's RoomPlan to create a model and import it into Blender.
The problem: I could not successfully import a USDZ model from the RoomPlan app into Blender. (I went through the normal process of importing a USDZ file into Blender: change the file type from ".usdz" to ".zip"; unzipped the file; then tried to import the ".usda" file). No surfaces appeared.
The solution: In Apple's source code from here, in the file RoomCaptureViewController.swift, I changed the line
try finalResults?.export(to: destinationURL, exportOptions: .parametric)
to
try finalResults?.export(to: destinationURL, exportOptions: .mesh)
recompiled, and went through the USDZ to USDA conversion process again. This time it worked.
Apparently Blender cannot import parametric USDA models.
Post not yet marked as solved
Has anyone successfully
imported Apple's (FBX) robot for Apple's CapturingBodyMotionIn3D demo into Blender
exported it back out (GLTF or other format)
converted it back to USDZ via Reality Converter
and gotten it to work in Apple's demo app again?
I have run into numerous problems, and each effort to fix a problem leads to new ones. For example, importing Apple's FBX robot has the bones pointing in funny directions (see attachment).
When I try to correct this on import by aligning the bones, the robot in the Apple app looks like it went through Star Trek transporter accident - limbs at weird angles.
Can ARKit/RealityKit track multiple bodies for animation simultaneously?
Reviewing Apple's CapturingBodyMotionIn3D sample code (for WWDC2019 session), there is no explicit linkage between the ARBodyAnchor and the loaded BodyTrackedEntity (e.g., the AnchorEntity used for the BodyTrackedEntity is not associated with the ARBodyAnchor). There seems to be some hidden linkage between the ARKit ARBodyAnchor and the RealityKit BodyTrackedEntity.
Likewise, the ARFrame has a property for only a single ARBody2D (detectedBody).
My interpretation is that only a single person can be tracked at a time. Is this correct?
Post not yet marked as solved
When I try to watch the WWDC22 "Platforms State of the Union" video on my Apple TV, iPhone, or iPad, using the Developer app, the video only shows a single frame every few seconds and there is no audio. The video plays fine on the Developer app on my Mac.
Has anyone else had this problem? Is there a work around? (I've tried deleting the Developer app on my Apple TV and reinstalling it, but no joy).
I am running into a strange bug where the exact same code compiles fine in one project but generates a compiler error in another project.
In particular, I am trying to create an AnchorEnity from an ARAnchor.
func addModelTo(anchor: ARAnchor)
{
let entityAnchor = AnchorEntity(anchor: anchor)
...
}
The compiler error message is not even consistent. Sometimes I get a single error message:
Cannot convert value of type 'ARAnchor' to expected argument type 'AnchoringComponent.Target'
Other times I get an error with two possible issues:
No exact matches in call to initializer
Candidate '() -> AnchorEntity' requires 0 arguments, but 1 was provided (RealityFoundation.AnchorEntity)
Candidate expects value of type 'AnchoringComponent.Target' for parameter #1 (got '(anchor: ARAnchor)')
I'm trying to track down why this sometimes causes an error and sometimes it does not.
Any pointers?
Post not yet marked as solved
I am creating a fixed-focus camera app with the focus distance at infinity (or at least 30+ feet away).
When I set lensPosition to 1.0, the images were blurry.
Some tests letting autofocus do the job showed a lensPosition of about 0.808 for my wide and telephoto lenses and 0.84 for the ultra wide lens did the trick. (iPhone 13 Max)
Will the lensPosition to focus at infinity vary between devices and lenses on that device?
Is there a way to determine the appropriate lensPosition at run time?
Does Apple have any documentation on using Reality Converter to convert FBX to USDZ on an M1 Max?
I'm trying to convert an .fbx file to USDZ with Apple's Reality Converter on an M1 Mac (macOS 12.3 Beta), but everything I've tried so far has failed.
When I try to convert .fbx files on my Intel-based iMac Pro, it succeeds.
Following some advice on these forums, I tried to install all packages from Autodesk
https://www.autodesk.com/developer-network/platform-technologies/fbx-sdk-2020-0
FBX SDK 2020.0.1 Clang
FBX Python SDK Mac
FBX SDK 2020.0.1 Python Mac
FBX Extensions SDK 2020.0.1 Mac
Still no joy.
I have a work around - I still have my Intel-based iMac. But I'd like to switch over to my M1 Mac for all my development.
Any pointers?
Note: I couldn't get the usdzconvert command line tool to work on my M1 Mac either. /usr/bin/python isn't there.
I had a weird case today when an endpoint system extension remained running even after I deleted the .app bundle.If I tried killing the process with "sudo kill -9 <pid>", the extension respawned.If I tried "sudo launchctl remove <name>", I was told I didn't have privilege.Searching my hard drive I found a copy of the system extension in /Macintosh HD/Library/System Extensions/...I rebooted into recovery mode, deleted the extension bundle, and restarted. Everything initially looked fine. The process did not come back.But then when I tried to re-build, re-package, re-install, and re-launch the application, the operating system complained that it could not find the system extension even though it was there in the .app bundle.The operating system seems to (A) create a cache/copy of the system extension bundle, and (my guess) (B) maintains a link to that cache location somewhere and tries to launch that cached system extension bundle.[my hacked solution was to rename the extension, including creating a new bundle ID and associated provisioning profile]Has anyone encountered a system extension that woud not die? Did you figure out how to kill it and clear out any caches of it?Thanks,
Is there an equivalent to MultipeerConnectivityService that implements SynchronizationService over TCP/IP connections?
I'd like to have two users in separate locations, each with a local ARAnchor but then have a synchronized RealityKit scene graph attached to their separate ARAnchors.
Is this possible?
Thanks,
Post not yet marked as solved
I don't know if this is an issue with Apple's Reality Converter app or Blender (I'm using 3.0 on the Mac), but when I export a model as .obj and import it to Reality Converter, the scale is off by a factor of 100.
That is, the following workflow creates tiny (1/100 scale) entities:
Blender > [.obj] > Reality Converter > [USDZ]
But this workflow is OK:
Blender > [.glb] > Reality Converter > [USDZ]
Two workarounds are:
export as .glb/.gltf,
when exporting .obj set the scale factor to 100 in Blender
Is this a known issue, or am I doing something wrong?
If it is an issue, should I file a bug report?
I am finding some unexpected behavior with lights I've been adding to a RealityKit scene.
For example, I created 14 PointLights, but only 8 appeared to be used to illuminate the scene.
In another example, I created 7 PointLights and 7 SpotLights, and the frame rate dropped quite a bit.
Are lights computationally expensive, causing some adaptive behavior by RealityKit?
Should I be judicious in my use of lights for a scene?
(Note: I set arView.environment.lighting.resource to a Skybox with a black image; my goal was to completely control the lighting. I don't know if that added to the computational load)
In a previous post I asked if 100,000 polygons is still the recommended size for USDZ Quick Look models on the web. (The answer is yes)
But I realize my polygons are 4-sided but are not planar, so they have to be broken down into 2 triangles when rendered.
Given that, should I shoot for 50,000 polygons (i.e., 100,000 triangles)?
Or does the 100,000 polygon statistic already assume polygons will be subdivided into triangles?
(The models are generated from digital terrain (GeoTIFF) data, not a 3D modeling tool)
Post not yet marked as solved
I've recently added some USDZ files to a web page, and I can download and display them fine via AR Quick Look on an iPhone or iPad.
I've noticed full occlusion is active in the AR view.
Over time, the device appears to heat up and the frame rate drops.
Are there any properties I can set in the <a rel="ar" ...> HTML tag to control things like occlusion or autofocus (i.e., turn them off)?
Todd2.