Molly Rocket

[sean]

The source code probably has a lot of incompatibilities with actual platforms, so getting it to compile and run will be difficult on some platforms. I'm not sure there's much reason to actually run it in the first place, as there's no documentation on how to use the UI, nor is there actually much interesting to see in the demo that I didn't already show in the talk, but for people who want to, please post source fixes and such here.

Here's the first one; I developed under VC6, so the included stb.h appearently has a few warnings under later VCs. The code isn't even being used in the demo, but the easiest fix is to download the latest stb.h: http://nothings.org/stb.h

[dreamfall]

I have updated the stb.h and now I just get:
error LNK2019: unresolved external symbol _stb_barrier referenced in function _update_vtex
error LNK2019: unresolved external symbol _stb_force_uniprocessor referenced in function _stbwingraph_main

Before that I added _CRT_SECURE_NO_WARNINGS
_CRT_NONSTDC_NO_DEPRECATE
to project->settings->preprocessor,

and also changed swprintf parameters to
swprintf(full_path, 50, L"%s*", stb__from_utf8(path));
to get rid of errors and warnings.

I am using Geforce 8800, windows 7, vs2008.

Any idea how to fix it?

[sean]

[dreamfall]

First it is two unresolved external symbol errors:

1>demo.obj : error LNK2019: unresolved external symbol _stb_barrier referenced in function _update_vtex
1>demo.obj : error LNK2019: unresolved external symbol _stb_force_uniprocessor referenced in function _stbwingraph_main

so I comment out three lines using:(guess I shouldn't do that)
stb_barrier(); and stb_force_uniprocessor();

then comes the assertion fatal error:
error C0204: version directive must be first statement and may not be repeated

[sean]

Ok, so the deal is the newer stb.h disabled threads by default, and I assumed the demo wasn't using threads. It probably isn't really; I probably started working on trying to have a background thread build the surface cache and gave up on it. (I don't remember, since this was 2 years ago.) So just commenting that stuff out is fine.

[dreamfall]

I am sorry that I expressed in the wrong way.
I found that assert happens when initializing the demo and compile the frag_shade_unlit, just at glGetObjectParameterivARB.

I didn't think I would have to go into such detailed things to make it work. And I won't bother to go on if there are tons of errors ahead just as you said.
Thank you anyway.

[sean]

Oh, I see, it's a compiler error from the shader compiler.

Yeah, it doesn't sound like it's worth it at this point.

[Bob]

If someone is still interested, got it running in VS2010, using a Geforce GTX 280.

Stuff I changed:
Removed one file in the project that triggered the custom build thing, it was in glsl shaders I think.
Removed the version line in virt_text.txt
Modified this line in virt_text.txt:
result.grad = vec4(dFdx(address) * gradient_scale, dFdy(address) * gradient_scale);