Initial test results from current DBT v1.5.4 FB wrapper!

[crysstaafur]

In a triple side by side testing of:
Dabooda Turbo 1.4 in visual basic 6
Dabooda Turbo 1.5.4 in visual basic 6
and...
Dabooda Turbo 1.5.4 wrapper in FreeBASIC

here is how it all went down:

Test machine:
Duel Core 64-bit AMD Athlon at 1.9Ghz(each core)
ATI Radeon HD 2400
4 GB RAM
Windows 7 64-bit

Test program:
DBTutorial1, set to resizable window, maximized



Dabooda Turbo 1.4 -> 741 FPS
Dabooda Turbo 1.5.4 -> 744 FPS
and...
DBT v1.5.4 w in FB -> 860 FPS

I am sooo busting my tail to get this out there folks!!!!

Test #2. Same program. Results of CPU usage/Ram usage
DLL: Dabooda Turbo v.1.5.4 is the only test DLL.

Calibration(test machine idle with just FireFox running):
core#1:2.0%(averaged 10 times)
core#2:0.5%(averaged 10 times)
ram: 897/4094MB(averaged 10 times)

VB6 version of Tutorial1:
core#1:8.7%(averaged 10 times)
core#2:65.1%(averaged 10 times)
ram:928/4094MB(averaged 10 times)

FB version of Tutorial1:
core#1:5.9%(averaged 10 times)
core#2:45.3%(averaged 10 times)
ram:921/4094MB(averaged 10 times)




On a side note: If you want to run both 1.4 and 1.5.4 side by side
and use the FB wrapper, you can, but.....
You *must* install the 1.4 dll first!! then install the 1.5.4 dll second.
Otherwise the FB based exectubles will flip out royally.
I will be forward in that I haven't tried compiling an FB exe
while in the oh-o state, but I would surmise that FB will also
puke.

If you are in this jam, here is how to fix it!
Uninstall 1.4 first. This will purge the windows registry of all
1.4 entries. Then you *must* also uninstall 1.5.4 also.
This will wipe the registry clean of all dbt references completely.
(unless you've got yet another build..)
Then reinstall 1.4. Finally reinstall 1.5.4. In that order.

In short: you want DBT builds to be installed in the earliest
version build number to the lastest, otherwise FB functionality
will get seriously boned.

For example:
Let's say you have 1.3, 1.4, and 1.5.2beta installed. You then install
1.5.4 and freak out cause the FB example for 1.5.4 won't work. But
the 1.5.2 FB sample or even the 1.4 FB sample worked. You will
need to uninstall
uninstall 1.5.4
uninstall 1.5.2
uninstall 1.4
uninstall 1.3

Run a regcleaner program to kill off any abandoned references
just in case.

then install in this order:
install 1.3
install 1.4
install 1.5.2(why?!?, I'd just skip this step 1.5.2 is a buggy 1.5.4....)
install 1.5.4

I hope this helps anyone out there with this (or a simular) problem.
Oh did I mention that the installer that comes with 1.5.2 and 1.5.4
can be copied into the 1.3 or 1.4 folder, and once it's .ini file is
readjusted, you can use that to manage your dlls.

While I know that 1.4 comes with an installer, it's path behavior
only works on 32-bit systems prior to windows vista. The new one
will work on all flavors of windows, including 64-bit flavors!

I will keep on posting as things progress...

crysstaafur out...
_________________
There are 10 kinds of people, those who can read binary and those who can't.. ^_^

[crysstaafur]

After playing with the FB version of tutorial 1, I have found that
full screen will work, but you have to set it's resolution to a
standard mode (640x480,800x600,etc).

only technically the fb native inkey command will work and
display (however fleeting), but only if it's tutorial1 is compiled
as console rather than gui, and the console window must be
in front and active.. So if you need inkey functionality be
sure to use the dbinkey.dll instead....
_________________
There are 10 kinds of people, those who can read binary and those who can't.. ^_^

[Meneliki]

Heya Crystaffur..

Just found the latest release of Dabooda turbo. Noticed it includes network functionality. Is there any new documentation to show how it works? im running VB through visual studio 2008 express, so i cant open the project files(theyre in vb6).

Thanks

M

[crysstaafur]

I believe Sion's socket network module has documentation, therefore I suspect you are curious about the p2p class I wrote. Yeah, sorry about the lack of documentation I was at the time just trying to get a release out there.
The basic idea for the p2p class would be as follows..

initp2p (to start it up)
makebuffer (to make a buffer for data to be sent)

Somewhere further down your code...
have a section that passes data to the remote machine(s).
...
..
Stash(datatype)
stashbyte
stashlong
stashstring
senddata
....
...
..
have a section for receiving data from remote machine(s)
getmsgbyte
getmsglong
getmsgstring
getmsgdone(to alert dabooda turbo that you are done receiving messages)
...
..
.
When you close down your program, you can either deinit by
using cleanup and/or nullify the network object.


It's been ages since I've used that library. I am working on the last
tiny bit of the new peer2peer library. Proper documentation will be included. As far as I know it is unique in being the only directx p2p
library/wrapper that doesn't use any m$ template code.. in fact
there are no forms at all. The upside is that it allowed the dll to
be compiled with early binding rather than late bound in it's linkage.

The vb dll is done, I am merely tweaking it atm while simultaniously
building (and tweaking) the freebasic wrapper for it. If this isn't about
the p2p class, and your question was about the network sockets class,
you need to find a guy by the name of Sion.. He usually haunts the
gpwiki forum these days.
_________________
There are 10 kinds of people, those who can read binary and those who can't.. ^_^

[crysstaafur]

as far as reading the source files, there are a lot of ways to do this.
Open them in notepad.exe lol no really, you'll be fine..

open them in fbedit/fbide/notepad++/msdos edit.com/qbasic 8P

Or start a new project (com dll/active x dll) in vb net. simply add the
files in..

You might even look around to see if there is a quickie tool someone made to help import vb6 code into vb net.. just a thunk... or make one yourself..
shouldn't be too hard if you are comfortable with file i/o and string manipulation.. peace...


oh, wait...
remember, in the class inits of the main engine is the switch for debug mode.
if you want to check out the dbt internals while running a dbt app.

Also if you implement the inline console, be very very sure to place the dbinkey.dll inside the same folder as your project's exe file.


quick question, would you be interested in testing out dbt 1.5.7? One of the things I am trying to get working is a built in hotkey (as well as related methods) that would allow switching back and forth between windowed and fullscreen.. I'll start work on 1.5.7 when the holidays have come to pass and I am not as busy..

l8trz
_________________
There are 10 kinds of people, those who can read binary and those who can't.. ^_^