You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Loading a project with custom classes will often result in the following compilation shown in the screenshots. You have to open and close the project a ridiculous number of times(often 30+ times) for the classes to eventually compile.
To Reproduce
Steps to reproduce the behavior:
Open a project containing scripts with a custom class
See error in output window
Open another project that does not contain custom classes
Repeat steps until the custom class compiles
Expected behavior
Custom classes should compile the first time upon opening a project with them like in previous versions of WolvenKit.
Screenshots
Desktop (please complete the following information):
OS: Windows 10
Browser: Firefox
Version 10.0.19045.2251
Additional context
I've reported this on discord before but with the next gen version coming up I thought it would be a good idea to document it here as well. Sorry if this is already planned to be addressed.
The text was updated successfully, but these errors were encountered:
This issue seems to be fixed in the latest stable build(7.2) as custom classes appear to compile reliably. However, it is no longer possible to add new chunks with customs classes to CR2W files. They do not appear in the dropdown to select a class when creating a new variable. Please see the example below. I have three new classes in the my project however they do not appear in the dropdown when adding a new list element as they did in previous versions. I know I brought this up on discord earlier but I just wanted to document it here as well. My apologies for the repeat request.
Describe the bug
Loading a project with custom classes will often result in the following compilation shown in the screenshots. You have to open and close the project a ridiculous number of times(often 30+ times) for the classes to eventually compile.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Custom classes should compile the first time upon opening a project with them like in previous versions of WolvenKit.
Screenshots
Desktop (please complete the following information):
Additional context
I've reported this on discord before but with the next gen version coming up I thought it would be a good idea to document it here as well. Sorry if this is already planned to be addressed.
The text was updated successfully, but these errors were encountered: