Before opening this issue, I ensure that...
Editor Tool
Scene Editor
RSDK Version
v3
Expected Behavior
R41D/Act1.bin loads normally.
Actual Behavior
Sprites appear garbled.
Steps to Reproduce
What I did was load every scene in its proper order to get its level data in XML format, ie.
- Load Palmtree Panic 1; save XML
- Load Palmtree Panic 1 Past; save XML
- ...etc until getting to R41D, which is Tidal Tempest Bad Future
To fix, close the Scene Editor tab and reopen it.
On exporting XML, it seems like whether there were garbled sprites or not, the data was identical - so it could be a rendering issue.
Also, I got a bunch of "Warning: QString::arg: Argument missing:" errors in the log output, but this also happened with stages that rendered normally.
ie.
Warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64641, resource id: 10741315, major code: 40 (TranslateCoords), minor code: 0 (:0, )
RETROED: Loading scene... 0%
RETROED: 14%
RETROED: 28%
RETROED: 42%
RETROED: 56%
RETROED: 70%
RETROED: 84%
RETROED: Loaded scene Act1.bin
Warning: QXcbConnection: XCB error: 3 (BadWindow), sequence: 449, resource id: 10746055, major code: 40 (TranslateCoords), minor code: 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"3\">3</variable>" , 3 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"unused\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"unused\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"5\">5</variable>" , 5 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
Warning: QString::arg: Argument missing: "<variable name=\"propertyValue\" type=\"uint8\" value=\"0\">0</variable>" , 0 (:0, )
...about 300 more
Screenshots
(It does, however, look very cool.)




Was another editor used on the file(s)?
No response
Platform
Fedora Linux 41
Additional Comments
Tested with both CD Mobile and CD Origins datafiles.
Before opening this issue, I ensure that...
Editor Tool
Scene Editor
RSDK Version
v3
Expected Behavior
R41D/Act1.bin loads normally.
Actual Behavior
Sprites appear garbled.
Steps to Reproduce
What I did was load every scene in its proper order to get its level data in XML format, ie.
To fix, close the Scene Editor tab and reopen it.
On exporting XML, it seems like whether there were garbled sprites or not, the data was identical - so it could be a rendering issue.
Also, I got a bunch of "Warning: QString::arg: Argument missing:" errors in the log output, but this also happened with stages that rendered normally.
ie.
Screenshots
(It does, however, look very cool.)
Was another editor used on the file(s)?
No response
Platform
Fedora Linux 41
Additional Comments
Tested with both CD Mobile and CD Origins datafiles.