Cannot build, run or debug a level - help!

[karmacomposer]

Every time I try to run a simple level with a terrain, a model and a lua player script attached to it, I get this:

 

Failed to create debug process "C:/Users/MFelker/Documents/Leadwerks/Projects/Billy1/Billy1.exe".

 

It will not write the .exe no matter what I do. I changed the folder permissions to admin and I am running as admin. What should I do to make this work?

 

I also got this for the included demo level. What now?

 

Mike

[tjheldna]

Hmm sounds like you need to compile the project in Visual C++ 2013. If you have this installed, the .sln it's in your projects Projects\Windows\ folder. Once you build it under debug and release you should be able to run from the editor.

 

Is this the non steam version?

[karmacomposer]

Yes. 3.0 with IOS and Android, Lua and C++, but I am no C++ coder.

 

Mike

[Ma-Shell]

If you created your project as a C++-project, you need to do as tjheldna said (compile it from VS). If it is a LUA-project, it should work out of the box.

[karmacomposer]

I created it as a Lua project, so something is obviously wrong.

 

Mike

[shadmar]

Debug process uses a network port to send debugging information, maybe your windows firewall or somethng blocks it?

Is F6 Release mode running ok?

[tjheldna]

Yes 3.0

 

3.0 didn't come with the binaries from what I remember they need to be created by compiling. I'm still under the impression that this is the issue as in 3.0 you need to compile the project regardless if it's Lua or C++. The compiler you need then is VS 2010 instead.

 

There is no coding involved, you just need to load up the project in the compiler by opening your projects [projectname].sln file and hit build under debug and release then you will be able to run it in the editor.

 

shadmars suggestion could be it to.

 

These are the first places I would look, hope you get there.

[Josh]

That's correct. Prior to 3.1, there was no Indie Edition, and all users were expected to compile the Lua interpreter in Visual Studio. Fortunately this does not require any coding, you just have to open up the project in Visual Studio 2010 and press F7, and it will work. Be sure to compile a debug and release version.