TrueVision 3D 6.5 has been updated.

For those who don't know yet. Truevision3D 6.5 has been updated. They say that this is the final beta before the public alpha.

Some cool features have been added also. I guess we have to wait for Gabriel to update the wrapper.

Yep all appears to be up-to-date, including the GCC one.

Would be interested to see the wrapper updated.

Is this just the 3D module or the complete package ?

I've already updated the wrapper. I sent it out to everyone who has donated last night. So far, no one has reported any issues, so I'll probably release it to everyone else in a couple of days if no new bugs come to light or as soon as I've fixed any issues which do come to light.

Wow...4 years in the making... :p
I bet Max3d can beat its record....

I'm interested in your wrapper, I just need to confirm it's working with Bmax ok - been unable to run a demo so far. If so I'd definitely purchase (donate).

Is there any chance I can get a hold of the free version of the wrapper now, Gabriel?

I'm really eager to start messing with the new features using BMax.

I tried it with C# Express and I can't fault it in anyway. Plus with the C# IDE you get all that wonderfull intellisense which BLide and the standard MaxIDE lack.

Great job Gabriel!!

I am also interested in this (as you probably know)...

yeah I tried to get the free version from your site but the page is unavaiable

I haven't had any bug reports so far, but I did just find a small bug with TVPhysics->CreateConvexHull which I've now fixed. I've sent out an update containing the fix to those who have donated. Assuming no more problems show up, I'll upload it for everyone else tomorrow.

That's good to know.

@Amon (and Gabriel): Just to let you know that next BLIde update will have intellisense support for any non-open source module, including, obviously the free version of this wonderfull 3D engine wrapper.

That's great, thanks Ziggy. I didn't realize that intellisense wasn't available for closed-source modules before now. If I'd known, I would have found a way to generate some docs for people to use as a reference.

I'd like a Blitz3D wrapper.

There used to be one, but no one showed any interest, so the author ( Seyjahin? ) stopped working on it. I no longer use B3D, so I have no plans to make a B3D version.

That would be great, ziggy. That's the one thing that puts me off BLide. I need intellisense dude. :)

Any news on the free version? Wouldn't mind having a play with this over the weekend.

I'm experiencing a few odd things in my own project, so I don't want to do anything else until I'm sure it's not in the wrapper. I've actually managed to find a number of errors in obscure parts of the engine which ( apparently ) no one was using so it's certainly getting a thorough examination, but I still have some errors with actors not being rendered properly which I can't pin down. I'll keep at it until I'm sure everything's good and release then.

Ok, we're down to one remaining issue, which I'm almost certain is nothing to do with the wrapper. Still, if there's a chance of getting this fixed too, I'd like to try. Current plan is to upload either tonight or tomorrow morning depending on how things go. The good news is the wrapper should be better than ever as I've found a number of small, silly and obscure issues while trying to resolve all the problems.

The latest version is available now. I've solved all known issues with the wrapper, many unknown ( to anyone but me ) issues with the wrapper and a few ( previously ) unknown issues with TV3D itself.

Should be good to go now.

Thanks dude. :)

I'm a little worried with what you said about meshes not rendering properly with this update and I hope it's not one of them bugs that appears on 1 computer but not others.

I'll be buying the Pro version of the wrapper soon to show my support to you.

Nope, it's a problem with removing a shader from an actor. In short, don't do it. I assumed that removing a shader from an actor ( with SetShader(Null) ) would reapply the internal actot shader which TV uses to control actors. Currently, however, it does not. So if you absolutely have to remove a shader from an actor, reload the actor and don't apply the shader, because otherwise the actor's mesh goes a bit wonky.

Quite possibly this will be fixed in a future version, but I don't think it's really a big deal, and it's nothing to do with my wrapper in any case.

Nice - it all seems to be working well, thanks.

Gabriel - any ideas how to get Autolists working for TV3D commands in BLide?

I don't think I've used Autolists in Blide. Can you give me a quick idea of what they're for and what you'd like them to do? You don't mean the intellisense stuff that Ziggy mentioned earlier, do you? Autolists, I think, are something else?

Yes.. intellisense is what I mean.

I'm still learning TV3D - so I mean when you enter an object or function, it brings up the options - e.g.

CartoonShader.
- CreateFromEffectFile(string filename)
- CreateFromEffectString(string str)

etc.

As you'd get in C#/VS.net

I got confused looking through the options and some posts about BLide. I think autolists is for something else - no idea what though!

Well until Ziggy posted above, I didn't realize that Intellisense wasn't available, because I have intellisense. As I understand from what Ziggy wrote above, it's available only if you have the source ( which you don't with the free version, because I wanted to hold something back for people who donate ) but according to Ziggy, he can ( and plans to ) fix this so I don't think there's anything I can do in the meantime. If anyone knows otherwise, if there is anything I can do in the meantime, let me know.

Aha - I thought as much.

You should get an e-mail from Plimus :) Whether ziggy provides support or not for it, you've obviously put a lot of work into it - and I'm keen to support that. I'm assuming you'll keep it up to date until release, as it sounds like you're using it in a title?

Thanks, I've received the confirmation and sent you the source. Yes, I'm using TV in my own project. I will be keeping the module up to date up until and beyond the release, partly because I know people will expect it and partly because it will likely be useful for my own work.