AggrorJorn Posted September 5, 2010 Share Posted September 5, 2010 So I am getting this error somewhere on a line but the engine.log as wel as the warning do not show me in which file this is. Lua error: [string "g:/visualknights/my dropbox/Project Blabla/s..."]:141: attempt to compare nil with number I checked multiple files, but they all happen to have a blank line at line 141. Is there a way to find out in which file the error occurs? Quote Link to comment Share on other sites More sharing options...
Laurens Posted September 7, 2010 Share Posted September 7, 2010 Wow, thats a wonderful person, lol. Can't you run your application with engine.exe and check the console window (not the log) for the error or is that truncated as well? EDIT: the profanity filter is lol as well Quote Link to comment Share on other sites More sharing options...
AggrorJorn Posted September 7, 2010 Author Share Posted September 7, 2010 Nope unfortunately the command line shows the exact same thing as the engine.log and error message. Quote Link to comment Share on other sites More sharing options...
macklebee Posted September 7, 2010 Share Posted September 7, 2010 look at the line right above it that actually has code... sometimes the debugger is off a line when syntax errors occur. Quote Win7 64bit / Intel i7-2600 CPU @ 3.9 GHz / 16 GB DDR3 / NVIDIA GeForce GTX 590 LE / 3DWS / BMX / Hexagon macklebee's channel Link to comment Share on other sites More sharing options...
Josh Posted September 8, 2010 Share Posted September 8, 2010 It's a problem with LuaJIT. I need to recompile it with the max string length increased. Quote 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 September 8, 2010 Author Share Posted September 8, 2010 Thats good to know. So it is easily solveable? Quote Link to comment Share on other sites More sharing options...
AggrorJorn Posted September 11, 2010 Author Share Posted September 11, 2010 Any possible solution for this? I still haven't found the error due to this debugging cause. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.