Glitch wrote:

MonocleBios wrote:Is 'FastExt.bb' in the same directory as 'Main.bb'?

Eeyup

What version of blitz3D do you have?
Put an invalid statement in fastext.bb, does another error show up?

It doesn't give me a version number, closest thing I have is the date modified which is 10/08/2011 (DD/MM/YYYY)

How do I create an invalid statement? I'm a bit of a derp with these.

Glitch wrote:It doesn't give me a version number, closest thing I have is the date modified which is 10/08/2011 (DD/MM/YYYY)

How do I create an invalid statement? I'm a bit of a derp with these.

Add something to the beginning of the file that would cause a compiler error, like the line 'ermagherd 5'

Did that, got a function not found error message and my invalid statement was highlighted.
Thanks for helping me with this btw.

Glitch wrote:Did that, got a function not found error message and my invalid statement was highlighted.
Thanks for helping me with this btw.

I'm assuming you also added the decl/dll to Blitz' userlibs directory and restarted Blitz3D.
Can you post a screenshot of the original error?

I didn't see a userlibs folder so I created my own in the same directory as blitz3d, I will get an image of the error tomorrow because its like 1:50 and I'm in bed.

Glitch wrote:I didn't see a userlibs folder

I think that might be your problem there. Have you tried getting a newer version of Blitz3D?

MonocleBios wrote:

Glitch wrote:I didn't see a userlibs folder

I think that might be your problem there. Have you tried getting a newer version of Blitz3D?

I'll look.

I tried disabling the launcher, but it keeps throwing "Memory access violation" errors on startup. Anyone else had this problem and knows how to fix?

I appear to be getting the same problem, first time I compile the source code it worked, only the program closed straight after being opened. I tried compiling again and got an error saying "function 'initext' not found".
I got the 1.98 update and put the fastext.dll in the userlibs folder, anything else I could be doing wrong?