So, I am using CapturedStructure to scan multiple spaces in a property. I intended to use the story field available on the Surface structures within the floors field. However, they all have a story == 0; and when I enumerate(), it seems incorrect as well. This is happening to me at least after printing the CapturedStructure into a JSON. This also happens to rooms's floors: The section states one story, but the floors all say 0

So, I have been playing with the new version of RoomPlan (it is pretty awesome!). However, I found this bug... or, I think it is a bug: When I get the JSON, I get the following field, for each room: { "rooms": [ { "story": 1, "floors": [ ... ], "coreModel": "xPNhmdphlnynwusRL92NgUYKht... ... ... This is kind of annoting, as this is quite a big field. With the coreModel, the file is 828kB. When I remove it, it is 267kB.

So, I have been working with RoomPlan in an application that is sensitive to the model's orientation. However, sometimes—even if the number representing the orientation I am capturing seems right—the final orientation is quite wrong. Now, I have also noticed that sometimes (and I am not sure when, so it is kind of hard to reproduce) the representation of the room is shuffled when RoomCaptureView().captureSession.stop() is called... is RoomPlan reorganizing everything at the end? If so, is there any way to prevent this from happening? Thanks!