---

Hi Guys,

New DBPro upgrade available. The link is here:

http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta2.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta3.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta4.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta5.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta6.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta7.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta8.zip
http://files.thegamecreators.com/darkbasicprofessional/upgrade/dbpro_upgrade_7_0_beta9.zip

Changes log:

Upgrade 7.0
===========

Updater
-------

* Added additional dialog to ask for destination folder (multiple DBP installations)

Help
----

* Help files replaced with new help system that covers all previously 'undocumented' commands plus visual overhaul
* Tweaked many examples to align better with latest update, correcting small issues in the code (samples too fast)
* Added 91 missing examples to a range of commands across the board (feature creep)
* Added 49 more missing command documentations plus examples (GameFX module)
* Added media to GFX folder to solve missing help layout graphics
* Added missing parameter to MAKE OBJECT PLANE (MAKE OBJECT PLAIN)
* SET BLEND MAPPING explained better
* Added missing FLUSH LIGHT MAPS command in help
* Adjusted typical float descrioption value from 2.5 to 0.5 (for COS sense)
* Specified that HSIN, HCOS and HTAN must be specified as angles in degrees
* Fixed CALL DLL help pages to reflect correct parameter types
* Completely removed TEXTURE BACKDROP from help system (discontinued)
* Updated GET IMAGE with original texture flag description to avoid confusion
* Additional help information provided for CHECKLIST FOR OBJECT LIMBS
* COMPILE CSG removed from help files, command discontinued years ago
* Updated examples in two camera examples for UPDATE MATRIX addition
* Fixed typo in the command help LIMB VISIBLE
* Updated KEYWORDS with correction for MAKE OBJECT PLANE
* #INCLUDE and #CONSTANT renamed from _INCLUDE and _CONSTANT
* Updated LIMB EXIST and LIMB VISIBLE command pages

Compiler
--------

* Executables no longer create a SW_NORMAL window on the taskbar, using SW_HIDE instead
* NOTE: To run a DBP EXE in native Vista, ensure you copy in D3DX9_31.DLL

Matrix
------

* Randomize matrix is now truely random and not predictable on rerunning code

ConvX
-----

* Added support for DECLDATA field in newer X file exports (supports XYZ+NORMALS+UV+DIFFUSE only)
* Above addition helps support new exporter in Truespace 7.6 free version

Core
----

* Fixed bug causing frustrum not to calculate for cameras with FASTSYNC

Basic3D
-------

* Fixed culling of objects involving multiple cameras (frustrum planes calculated after vis check instead of before)
* Increased cap of bones allowed for shaders from 32 to 60 (new DBP shader limit)
* Added additional detection of excluded objects to speed up largr object use apps
* Duplicated MAKE OBJECT PLAIN with MAKE OBJECT PLANE to correct a very old typo
* Added extra object check at DrawObject call to ensure null-objects not drawn!
* Removed runtime error if try to FVF convert mesh with more than 65535 vertices
* Added missing parameter of Mode to MAKE OBJECT PLANE
* Fixed MAKE MESH FROM OBJECT so it once again converts strips to tri lists (fixed)

Camera
------

* Added Philips 2D+Depth support as stereoscopic mode 3 (requires special internal build of DBProSetupDebug.DLL (WOW build))
* Added new mode and parameter to SET CAMERA TO IMAGE : Mode 3 uses extra parameter to specify D3DFMT value for image

D3DFMT_UNKNOWN = 0,
D3DFMT_R8G8B8 = 20,
D3DFMT_A8R8G8B8 = 21,
D3DFMT_X8R8G8B8 = 22,
D3DFMT_R5G6B5 = 23,
D3DFMT_X1R5G5B5 = 24,
D3DFMT_A1R5G5B5 = 25,
D3DFMT_A4R4G4B4 = 26,
D3DFMT_R3G3B2 = 27,
D3DFMT_A8 = 28,
D3DFMT_A8R3G3B2 = 29,
D3DFMT_X4R4G4B4 = 30,
D3DFMT_A2B10G10R10 = 31,
D3DFMT_A8B8G8R8 = 32,
D3DFMT_X8B8G8R8 = 33,
D3DFMT_G16R16 = 34,
D3DFMT_A2R10G10B10 = 35,
D3DFMT_A16B16G16R16 = 36,
D3DFMT_A8P8 = 40,
D3DFMT_P8 = 41,
D3DFMT_L8 = 50,
D3DFMT_A8L8 = 51,
D3DFMT_A4L4 = 52,
D3DFMT_V8U8 = 60,
D3DFMT_L6V5U5 = 61,
D3DFMT_X8L8V8U8 = 62,
D3DFMT_Q8W8V8U8 = 63,
D3DFMT_V16U16 = 64,
D3DFMT_A2W10V10U10 = 67,
D3DFMT_D16_LOCKABLE = 70,
D3DFMT_D32 = 71,
D3DFMT_D15S1 = 73,
D3DFMT_D24S8 = 75,
D3DFMT_D24X8 = 77,
D3DFMT_D24X4S4 = 79,
D3DFMT_D16 = 80,
D3DFMT_D32F_LOCKABLE = 82,
D3DFMT_D24FS8 = 83,
D3DFMT_D32_LOCKABLE = 84,
D3DFMT_S8_LOCKABLE = 85,
D3DFMT_L16 = 81,
D3DFMT_VERTEXDATA = 100,
D3DFMT_INDEX16 = 101,
D3DFMT_INDEX32 = 102,
D3DFMT_Q16W16V16U16 = 110,
D3DFMT_R16F = 111,
D3DFMT_G16R16F = 112,
D3DFMT_A16B16G16R16F = 113,
D3DFMT_R32F = 114,
D3DFMT_G32R32F = 115,
D3DFMT_A32B32G32R32F = 116,
D3DFMT_CxV8U8 = 117,
D3DFMT_A1 = 118,
D3DFMT_BINARYBUFFER = 199,

