shader files using #include

Hey there,

I noticed that using #include in a shader file works fine until you compile your application.
Once compiled the engine just crashes as soon as the shader gets compiled (i.e. when an object using the shader gets visible).

It's not a big deal since I'm going to join my shader files and compile them to .fxo-files when I'm done, but you might wanna look into this.

Hm... I think I once compiled some of the default shaders (they have several #include statements) to fxo without problems.
Also I regularly used the default shaders in compiled, published and also resourced projects without any problem noticed.

Are you including with <> or with ""?

What to you mean with "compile your application"? Compiling the shader, or publishing the application?

When you publish your game, you must manually include all files that are not automatically included. That's also all shader files that you need.

Sorry, should have explained it a bit more precisely.

The crash is caused by uncompiled shaders (.fx-files) in a published application.

I've put all the required files are in the published folder.

here's a small example: crash.zip

I can confirm this. Had the same problem in a recent project.

Thanks for the example! I can confirm this problem - shader includes only work when they are compiled. We'll look into it in detail. Shader includes will be probably fully supported in the next update.

As a workaround, either compile the shader, or insert the code instead of an include.

Hi,
is there a date when it would be fixed?
Approx. 10-11 months ago I finished a new update for my MapBuilder (billboard model lod, some lighting fixes etc.), what I have wanted to release together with a new GitHub repository, but using no incudes in shaders or compiling them are no good in my case, I'm afraid it would break the workflow...

I have no ETA for the next update yet.

then is there a link to the previous engine version A8.46.2? I would move back and ask my users to do the same. (I have the installer on my disk but it would be better to use an official link)

Why would you want to do that?

in general, it would be great to have the links of the earlier versions available, they could be useful when one update has a bug stopping the project working as before. especially when updates are not so quick as before.

We don't want old versions to be around. Anyone should have the recent version. If one update really had a bug stopping the project working as before, then we would just fix that bug. Such a fix is normally released a few days after the buggy update, so I don't see why someone would need an old version.

Hi JCL, when can we get the bugfix update that cures the latest version what currently makes my project totally unusable?

Which bugfix update? Showstoppers of the last version have been all fixed as to my knowledge.

ahh, probably I missed that update, thanks