Okay, I did search the forums and found no answer for my question.

When I set up Evolved's Fresnel Water Shader from "The Ultimate Shader Pack", I get this:


Obviously, the refraction's a little messed up. I've checked the actual output of the refraction camera, it is those colored lines you see. As the Refraction demo in the pack works fine, I don't see why this shouldn't be fixable. But I'm new to shaders, and I have tried and can't figure out the problem. This error also occurs in Evolved's Fresnel Water demo, and my code is practically identical to his.

Does anyone know what's going wrong here?

Welcome to DarkBASIC Pro, every 'upgrade' breaks something.

Which update are you using though? I have 6.6b on my machine and it's practically broken shaders for me however I'm forced to use it as my project uses the Enhanced Animations plugin. If I were you It'd stick with 6.2 for now and shaders including the Fresnel one should work without problems.

I don't know what I have, but whatever it is probably's higher than 6.2 - crap, how come

every 'upgrade' breaks something

? Upgrades arn't supposed to do that... oh well, go figure I guess. I take it from the way you're talking it's possible to downgrade? I suppose I'll go try that then.

Okay, I went back to 6.2 (had been using 6.3, so no big deal) and nothing broke - but the Fresnel works beautiful. Thanks a million.

-thinkdigital

I use 6.2 for lots of reasons.

6.2 kid here as well

I'd bet that the fresnel water shader problem is to do with camera/sync mask numbering that has changed with a recent upgrade.

U6.6b works fine for me (when I remember which bits of functionality have changed ).

@Dark Coder

I have 6.6b on my machine and it's practically broken shaders for me however I'm forced to use it as my project uses the Enhanced Animations plugin.

What problems are you having? U6.6b seems to work fine with shaders for me (but not the original U6.6 admittedly ). But I haven't done so much with shaders recently so I might have missed something.

If you have a simple demo of one that fails post it and I'll have a look.

just change the camera numbers.. This question have asked many times in ultimate shader pack thread.. also im using 6.6b

This question have asked many times in ultimate shader pack thread

Indeed it has - and elsewhere.

What problems are you having? U6.6b seems to work fine with shaders for me (but not the original U6.6 admittedly ). But I haven't done so much with shaders recently so I might have missed something.

Hey, it's mainly shaders that use external cameras which I have issues with. Before you say it, no I'm not stupid enough to use random camera numbers like 50, 86 they are all indexed sequential ones. For example EVOLVED's PS1.1 bloom shader has done me wonders in the past like in my Final Exodus project, I even made my code portable for any other projects but alas it doesn't work at all under 6.6b my screen is just black for some reason, as soon as the Render Target goes through the shader it just goes black. My trade off was to use EVOLVED's PS2.0 shader which I'm not so happy about as I'm basically sacrificing compatibility for this feature to work again. However even this shader returns very arbitrary results. With absolutely no change in code, or changing seemingly random lines of code the shader will either cause a Window Illegal Operation or it will run fine. I can even add a comment line and my shaders will suddenly break or I can add some other random thing and it may start working again.

This has nothing to do with my PC as I have twin PS3.0 capable cards and I often play games which use shaders, I've even played some of my other games that use this PS1.1 shader without issues.

For example EVOLVED's PS1.1 bloom shader has done me wonders in the past like in my Final Exodus project, I even made my code portable for any other projects but alas it doesn't work at all under 6.6b my screen is just black for some reason, as soon as the Render Target goes through the shader it just goes black.

I've just tried it using U6.6b and it works fine. I attach a screenshot.

Are we talking about the same shader? I'm using the demo from the July 2006 version of the Ultimate Shader Pack.

This has nothing to do with my PC

Maybe, maybe not. Could you zip up the PS1.1 demo you're using and post it so I can see what the problem is?

Well I just donwloaded the Ultimate Shader Pack Final and ran the '21 - Bloom [Evolved] [SM1.1]' without any code modification under 6.6b and get an illegal operation 'AppName: bloom.exe AppVer: 1.0.0.0 ModName: dbprobasic3ddebug.dll
ModVer: 1.0.0.0 Offset: 000144d0' However the HDR shader works.

Well I just donwloaded the Ultimate Shader Pack Final and ran the '21 - Bloom [Evolved] [SM1.1]' without any code modification under 6.6b and get an illegal operation 'AppName: bloom.exe AppVer: 1.0.0.0 ModName: dbprobasic3ddebug.dll

Weird - that seems to be exactly the same one I'm using. Could you check the dates on the "bloom.fx" and "bloom.dba" files as shown in the zip file? In mine they are both shown as 18/6/2006.

And what date have you got on your "dbprobasic3ddebug.dll" file? Mine shows 20/3/2007.

I have no idea what that error message means . Sounds like one for TGC.

Yes, my file dates are the exact same.

I usually get this kind of error when i changed some sahder code,if i do something wrong with any shader code i see this error.
@dark coder
I think the problem is in your bloom shader code.

I think you need help from someone who knows about the inner workings of DBP. Might be worth e-mailing Lee or Paul - they might spot the cause of the error message immediately. Or perhaps one of the moderators might be able to help, e.g. IanM?

I'm assuming you are using Windows XP...

No idea what to suggest otherwise - except possibly that your U6.6b is corrupt somehow.

@BandM

But he hasn't changed the code and it works fine for me.

I usually get this kind of error when i changed some sahder code,if i do something wrong with any shader code i see this error.
@dark coder
I think the problem is in your bloom shader code.

Well as stated above I only just extracted this shader from the original rar file, and as I have little to no experience with HLSL/ASM I wouldn't edit the files for anything bar filenames, so no the shader isn't the issue. Note I also said that this worked in a previous version(6.2 I believe) so the issue is likely DBP, I'll try reinstalling 6.6b as I may have somehow messed that up...


[EDIT] Yes I'm using Windows XP, also I have an nVidia card if that changes anything.

also I have an nVidia card if that changes anything

Unlikely. I'm using an nVidia GeForce FX 5200 card without problems.

Let's see what the re-install does.

I have no idea what DBP version I'm using now (6.3 I believe...) but if you change the camera numbers to 1,2 rather than 31,32 it should work fine.

but if you change the camera numbers to 1,2 rather than 31,32 it should work fine

Hmm? In my copy the cameras are 50, 51, etc and the demo works fine - exactly the same as if I number them 1, 2, ...

The plot thickens.