Printable View
Wo0o0ot! More progress :D
I have FINALLY managed to get an editable player start position built into the map files. Its just a camera object that stores the initial startup view. see the screeny...
Its a secure dialog, can be called with a single line of code and instantly returns a new camera object based on an old one you pass into it;
It can even do two at a time! that was something i never figured out how to do with the API and was planning on using directsound for it in future, i guess i won't have to with VS05 :)Quote:
Originally Posted by wossname
HAHAHA that's a classic! you should put that in your signature instead of the carpet thing! :lol:Quote:
Originally Posted by wossname
Lol, I like the carpet one better, but feel free to put it in yours though.
where do the paisley carpets fit into this?Quote:
Originally Posted by wossname
wØØsy:
Did you start on the input class at all? If not, I have a suggestion. Is it possible for you to make a static array with bools. And a static Enum that has simple names for the keys. Something like:
[Removed because of frustration]
Tell me if you didn't get it. And I can try to explain again. I think at least this is by far the simplest way to do it. And similar with the mouse. The upadte function can just update an X and an Y variable to tell how much it has moved. Then I can reach them since they are static. And it will also work exactly the same way as the camera...and that is a good thing..:)
If we can manage to pull that off today too, then we would be leet..:)
- ØØ -
Ehhh....looking back at all your screenies....have you ever tried to move the camera INTO the map? Or have you ALWAYS just had a negative Z? Can you please test with a positive Z as fast as you have the posibility on your copy, so I can see if it is I who have messed something up now, or if it has been like that all the time..
- ØØ -
Note, yes I've tried a positive Z and it crashed, but to be more precise if the camera is INSIDE the map then you will have something behind you...which is bad news and causes the game to crash. I think your BSP will fix this problem. Its perfectly ok to have the camera outside the map as long as all the wallparts are NOT behind you. I can't remember what happens if you stand to the north and look south at the map, i think its ok but I'll just check that tonight.
About your keyboard question, do you mean something like the GetKeyboardState() API function that returns an array holding all the keyboards status?
I can add that to the KeyTesterClass if you want, but it will be a byte array (i think) instead of bool, but i can put a bool accessor on it if that's any better.
Did you take a look at my KeyTester class in the codebank? It lets you test keys without neding a bool array at all. I supose with an array olding all the keyboard you can have as many keys down at a time as you like. I guess that's why you wanted it?
Tr333: If you can find me a paisley texture then it'll be in the next set of screenshots :
I think I found out what the problem is...and it does NOT look good...:(
Just look at the first picture here. It shows a screenshot from when you are inside the map. Not good, not good. Then I started thinking. And found out it is because we are not culling away stuff that is closer then the Near Plane. So I started to set the position for stuff that is closer then the Near Plane to (0,0,0). And then it looks like in picture number 2 there. As you can see much better. But still problems.....grrrr..this is so going to be a though one...I have no idea where to start...hmm..pen and paper I guess..:(
- ØØ -
First picture where?
****..:D...hehe..you where right...:D...grr....can you please do the rest of the app alone.:D..I am not sorthy (SP?)..:(...ok this culling method worked.Quote:
Originally Posted by wossname
[Removed because of frustration]
Quote:
Originally Posted by wossname
I don't want to get an array returned. I just want it to be an array in the background so I can ask with an enumtype if a specific key is down. Then it will work like DPlay..:)..and the same way as all my games and demos are workin..:)...totaly normal thing to do..:)
No, sorry, just saw there was something there...will have a look at it later on today if I have the time...Quote:
Originally Posted by wossname
Quote:
Originally Posted by wossname
Forgetabout it now..:D..it is working..:D
- ØØ -
Ok no problem, I'll add the array thingy now.
Quote:
Originally Posted by wossname
Sweet...I am SOOO looking forward to sync up with you tonight..and then be able to add some space partitioning code on friday to saterday...:D....we are the best..:D
BTW When did you become the leader for this project..:D
- ØØ -
No no no no no....we are just getting more and more troubles here you know...:(....just look here....guess who will say: "I said so"...:(
http://www.noteme.com/doomsharp/img/img044.jpg
- ØØ -
The roof tiles, the right-most row, the straight line on it looks a little bent.
Quote:
Originally Posted by Cade
That was my point..;)..and the same goes for the wall with the
_
_
_
_
_
on it too....++
- ØØ -
nice warpy look, DoomSharp() Psychodelic edition? :)
:lol: That texture problem is what I've been telling you since page 4. :lol:
It doesn't matter at the moment. We'll burn that bridge when we come to it.
So you now put the camera anywhere without it crashing?? :)
I've updated the KeyTester class as you asked...
http://www.vbforums.com/showpost.php...47&postcount=1
It supports Key toggling too so we can have a key turn something on or turn something off! That will be very handy for turning sound / enemies on or off during debugging.
Quote:
Originally Posted by wossname
Yeah, but it hasn't been visible like this since testing..this is just hillarious..:)
Quote:
Originally Posted by wossname
I hope YOU do...;)...ehehheheh
Nope...it is crashing on one of your cryptic lines..so I havn't looked into it yet...might get the time tomorrow...or later on tonight..but doubt that...Quote:
Originally Posted by wossname
Quote:
Originally Posted by wossname
Blimmey....you are my man...:)...I am still drawing circles and lines on paper....there is SOOO incredible much math behind this...you have NOOOO idea..:)
- ØØ -
kinda grows on ya ;)
Got my unsafe blitting code working at last. :D
Quote:
Originally Posted by NoteMe
Nan doesn't have to be division by zero. but the weird thing is that it is not in my code, but rather when I give it too you. I will try to dig into it though.
BTW that FPS is REALLY REALLY fast...I want to **** on my self..:) But why is it scewed? Are you working on that? When it is not looking like an 8 anymore, then I will kiss you and do everything you want me to do with you..:)
BTW ONE more big math Q here now, and then I think I am done with my HUGE lookuptable....:D..it is so nasty..it is so cool, it is...I mean...it HAS TO WORK..:)
- ØØ -
Did you look at the screeny here:
http://www.vbforums.com/attachment.p...id=40215&stc=1
its not like an 8 any more.
0xC0DE...
not too sure about the copyright on these images...
http://www.craigiestockwellcarpets.c...lliamsburg.jpg
http://karastan.com/images/Carpet_Im...64_cashmir.jpg
Quote:
Originally Posted by wossname
Yeah, but look here...the two vertical lines are not vertical...hence scewed..arn't they?
http://www.noteme.com/doomsharp/img/img045.jpg
Yeah that perfectly fine, it is a quad after all, no triangles involved here. The alg fits the texture into the 4 point polygon wherever the points are :D It'll look soooo sexy in the game.
That framerate was on a crappy computer and it was working with 24 bit pixels, we are working in 32bit premultiplied alpha pixels which are faster to blit anyway plus they are native ints, so i can use a single int pointer to transfer the pixels. Its going to burn rubber when we get it into the game. How exciting is this???.
Note, are we going to be able to have any occlusion culling later on, or is that already part of the BSP? (I still find BSP's hard to understand, I only just get the basic idea).
That skewing will happen anyway if our eyelevel is high and we are looking slightly downwards like this...
that image looks like you've "missed" pixels, due to rounding i guess?
BSP is out....It is BlackBox...I keep telling you..;)...you know what gets in, and you can see what gets out,....but you have NOOO idea how I do it..;)...and hopefully it will be ready on saterday before noon. That is my goal. So not today..:(...To much math left..:(
But about your drawing. Is the four points defined by you now? So you can actualy make it a perfect trapesium or what it is called? BTW care to send it to me, so we can really speed test it?
- ØØ -
Quote:
Originally Posted by Phill64
yeah, I guess that too, but first of all, it is possible to fix. Second, I don't think you will se it, in game if the "skybox" has more or les the same colour as the walls or at least a dark color since we have grey walls.
- ØØ -
Quote:
Originally Posted by wossname
Hehe..yeah, but the man is not a sky scraper though..:D
- ØØ -
the code is in post #583 ^^^.
Yeah you just pass in an array of 4 points plus the source and destination bitmaps and the rest is magic. DON'T use coordinates outside the destination bitmap area (no negatives and nothing greater than width or height) or it piss RAM all over the place.
The frame rate doesn't incluse the Device.Present() call so it fairly accurate. I don't think there are any restraints on the positions of the pixels so it will end up twisting, stretching, inverting or flipping the image any way you like.
OK saturday but NO LATER.
I told you I will bring my pillow to work tomorrow and then stay up all night untill it is finished..;)...I am going to this party later on on saterday, so if I am tired and so on I guess I will just get drunk faster..:)
BTW coords outside the window can be a problem...we have to work on that one..
*runs to test code*
- ØØ -
And the verdict is...
Debug mode:
92-102FPS
Retail mode:
102-112FPS
- ØØ -
Holy expletives batman!!!
Uhhhh which code are you testing there, yours or my blitting code?
Yours of course...I don't have any Blt code..:)..
- ØØ -
I though t you might be talking about your normal code while testing your Blax0rBox0r :D
Paisley PWNS j00 noobz...
No no no no...the BlaxBox won't improve framerate..remember the number of walls you have on the test map is nearly equal to the MAX walls you can have in a scene at any time...so I can't trim it much more then that..but what I can do is to make a map 3 times it size render nearly just as fast as this one...;)Quote:
Originally Posted by wossname
- ØØ -
BTW what do you think of my new dynamic signature...:)...it is just two test images now..I can't draw for ****...but they are changing every time you load a page with me on it..:)..and it has different text too. For now, only two different..but after a while..many..
DoomSharp();
- Will make you cry like a baby.
:D and its not even remotely optimised yet. This could be the answer to all our problems mate. We'll be billionaires!!! (In reps, if not in $$$).Quote:
Originally Posted by NoteMe
*thinking*
- Store textures as integer arrays instead, images in file get converted to array when the renderer loads them.
- Lock the destination bitmap once for the entire frame, locking/unlocking takes a millisecond or so.
- optimise the Trajectory class, its a bit flabby.
- 32bppPARGB pixels are much more efficiently handled by the CLR than 24BPP.
- ALL textures MUST be 32bppPARGB, this can be done upon game_load by the renderer. All original textures are to be freed up immediately after they have been converted to integer arrays to save RAM.
- cache all cachable variables in BlitQuad() and change the args to pointers where possible.
I know..I have sooo fate in you...I am not even sure what to say...I sooo love you...:D
- ØØ -