Ultimate 3D 2.1.1 - A new fixed DLL

We hope you enjoy your visit.

You're currently viewing the Ultimate 3D Community as a guest. This means that you can only read posts, but can not create posts or topics by yourself. To be able to post you need to register. Then you can participate in the community active and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free.

Join our community!

If you are already a member please log in to your account to access all of our features:

Pages:
1
2
3

Ultimate 3D 2.1.1 - A new fixed DLL; Fixes all known bugs, no new features
Topic Started: Jan 3 2009, 02:54 AM (1,886 Views)
Dr. Best	Jan 3 2009, 02:54 AM Post #1
Administrator Posts: 3,588 Group: Admin Member #1 Joined: March 16, 2005	Hi everybody, as announced before I have been working on a new fixed version of Ultimate 3D. Over the past few month there have been several bug reports and most of them could be verified as real bugs. I am sorry that it took me that long to fix them, but I have been really busy and fixing the bugs caused quite a bit of work since some of them had really tricky causes. By now the old Ultimate3D.dll has been replaced by a new one in all official downloads on Ultimate3D.org. Additionally you can get the fixed DLL here. Its installation couldn't be any easier. Download it and replace the old DLL by this new one. This fixed DLL is referred to as Ultimate 3D 2.1.1. Here is a list of all bugs, which are fixed in it: With the old DLL stencil shadows start about 28 units away from the model, if a model with vertex skinning casts shadows for a directional light (reported by skarik). If a terrain tile uses four diffuse maps parts of it, which should be solid, become transparent (reported by skarik). Parts of text and 2D graphics are missing randomly, if user defined clipping planes are used. If a .md2 file got exported to a .u3d file the texture coordinates were exported wrongly (reported by nic_rf). Two mistakes in the documentation have been fixed (reported by MysteriXYZ). There are no new features in this new version. Another issue, which has been reported turned out to be caused by a problem in some graphics device drivers. To avoid this problem avoid using the def instruction in pixel shaders. Otherwise the constants may not be set correctly. With friendly regards, Dr. Best



luenardi	Jan 3 2009, 10:47 AM Post #2
LEVEL 50 FIREFLY Posts: 1,409 Group: Members Member #930 Joined: December 29, 2007	Thanx dude! your just too awesome.
	Better! Faster! Stronger! -_/The Coded One is coming!\_- Blink.............. and youll miss it! saving cap Still known as luenardi.


Huika	Feb 3 2009, 07:11 PM Post #3
Advanced Member Posts: 45 Group: Members Member #2,950 Joined: January 14, 2009	Thank you Dr. Best! = ))) Ultimate 3d is really great! I´ve tested many engines like panda3d and ogre3d, but i´ve got really impressed with the simple way it is to work with ultimate 3d. Since i´m a designer and not a programmer, this is my big chance of creating 3d games :)



ashrat3000	Feb 4 2009, 01:07 AM Post #4
u3d raytracer Posts: 1,578 Group: Members Member #379 Joined: September 2, 2007	Wait did this fix the multiple motion blur shaders issue? And the PSS issue where the screen would move 1 pixel to the right and down. Or were those already fixed... Or is the def causing those problems. offtopic: Why can't I get the motion blur shader to affect a different camera? camera_index isn't changing anything. Edited by ashrat3000, Feb 4 2009, 01:08 AM.
	그대를 사랑해


Synexn-Prime	Feb 4 2009, 01:49 AM Post #5
Sierra Prime GF32 : Unit 7 Posts: 5,103 Group: Members Member #94 Joined: October 5, 2006	ashrat3000 Feb 4 2009, 01:07 AM Wait did this fix the multiple motion blur shaders issue? And the PSS issue where the screen would move 1 pixel to the right and down. Or were those already fixed... Or is the def causing those problems. offtopic: Why can't I get the motion blur shader to affect a different camera? camera_index isn't changing anything. 1. Those were fixed. 2. Def is causing the problems in the current version. offtopic: Probably because you have it in the wrong order.
	Synexn-Prime, the Bigger Sister. Prepare to watch her fly. Watch that tear shatter the steel. 2012. Current Stone: Water : Prepare to help her survive. June 2010. formerly known as skarik


ashrat3000	Feb 4 2009, 04:40 AM Post #6
u3d raytracer Posts: 1,578 Group: Members Member #379 Joined: September 2, 2007	skarik Feb 4 2009, 01:49 AM ashrat3000 Feb 4 2009, 01:07 AM Wait did this fix the multiple motion blur shaders issue? And the PSS issue where the screen would move 1 pixel to the right and down. Or were those already fixed... Or is the def causing those problems. offtopic: Why can't I get the motion blur shader to affect a different camera? camera_index isn't changing anything. 1. Those were fixed. 2. Def is causing the problems in the current version. offtopic: Probably because you have it in the wrong order. Huh. I must still be using 2.1.0. offtopic: What? Edited by ashrat3000, Feb 4 2009, 04:40 AM.
	그대를 사랑해


