AggrorJorn Posted June 17, 2013 Share Posted June 17, 2013 When a lua script contains an error, the debugger will tell me in which script. However, if the path is quite long, I can't see in which script the problem is. 2 Link to comment Share on other sites More sharing options...
Admin Posted June 25, 2013 Share Posted June 25, 2013 Does this occur when the engine is run in debug or release mode? Are you sure your project is up to date? Link to comment Share on other sites More sharing options...
MikeClarke Posted June 25, 2013 Share Posted June 25, 2013 This occurs for me when i run the game via run debug, i can't scroll across the content to see what errors were generated. Operation Mosquito Recruiting 3d Modeller/Animator. (pm if interested) It is the greatest of all mistakes to do nothing because you can do only a little. Do what you can. - Sydney Smith Link to comment Share on other sites More sharing options...
Josh Posted June 25, 2013 Share Posted June 25, 2013 You mean the Darkness Awaits example game? Are you using the default installation path? My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
AggrorJorn Posted June 25, 2013 Author Share Posted June 25, 2013 Both debug and run show the same error. And in both situations I can't see in which script it is. Link to comment Share on other sites More sharing options...
Admin Posted June 25, 2013 Share Posted June 25, 2013 Will need your project, and the path it's installed to. I created a project with a very long path and had no problems: "c:/leadwerks/projects/sfhkljhakljshlkjashfdlkshfljkdshafdsjlhfdsjklfhksjafdsa/sdfsajdfhslkajhflskdajhfsladkfhsaldkfhsdkl/test/scripts/mover.lua" Link to comment Share on other sites More sharing options...
AggrorJorn Posted June 25, 2013 Author Share Posted June 25, 2013 even when you get an error? Wait I will set up an example. Link to comment Share on other sites More sharing options...
AggrorJorn Posted June 25, 2013 Author Share Posted June 25, 2013 A small test to replicate the issue. If you run the project in the editor with the script editor open, you will see the warning. in the example I only compiled the Release version. Link to comment Share on other sites More sharing options...
Admin Posted June 25, 2013 Share Posted June 25, 2013 I can produce the error, and it only occurs in release mode. So the problem is in the LuaJIT code... Link to comment Share on other sites More sharing options...
Admin Posted June 26, 2013 Share Posted June 26, 2013 Fixed for next patch. Link to comment Share on other sites More sharing options...
Recommended Posts