Quote: "Listen, this may sound like some fool wining, but i think DBP isnt as good as one would think it was before buying it!For starters"
Isn't that a contradiction?
Quote: "For starters, there is no real easy way to do the levels,I mean if you use this so called amazing cshop, which by the way is more money added on to your game making pursuits"
I don't believe anyone one has ever called CShop amazing, and if they have they should be shot (no offense Josh
).
Personally I use
GTKRadiant, created ID Software, Enhanced by the community, covers over 16 Seperate Game BSP types and
FREE.
Quote: "then you find out it doesnt read the .x geometry into dbp properly,so you use a dll of sum1's then find out you need to buy another dll for collisions to work(more money!!)"
With the exception of sliding down stairs (a bug we've been assured will be corrected soon) BSP Collision works a treat, and is part of the built-in functionality.
This said the DirectX Collision is just as good if you use box collision and remember to make each side you want to use a seperate limb.
Quote: "I mean is it me or does sum1 else think its abit daft and dbp should of had these already?"
They are, just because something doesn't work exactly how you believe it should doesn't mean the function isn't working.
Quote: "Yes I know one could code these features or workarounds and such, but in my opinion thats advanced stuff and abit disheartening when you just purchased this amazing powerful but simple programming language(or thats what it says on the tin anyhow!!)"
What work-arounds? The manual clearly states and has examples for BSP Levels, if you need outdoors terrain then there are also examples for creating those types of levels too.
The examples and help weren't created just for the sheer hell of it, they are there for a reason.
