Post not yet marked as solved
Since the 3 entities are children of Body, applying anything to the parent should (will?) effect the entire thing. Will be easy enough to test, right?
Post not yet marked as solved
Thanks Henry, for such a thorough answer.
You illustrate the problem. The last line where you call applyImpulse on physicsBody results in "Value of type 'PhysicsBodyComponent' has no member 'applyImpulse'". That's the challenge I am trying to resolve. Upon what object is applyImpulse supposed to be called on if not physicsBody as you (and I) have defined:
guard let physicsBody = tappedObject.entity.components[PhysicsBodyComponent.self] as? PhysicsBodyComponent else {
fatalError("PhysicsBodyComponent not found on the entity")
}
To further clarify, this is a gesture handler that shows the issue:
func Throw(objToThrow: EntityTargetValue<TapGesture.Value>) {
let entT = objToThrow.entity
let comp = entT.components
let pbc = comp[PhysicsBodyComponent.self]!
let physicsBodComp = pbc as PhysicsBodyComponent // Type casting is unnecessary as pbc is already a PhysicsBodyComponent
let impulse = SIMD3<Float>(x: 0.0, y: 10.0, z: 0.0)
let position = SIMD3<Float>(x: 0.0, y: 0.0, z: 0.0)
let referenceEntity: Entity? = nil
physicsBodComp.applyImpulse(impulse, at: position, relativeTo: referenceEntity); // <<< error here
}
Thanks!
Post not yet marked as solved
I don't see it either. I suspect they took it out due to issues. I too would like to detect collisions with particles. Might be a question for DTS.
Cheers...
Post not yet marked as solved
Same issue here. Would love to see how P.E.'s work. Any ETA on repairs?
Post not yet marked as solved
Yeah, it's kinda how Apple does things. In a way it makes sense - work out as many bugs as possible then do a big release. But in the mean time, us developers are kinda in a holding pattern. I'm sure they know that and have a release schedule, so we'll just have to wait. I think they said that iOS will go public beta in July so we should definitly see something before that release.
Post not yet marked as solved
Yeah I think you’re right. I’ve been an Apple developer since the Mac first came out in 1984 and honestly this is one of the most exciting updates / releases I’ve seen in 35 years with Machine Learning, Augmented Reality, new programming methodology in Swift, and a ton of other things. Very exiting future!
Post not yet marked as solved
Yes, no new templates. Hmmm.... I wonder when.FWIW, I wrote a playground that calls the MLObjectDetector framework and while it works and results in models, it is extreamly slow to produce even modest models - not sure how much it is actually using the GPU, and the results out of these models so far are super sub-par in terms of object detection. I am still working on that. It makes me think there might be bugs deep down inside the Object Detection guts, but I don't know for sure. Maybe when they fix these supposed bugs (mid June of 19 now), the templates will show up...
Post not yet marked as solved
You can look for public models to start. https://developer.apple.com/videos/play/wwdc2019/704/ talks a little about that at the beginning.
Post not yet marked as solved
Take a look at https://developer.apple.com/videos/play/wwdc2019/704/ to embed your users own data back into the model.
Post not yet marked as solved
I think you mean, how do you add to one of these existing datasets using it as a base, right? No I don't - that's a good question. I do remember watching a video on how a user can modify an existing dataset and customize it with their own data, but I don't know how to take a pre-baked dataset and add to it during development then deploy that amended data in a final app. But there must be a way!Sorry...
Post not yet marked as solved
BTW, here are Apple's community derrived models: https://developer.apple.com/machine-learning/models. A decent starting point perhaps.
Post not yet marked as solved
I suspect Apple will come out with a new Create ML upon the next update. I emailed a number of the ML engineers to try to find out what is going on.I've not used external .mlmodel files before but there were instructions I saw somewhere on the developer site. A concern that one of the Apple Engineers expressed in one of the videos was to beware that these public models are pretty generalized so don't work ideally in actual implementations - or better said: they are great starting points but should be amended to or replaced by your own data collection efforts.One interesting thing to note is that while Apple provides a great tool in Create ML, they "forgot" to design at least a basic image collection gathering toolset (that I am aware of) to help one gather and tag images in an easy manor like Create ML. Things can be done in Python and Playgrounds but it would have been nice for them to provide a comprehensive toolset for image (and audio) gathering and tagging.Still, Create ML and Apple's ML to begin with is AMAZING!
Post not yet marked as solved
I am looking for the other templates as well. I suspect (hope) Create ML will be updated in a week or 2. I'd like the Object Detector image of the Image Classifier.
