MS 3.5 Translucency does not render.

#1 It works fine for me.

#2 Yeah, that's why I'm not understanding it. Pure and clean build, doing the same thing the developer in the above link does, and the texture does not render whatsoever once that change is made. Do what he did to the "One" material, and post your system specifications.

I always end up with the extremely odd problems.

#3 I'll do exactly what that other guy did to prove this.


And for the materials.cs file:

new Material(light1)
{
   baseTex[0] = "light";
   emissive[0] = true;
   glow[0] = true;
   translucent = true;
   translucentBlendOp = 5;
 };

#4 What version of the DirectX SDK are you using, and what are your system specifications?

#5 No apology necessary, I thought your "hostility" was a poke at some fun. :)

Without antialiasing, my glow problems disappear, they look nice. Can't say the same about the jaggies. :P

However, the tranclucent invisibility remains, both in the box model, and in my own muzzle flash mesh, which did have the additive translucency flags checked on export. Still render inivisible, or with the image on a nice black square. (No translucency)

I'm using the DirectX April 2006 SDK.

#6 I'll switch to April 2006 and try.

#7 I appreciate it. (Edit wars, updated my last post too)

#8 Actually, I previously thought that all models and meshes, even the default ones, that I apply translucency to, render invisible. I applied the same translucency code to all sides of the test box, and only the CustomMaterial defined sides were visible and translucent as they should be. The rest were completely unrendered.

It appears only CustomMaterials work with translucency here; a regular "new Material" becomes invisible (Or, if I don't tell it what BlendOp, black)

Upload your TSE.exe and TSE.ilk file; I'll see if dropping yours in changes anything. Likewise, here's mine.

#9 @C2,

Offtopic, but why are you uploading the incremental link file? (:

#10 No, that tree example I posted was a new material, not a custom one. I'll upload my tree model. Try it and see if it works.

Tree Download

#11 @Stefan: Actually I thought the .ilk was necessary to run the .exe; I thought I remembered having some problem with it not working without it, and never thought again on the issue. Guess not. :)

@Matt: Tree's leaf textures show up black. (I know the screenshot is off my dirty build, but I also tried on a clean build to the same result) Upload your TSE.exe file, that way I can see if it is in fact, our different DirectX SDKs somehow having an issue here.

#12 Also off topic:
It looks like the character model is holding up his hand as if to say "WHY?" in frustration at the problem.

#13 Indeed.. haven't been able to port my first/third person weapon model yet in 3.5, a lot of code changed that I haven't understood yet. :)

#14 exe

Please note that there is no ILF in this.

#15 Tree still renders the same, even with your TSE.exe, in clean scripts.

#16 OK, I was able to repro this issue, the fix is checked in - fog wasn't being set up properly for translucent objects.

#17 My God, how happy I am to hear those words. Thanks.

#18 WOOOOOT!!!!

#19 Just wanted to say, (though your RenderTranslucentMgr fix isn't in yet; I'm not sure if that may fix it), translucency still does not render correctly if there's many translucent objects (like precipitation). If I rotate the view to view the player, the muzzle animation's full texture will render (including the black, which should be transparent), as seen in this age-old video that was posted on the TSE MS 3.5 release thread, and many other translucency threads I hijacked ;) . This problem appears on my translucent projectile, and translucent mesh flame that appears where bullets strike, if Precipitation or many translucent objects or particles exist in the scene.

This has been an issue ever since TSE began: translucency does not stay translucent sometimes. It's not a serious bug, but it does make things look like crap sometimes.

#20 @Brian:

On a similiar note, the shader cube in the demo is visible when the fog should hide it.
It does disappear when it reaches the visible distance, however.

I don't know if that's the same issue, just thought I'd throw it out here.