[Nico]

Originally posted by PhReAk
works in OpenGL
thats a nice model

thanks.
Raaaaah, now I have to get the damn exe to work, as my main complaint about the FS2 engine is gone!
Bob, you rule. Not only because you did it, but because you tried
everybody else said it was too much work, proof being they didn't even look into it, if it was just a lign to change.
you have my respect.

[Taristin]

Originally posted by Venom


Raaaaah, now I have to get the damn exe to work,

PLease, please, try not to use my name in vein... ;p

[vyper]

He has respect from most of teh community for this!  Been trying it out Bob, and I like to say HELL YEAH!

Note: I'd say 0.4~ is a good view .

[LAW ENFORCER]

Originally posted by Venom

Bob, you rule. Not only because you did it, but because you tried
everybody else said it was too much work, proof being they didn't even look into it, if it was just a lign to change.
you have my respect.

I was gonna say something like that... but didn't

anyway.... I remember people saying it would be serveral years before we saw any real changes. Arn't we glad they were wrong

SCP Forever (actualy... based on Duke Forever, thats a baaaaadddd name!)

[Bobboau]

actualy I think it was fryday who is the one who mentioned the beck buffer format thing, the reason I didn't do this a month ago (other than my computer not working quite right) was becase I figured it wouldn't be as stable due to the varius hard war configurations, and I wasn't sure I'd know how to fix them,
I am going to try removeing the format types that have a stencle component, but in the mean time make sure you have the correct registry settings (you should have a FS-open video entry thingy in there somewere (on the bottom I think))

or better yet try to figure this enigma out

[LAW ENFORCER]

Bob, do you want an Imperial gaurd?

I'll sign up to the Galactic Empire for gaurd duty!;7

[Unknown Target]

Ummm....this WILL get put into 3.6, right?

Oh, yea, could we also get the poly limits bumped up? That's MY complaint

[Bobboau]

I just updated the zip, it now trys only three formats a 32 bit one a 24 bit one and the old 16 bit one, as RTs post sugests that the stencle formats may be causeing crashes when it trys to see if they work

[Deepblue]

Hey venom did you get the partial transparecy on the cockpit by flpping the faces?

[Bobboau]

actualy he should change the higherarchy so that canopy comes after pilot and then retexture canopy with a seperate texture wiuth the string'-trans' in it, maybe make the object double sided with a darker texture on the outward faceing polys

so is it not crashing any more for the people that it was, or still not working?

[Flipside]

It seems to be a lot happier now, I think it was the updated clipping code that cleared the problem for me.

Flipside

[Nico]

deepblue:
yup

Originally posted by Bobboau
actualy he should change the higherarchy so that canopy comes after pilot and then retexture canopy with a seperate texture wiuth the string'-trans' in it, maybe make the object double sided with a darker texture on the outward faceing polys

so is it not crashing any more for the people that it was, or still not working?

well, I also have to flip the dashboard polys, they're inverted. when I did that plane, I wsn't aware of the trans tag.

I haven't tried the latest build yet, but trust me, I will ( d/ling the zip ).
If it works, I'll start my new project right away ( I can't sleep, damn heat ).

[Nico]

yeah, it works ( but only with the launcher )!
But I have horrible sound problems with it  ( the musics are "slow" and there's an awful lot of static, which disappears only when I click a button, during the loading time. That's odd.
How, it also makes the whole game run slower...
bah, anyway, the clipping thing worked.

as for the debug code, am I supposed to type www.freespace2.com during mission?

[Bobboau]

yes, but I just uploaded a () new version that has a comand line that will alow you to set it '-fov XX' so
"fs2_open_z.exe -fov .3"
will give you an in game FOV of .3 (wich for those of you havn't played with it will make everything look huge), to play with it in game type 'www.freespace2.com' to activate the debug code and hold down ~, alt, and ether - or + and it will change you're fov

[Fry_Day]

Bobbau, you need to take into account that NVIDIA cards can't do a Z-buffer with greater bit-depth than the framebuffer, so someone running in 16-bit can't get a 24-bit Z-buffer

On a non-related note, this 16MB Radeon Mobility is driving me nuts.

[Nico]

Originally posted by Bobboau
actualy he should change the higherarchy so that canopy comes after pilot and then retexture canopy with a seperate texture wiuth the string'-trans' in it, maybe make the object double sided with a darker texture on the outward faceing polys

so is it not crashing any more for the people that it was, or still not working?

how does that -trans tag works anyway? is it an opacity map ( black = 100% transparent, white=100 opacity, grey= inbetween )?

[Bobboau]

it makes a texture use additive alpha
but it uses the post lit values, so a polygon that is totaly un lit would be nearly 100% transparent even if the color of the texture was bright there
this isn't like glow maps, it is just something you put into a texture name so it is rendered diferent

[Bobboau]

I think the code would handle the Nvidia problem, but I'm not sure, someone with a nvidia card tell me if it's working for you.

[RandomTiger]

Put DX8 debug up to max and it breaks with this comment:

DepthStencil Format is not supported for this Adapter/DevType/AdapterFormat. This error can happen if the application has not successfully called CheckDeviceFormats on the specified Format prior to calling CheckDepthStencilMatch. The application is advised to call CheckDeviceFormats on this format first, because a success return from CheckDepthStencilMatch does not guarantee that the format is valid as a DepthStencil buffer for all possible cases i.e. D3DRTYPE_TEXTURE or D3DRTYPE_SURFACE or D3DRTYPE_CUBETEXTURE.

[RandomTiger]

Originally posted by RandomTiger
Put DX8 debug up to max and it breaks with this comment:

DepthStencil Format is not supported for this Adapter/DevType/AdapterFormat. This error can happen if the application has not successfully called CheckDeviceFormats on the specified Format prior to calling CheckDepthStencilMatch. The application is advised to call CheckDeviceFormats on this format first, because a success return from CheckDepthStencilMatch does not guarantee that the format is valid as a DepthStencil buffer for all possible cases i.e. D3DRTYPE_TEXTURE or D3DRTYPE_SURFACE or D3DRTYPE_CUBETEXTURE.

Nice work though