[SOLVED] scripts located in extern_path not loading when opening world from editor

[dred]

We have our project split up into two folder structures, one for common components between different projects, and one for the specific project we are working on.  we have been using the main project data folder and using extern_path to point to the common folder.  everything works fine while running the applications.  We can switch world with world_load command with no problems. 

 

The problem arises when in the editor. Using "File->Open World" to open a world produces errors.  The error is that it can't open the script file located in the extern_path directory.  In the editor we can use world_load to load that same world fine, we just can't use the menu item.

 

Thanks,

Dusty

[silent]

Hii Dusty,

 

If I understand you correctly, world_load command can load worlds from extern_path without any errors, but loading the same world via File -> Open World will cause errors?

[dred]

Almost world is in the normal data_path but the world.cpp file includes scripts that are located in the extern_path.  world_load will load the world fine, but File -> Open World will cause errors.

 

Parser::load(): can't open "scripts/testscript.h" file in this example scripts/testscript.h would be in the extern_path.  If i were to move that script to the data_path the world would load correctly from the File -> Open World menu item.

[silent]

Thanks for the clarification.

 

I've successfully reproduced this issue and added it to our internal bug tracker.

[dred]

Thanks! 

 

Luckily there is a decent workaround of being to just use the world_load command, it will get more tedious with lots of levels, but it should work.

 

Dusty

[silent]

Hi Dusty,

 

This issue should be fixed in the next SDK update :)

[dred]

Thanks! 

 

looking forward to it!

[silent]

Fixed. Fix is available in the Unigine 2.0 RC SDK version.