Renderware, Tokamak, Ogre3D, etc.. provide you with free trials.
Renderware requires you to mail in an application first, but I'd rather spend 3-4days waiting for an application reply rather than paying just to view what something is like.
Quote: "For what it's worth, I don't see any reason why DBpro users should expect DarkSDK as part of their Dbpro purchase (It's not an update). Although, I can certainly see their been room for a update plan for existing Dbpro owners, whom may not be very Basic orientated, but certainly not free."
Currently we're using DarkSDK 1.2 with DBP to create TPC DLLs.
That is what the help file calls the GlobStruct.h
I believe taking away a server they've provided free, for so long is taking the cake a lil. Also I could be wrong, but I believe before DBP was released we were promised the FREE ability to create extensions for the language.
I don't give a damn what the DarkSDK is used for outside of DBP or how much they charge for it.. but I don't think we should be charged to use it
FOR DBP.
On the other hand, I don't really care. Completed work on my .Net Control DLL version of the DBP Interface; if i need to create anything I'll use that instead. There's nothing illegal about using exposed engine functions within the bounderies of the DBP EULA.
Of course they might change this in later versions, but I'd see that as a little petty and vindictive.
[edit.post]
Quote: "If what IanM says is true, his interface library is not any breach of copyright."
IanM did not edit the DLLs, disassemble, etc.. He simply read the *publically exposed* Resource Table, and prototyped the functions into a Namespace Class.
Then when building the classes, allowed C++ to create the linker libraries.
With my C# Control Library, I've not even needed to create any 3rd Party Libraries or such.. it just accesses the functions directly.
Microsoft's EULA on Dynamic Link Libraries notes that you are allowed to use freely exposed functions. If TGC don't want them used then they should encrypt the Resource Table
