Closed LimeProgramming closed 2 weeks ago
We need logs for this.
They are necessary, if you don't provide us with the information to resolve issue, we won't look into it.
I've reported the issue as far as I am willing to/feel necessary to. If you choose not to look into it, that's up to you. Have a good day.
You're not giving us the necessary information to resolve the issue. This is not up to us, it's up to you.
If you don't want to give us the info we need to look into this and resolve the issue, that's your choice, not ours.
I've reported the issue as far as I am willing to/feel necessary to. If you choose not to look into it, that's up to you. Have a good day.
Its more necessary to see why you're having issues than you think, connecting GUIDs to writes seems to work fine as far as I can tell, even overwriting the types is fine
Usually if you're asked for logs after the issue it means that they genuinely are needed or something could be going wrong on your end that could be solved
@LimeProgramming
There are two Write nodes, ValueWrite<T>
and ObjectWrite<T>
- have you tried both to make sure you're not using the wrong one? I've noticed that the "ribbon gets stuck on the tool" thing happens when the wrong one is used based on the input type sometimes, eg when I've tried attaching a BodyNode enum value to an ObjectWrite
.
Describe the bug?
Guid types only plug into format string node, a write or a dynamic node just don't work, wire gets stuck to flux tip.
I've seen it a few times before with different nodes depending on how they are spawned.
To Reproduce
try plugging Random Guid into a write node or anything that isn't a "format string" node
Expected behavior
Guid threads plug into things that take guid threads
Screenshots
https://github.com/user-attachments/assets/cd0220be-1d2d-46a7-b2f7-ca6cb22fa51c
Resonite Version Number
2024.10.29.1229
What Platforms does this occur on?
Windows
What headset if any do you use?
pico 4
Log Files
I'm open to discussing the issue further if you'd like, though I won’t be sharing logs in this case, as I feel they’re unnecessary here and their exclusion is not a valid excuse to dismiss this issue.
Additional Context
No response
Reporters
U-Calamity-Lime @calamitylime