Synexn-Prime	Feb 4 2009, 04:49 AM Post #7
Sierra Prime GF32 : Unit 7 Posts: 5,103 Group: Members Member #94 Joined: October 5, 2006	One must realize that a post screen shader is just like any other object, giving GM an unchangeable u3d_index variable, and if one changes changeable properties after creation, that in order to apply these changes, one must update the engine with the changed value of the property before you may see any change in your object, isn't that right?
	Synexn-Prime, the Bigger Sister. Prepare to watch her fly. Watch that tear shatter the steel. 2012. Current Stone: Water : Prepare to help her survive. June 2010. formerly known as skarik


noone	Feb 5 2009, 07:35 PM Post #8
Member Posts: 21 Group: Members Member #2,944 Joined: January 5, 2009	I have some problems with the DLL. I've downloaded the new DLL, replaced the old. It can't define three functions: GetDistanceToTerrain,GetDistanceToModel and GetDistanceToTerrain. ( Please ignore the attached picture, when I attached it, i didn't know, that I won't need it ) Attached to this post: U3D211.jpg (40.26 KB)



Dr. Best	Feb 5 2009, 07:57 PM Post #9
Administrator Posts: 3,588 Group: Admin Member #1 Joined: March 16, 2005	You have been using Ultimate 3D 2.0 before updating. Updating from Ultimate 3D 2.0 to Ultimate 3D 2.1 requires some changes in your code. Here is the detailed description on how to update.



noone	Feb 5 2009, 08:40 PM Post #10
Member Posts: 21 Group: Members Member #2,944 Joined: January 5, 2009	Thank you!( And sorry for don't looking at that ) Whoa, like the new features!



Andrew75	Feb 7 2009, 04:21 PM Post #11
Andrew75 Posts: 777 Group: Members Member #304 Joined: July 22, 2007	wow its amazing you could find the time for this update Dr Best, howd you squeeze it in? its good to see that you still support the old 2 series of ult 3d. ^__^
	(SONIC CD REMIX) check out my vids http://www.youtube.com/profile?user=tuxmask75 Check out our projects vids http://www.youtube.com/profile?user=AXSXProject


Dr. Best	Feb 7 2009, 07:17 PM Post #12
Administrator Posts: 3,588 Group: Admin Member #1 Joined: March 16, 2005	Andrew75 Feb 7 2009, 04:21 PM wow its amazing you could find the time for this update Dr Best, howd you squeeze it in? its good to see that you still support the old 2 series of ult 3d. ^__^ I did it during the holidays .



Ormick	Feb 23 2009, 05:12 AM Post #13
Advanced Member Posts: 79 Group: Members Member #2,904 Joined: October 26, 2008	Glad I decided to visit here before I went back to U3D. I've been working with GM2D for 3 months now, and the limitations are just pissing me off. But I learned alot with that, and now I'm ready to get back in the game. And Huika, I know how you feel about being a designer and not a programmer. Edited by Ormick, Feb 23 2009, 05:13 AM.
	Every forum needs an indecisive noob. I'm it.


Gandalf20000	Sep 5 2009, 05:26 PM Post #14
DirectX Newbie Posts: 2,186 Group: Members Member #1,724 Joined: March 4, 2008	I'm posting this here, since I don't think it warranted it's own topic, and this is the topic about U3D 2.1.1, so... I think I might have found a possible bug. With SetMaterialStageTexCoord(), the manual says that if you set the coordinate set argument to -3, it uses the vertex positions on screen as texture coordinates. Here's the problem: it does that, but the texture repeats (a lot) within the view frustum. It shouldn't be doing that, since (to my understanding) it is supposed to be using the vertex positions in relation to the view frustum as coordinates. In other words, shouldn't the projected texture fill up the entire frustum of the camera?
	A website about my dad's books


Dr. Best	Sep 5 2009, 05:37 PM Post #15
Administrator Posts: 3,588 Group: Admin Member #1 Joined: March 16, 2005	Gandalf20000 Sep 5 2009, 05:26 PM I think I might have found a possible bug. With SetMaterialStageTexCoord(), the manual says that if you set the coordinate set argument to -3, it uses the vertex positions on screen as texture coordinates. Here's the problem: it does that, but the texture repeats (a lot) within the view frustum. It shouldn't be doing that, since (to my understanding) it is supposed to be using the vertex positions in relation to the view frustum as coordinates. In other words, shouldn't the projected texture fill up the entire frustum of the camera? Well, this is a matter of definitions, but I know about this behavior and I never intended to change it. You can use a simple vertex shader, if you need it different. This feature is never that useful anyway, since screen space texture coordinates need to be computed per pixel and not per vertex to avoid distortions. Examples for shaders, which do this are the portal shader and the water shader. Basically the only reason, why this feature is available, is because it is an easily accessible feature of the pipeline of Direct3D.


Go to Next Page
« Previous Topic · Announcements · Next Topic »

Pages:
1
2
3