Open lextoumbourou opened 3 years ago
A temporary work around for anyone that comes across this is to remove the OptionalCoordinateFrame
lines from the rbxlx file as follows:
grep -vwE "OptionalCoordinateFrame" PlaceFile.rbxlx > PlaceFileNew.rbxlx
This is a new data type that rbx-dom doesn't support yet. Can you file a feature request over there to support this?
Looks like someone already has: https://github.com/rojo-rbx/rbx-dom/issues/167
Thanks for your help!
In the future, I want to work with @LPGhatguy on being able to ignore unknown types like this, otherwise it creates a problem where we need to release a new version every time something we don't even use gets released.
Can you tell me if this version works?
https://github.com/rojo-rbx/rbxlx-to-rojo/suites/2471064074/artifacts/53133886
I'm on Mac, but the mac version from that build seems to work. Thanks for getting on it so fast!
Looks like someone already has: rojo-rbx/rbx-dom#167
Thanks for your help!
Where can I place the temporary fix code?
Should this issue be closed? I'm having the same problem a year later and I don't know if I should open up another issue
Probably just need to update the rbx-dom crates, it's easy enough to where I should be able to do it
After latest Roblox update, Studio version:
0.473.0.420291
rbxlx-to-rojo no longer works and returns this error:Looks like Roblox may have added an additional property that the decoder doesn't like.