You can remove pragma_path from the script and place cube.mdl inside the same directory as your script.

With level the engine expect a WMB file not hmp or mdl. This is not always required though Lite-C doesn't have WED so it make little sense. That is why I set it to NULL. (You can load WMB files with Lite-C). This should work without message after you comment out pragma_path.

HAHA! I seemed to have fixed it. You put NULL under level_load, when a blank level should be "". I then tweeked the code to insert my model, and voila! The program is complete!

Guess Lite-C is not updated yet. You can set it to NULL in A7.07.5+

If you don't have a level_load function at all you will get this message again. So in the case you are not going to use a level WMB, make sure you set it to NULL. NULL means nothing and "" is a empty string.

okay, thanks for all the help.

I'm just about to give up now. Whenever I make a new project, write my code, then compile it, it on;y runs if the program works. If it has errors, then it tells me, and closes. When I "fix" them, then run it again, it just shows me a distorted picture of some sort, usually of the last program ran or of my desktop. I can't use this if it never compiles right. Either this is SUPER buggy software, or there is something horrible wrong with the default preferences.

You can not run a faulty code. You must fix your code before you can compile and run it. Hope this helps.

You need to learn a language before you can use it, we all made that experience. For learning lite-c download the workshops, they explain everything you need for the beginning.

If there was something wrong with the software, forums would be posted to the max with a lot of angry people. My guess is your hardware or operating system. Would like to know what your using to get things running.

your right, I just get frustrated with the totally un-helpful error reports. It does only work when its all right. Thanks for help again, I'm okay now...

There are still a few minor bugs with SED and Lite-C, but most of them don't matter that much (e.g. local variables don't show up in the "code jumper"). There are, however, many things you can do to keep the coding process going smoothly. Here are a few that I have to remind myself of every now and then:

-- Options>Preferences>Environment tab>Use the current file for Test Run should be checked. I think you already have this set, but I can't quite tell from your responses to D3D's queries.

-- Never use Debug Run (red arrow) if Test Run (black arrow) will do. In Debug mode, any errors in your script will crash SED.

-- Save all necessary scripts, then wait a few seconds before testing. Sometimes the engine needs time to "catch up" with your hard drive.

-- Legacy mode is hard to read and not usually necessary. Unless you really need low-level DirectX stuff, just include <acknex.h> and <default.c> and go. This may be the reason for your program just showing the background: litec.h has created a window, but your script doesn't tell the window to do anything, so it just copies what's already there.

-- The more advanced features you use right off the bat, the greater the chance one of them "won't work" because you overlooked something small. Legacy mode and .X files are among these features.

Hope I didn't sound rude; all of these things used to annoy me, but I learned to work around them.