* Added two new modes to SET CAMERA CLIP (3&4 same as 1&2 except they are for shaders)

Image
-----

* Corrected bug from U69 causing LOAD IMAGE to resort to zero-mipmap mode (BETA2 onwards)

Setup
-----

* Require special DBProSetupDebug.DLL (WOW build) alongside stereoscopic mode 3 usage

Bitmap
------

* SET CURRENT BITMAP now accepts a negative number, which specifies a camera target using the positive equivilant of the negative number.

If you find U70 breaks something that worked in U68/U69, let me know by emailing me at lee@thegamecreators.com

---

Is this the 7.0 discussed in the last newsletter?

"Many of the secret commands have proved to be reliable and useful, and so we have decided to overhaul the help system to include many of these commands for you to enjoy as an official part of the language. Watch out for these additions in Upgrade 7.0 of DarkBASIC Professional!"

---

And does it fix all the problems reported with U6.9?

---

Help files don`t appear to have changed - this cause its beta still? Commands(secret) seem to work though.

---

Excepts the bug causing objects to disappear when using many cameras (u6.9), everything seems to be OK for me.
This new parameter for Set Camera To Image is exactly what I need.

---

Agreed with Jeff and GG - I'm waiting for the "overhauled help system" as stated in the newsletter, waiting for the documentation on all the 7.0 commands and waiting for all the fixes reported in U6.9.

---

7.0 already, awesome
I'd like to pretend that 6.9 was never released.
mine still says 1.069, shouldnt be 1.070??
I cant wait till the disappearing objects are fixed.

---

Does it solve win-9x problems with DBPCOMPILER.EXE
(http://forum.thegamecreators.com/?m=forum_view&t=131700&b=15)
and DBProFileDebug.dll
(http://forum.thegamecreators.com/?m=forum_view&t=129158&b=15)?

---

What is this new parameter to SET CAMERA TO IMAGE?

---

Read the patch notes after you install it(in the DBP dir).

---

Wow! Thanks Lee You actually looked into my set camera to image request Im really glad.

Tho it may be that it isnt that what i think but im just guessing I must try it out.

First i need to install DBPro again because i formatted my computer to linux, and so far all dbpro apps ive tested have worked fine.

---

I keep getting Update Aborted: Could not detect Dark Basic Pro installation

Any ideas?

---

Something stupid on your part?

---

Perhaps installing DBP works?

---

You probably just copied the files, rather than install. I have done it in the past to restore it. You must add an entry into the registry, can't remember the exact path. The Codesurge thread talks about it a lot.

---

Tested... Still does not... :-(

---

What problems?

Most of the shader related problems people were reporting seem to come from the fact that you now have the make cameras in order.

ie. you can't make camera 30 unless you have made camera 1, 2, 3,..., 29.

---

huh? You cant have multiple cameras full stop as it culls all objects within them, apart from camera zero.

---

I must say that I tried to use a cube-map with 6 additional cams (and I changed the code so that there should be no cam-nr out of line):
0 = scene-cam
1-6= shader-cube-map-cam

And some of my objects get culled away as soon as I apply the shader to an object! So I think, that having all cams in "a row" doesn't solve the problem!

---

With regards to the camera culling bug, it still exists in 7.0 (even if cameras are made in sequence).

http://forum.thegamecreators.com/?m=forum_view&t=132061&b=15

---

Ok didn't know about that. What a stupid bug, that really needs to be fixed in 7.0

---

I am looking at buying Dark Basic professional, and I downloaded the free trial version. The program opens fine but when I try to compile and execute the the example program's or any other I get a window that says the compiler is not compatible with this version of DB pro. I tryed installing the latest update to DB Pro but got the same thing. Can you Make Executable's with the Trial version??? I am useing Windows Vista and Have the latest direct X updates and drivers. My Vista Op system has the latest updates. Regular FPS Creator runs perfect. I dont mean FPS X10 I dont have that yet. I realy want to use this Program can anyone help???????
If I did not Post this correctly please forgive it's my first time Posting. Please Help !!!!!!!

---

Crazy7, are you saying you tried to install this 7.0 beta update to the trial version and it didn't work?

---

thats not a bug you need to install direct x 9 oct 2006 or later(correct me if I'm wrong)the vista direct x 10 doesn't work as for bugs in the trial version its a trial if they fixed all the bugs they may as well release DBP for free

---

Whenever I use Advanced Terrain it always goes grainy for some odd reason, I've tried with a range of different textures etc. But I'm pretty sure it's nothing to do with the media.


That isn't anything to do with the compression of the screenshot, it's actually that grainy. Seriously though, it's like watching an old TV. And I think in the first one it made the sky go dark.

---

@The Wilderbeast

Have you tried changing the values to the diplay command as I seen that Lee has chaged it somewhat, so it might need some extra value add to it.

---

You need to generate mipmaps, use set object texture

---

In 6.9 and 7.0 you can experience the grainy look if you do not use the ",0" argument with the Load Image commands. The argument did not seem necessary before.

---

Okay, thanks for that Jeff, I'll give it a try.

---

Yay, my request for an extra parameter to set camera to image was actually done!

Thanks!!!

edit:
To those who don't know it means that if you use the extra parameter you can then use the image in external dlls like BlueGUI (eg. you can have a 3d image on a panel!)

---

Sorry to poop on your ride on but I'm pretty sure it was my request , and the command allows you to alter the render target surface format. Before it was fixed to X8R8G8B8 or A8R8G8B8(Lee previously stated this was a floating-point format which is why he added it I think), both of which aren't useful for things like depth mapping, so I suggested Lee add the ability to specify the exact format so we can set the surface to whatever we need, I posted the updated example that requires this feature here: http://forum.thegamecreators.com/?m=forum_view&t=91453&b=1&p=22. In this case I'm using the D3DFMT_R32F format, which allows me to render to a single 32bit texture, but it stores merely a single 32bit float, meaning camera depth in this case is preserved and I don't need any other channels as depth doesn't have any colours, and makes useful orthographic projection possible.

---

Hi Lee,
Any planed date for another beta for 7.0 upgrade ?

---

"Hi Lee,
Any planed date for another beta for 7.0 upgrade ?
"

I second that. Any chance of getting shadows working before the competition ends?

---

Does HELP-->About DBPro return 1.069 for the beta 7.0? It does for me.

---

Indeed it does

---

BETA2 now available. U70 is not going to be an all dancing all singing bug fixing romp on reported issues, just delivering what I mentioned in the newsletter and tackling the more annoying bugs introduced by mistake during U68/U69 work.

Check out the new help layout and additional command documentation. Post here if you want to see more details in any of the commands from the language. Pick three commands you would really like to see explored, rather than suggesting I just 'do all of them'. After all, there are now thousands of the little fellows!

---

Thats awesome! Thanks lee!

---

I just tried the latest and found 2 issues with it in my entry. I also noticed this issue occurs in one of my shader demos so you have an example(attached). Basically there is no linear interpolation on my shadow render targets, as you can see the demo works fine in 7.0b1(though you may need to uncomment the Set Object Radius ID, -1.0 lines there). And by fine I mean the penumbra is nice and smooth(well actually highly dithered but still smooth :p), under 7.0b2 my shadows use Nearest Neighbour sampling only, despite having specified linear for all 3 filters in the shader for every sampler as well as Set Object Filter ID, 2. You can clearly see the 4 samples from the shadow map overlapping, anyway so the difference should be obvious.

The second issue is that the frustum culling is only calculated for camera 0, all other cameras share its scene visibility. You can see this in the example if you look at an object that casts a shadow and slowly turn the camera(while looking at its shadow), as soon as the object leaves the screen the shadow vanishes, this shouldn't happen as the object is still in the view frustum of the shadow cameras which are the ones that basically cause the shadow to be cast.

---

I'd really like to see multiple render targets.

Also, I'd really like to be able to render transparent objects without the wierd artifacts around the edge. If I use transparency mode 4, the object will disappear into nothing if the camera gets too far away. Setting it to 2 will cause their to be an outline around the object. Either of these modes causes problems with shadow mapping. Leadwerks engine seems to be able to render transparent objects without problems(I'm looking at the vegitation on the terrain). I don't know how it works, but I'd like to see it in dbpro.

Edit: I just figured out the transparency problem. I knew that if I posted asking about it, I'd figure it out about 5 minutes later. I just tell the hlsl effect to sample the transparent object's texture with no filtering.

Texture = (Tex0);
MipFilter = NONE;
MinFilter = NONE;
MagFilter = NONE;

---

Lee, that's one heck of a lot of work been put into the help file like the new way of listing the demos, and the small demos on commands that just did not have anything before.

worth the wait.