Message 1 of 1
MAXScript Wire Controller Exception in XRef Scene
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have a problem dealing with wired parameters that are in XRef scenes.
In the scene with the parameter wiring, all works as expected. Wires work just fine (in this case, there are various helpers whose positions are wired to other object parameters).
When that scene is References in other files as an XRef scene, the other files will always start off with a barrage of Wire Parameter errors. This is what the MAXScript listener spits out:
I am curious about why this might happen and how to address it. It isn't actually breaking anything, but it is annoying to always have to close out all those errors when opening the files referencing this file.
What I don't understand is that in the original file where the wired parameters were set up, there are no startup scripts that create these wirings... they were simply wired with a function sometime in the past. Is there something inherently different about wiring an object's parameters via the wire parameter interface inside Max and the paramWire.connect and the paramWire.connect2Way functions?
Why have no startup errors in original file but cause startup errors in the referenced version?
Shawn Olson
Developer of Wall Worm
3ds Max plugins and Scripts
3ds Max 4/Gmax - 3ds Max 2020
Mudbox 2009-2019
Windows 10 x64
i7 8700K
64GB RAM
Geforce 1080ti
In the scene with the parameter wiring, all works as expected. Wires work just fine (in this case, there are various helpers whose positions are wired to other object parameters).
When that scene is References in other files as an XRef scene, the other files will always start off with a barrage of Wire Parameter errors. This is what the MAXScript listener spits out:
>> MAXScript Wire Controller Exception:
-- Unknown property: "pos" in undefined <<
-- Error occurred in __wire__()
I am curious about why this might happen and how to address it. It isn't actually breaking anything, but it is annoying to always have to close out all those errors when opening the files referencing this file.
What I don't understand is that in the original file where the wired parameters were set up, there are no startup scripts that create these wirings... they were simply wired with a function sometime in the past. Is there something inherently different about wiring an object's parameters via the wire parameter interface inside Max and the paramWire.connect and the paramWire.connect2Way functions?
Why have no startup errors in original file but cause startup errors in the referenced version?
Shawn Olson
Developer of Wall Worm
3ds Max plugins and Scripts
3ds Max 4/Gmax - 3ds Max 2020
Mudbox 2009-2019
Windows 10 x64
i7 8700K
64GB RAM
Geforce 1080ti