Sucks that FRAPS drains my FPS, so as a result the video is a bit choppy, but you get the idea =)
Video of the topic menu in action
🎉 Celebrating 25 Years of GameDev.net! 🎉
Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!
I would like to say this is /done/ but it is lacking the hit-testing element which will be coming next, either way i've got it displaying and animating.
Sucks that FRAPS drains my FPS, so as a result the video is a bit choppy, but you get the idea =)
Video of the topic menu in action
Sucks that FRAPS drains my FPS, so as a result the video is a bit choppy, but you get the idea =)
Video of the topic menu in action
Previous Entry
Documentation
Next Entry
w00t
Comments
Rob Loach
I love the music [wink]. The menus make the system seem more alive.
April 05, 2006 09:12 AM
not had a chance to watch the video, but the image looks like it's really coming together now [smile]
Keep up the good work!
Jack
Keep up the good work!
Jack
April 05, 2006 09:55 AM
Looks pretty neat despite being a bit choppy. I'm looking forward to seeing it in action.
Any idea yet how your framerates will compare in Project2 to Morning's Wrath? I'm curious because in high resolutions I got some severe graphics lag in MW. Since this looks to be mostly (all?) outside, you should have alot less overdraw causing slowdowns. (At least, I've assumed that was my problem.)
Any idea yet how your framerates will compare in Project2 to Morning's Wrath? I'm curious because in high resolutions I got some severe graphics lag in MW. Since this looks to be mostly (all?) outside, you should have alot less overdraw causing slowdowns. (At least, I've assumed that was my problem.)
April 05, 2006 10:44 AM
well comparing MW and Project2 is really an apples and oranges case.
Morning's Wrath used an engine that was developed with running on a 2D api in mind, it was later on that a 3D api was utilized to that we could have alpha blending. however the point at which the api could be integrated (the engine uses it's own api which was translated via DLLs to the real api) did not give us enough informat to do a really good job with the Morning's Wrath Direct3D adaptor.
for instance, with a 2D api it is VERY common to submit a number of 'blits' every frame randomly.
however since the 3D system had to emmulate this, vertex data could not be cached, thus dynamic vertex buffers were required which hurt performance a lot, that coupled with things like having to break large images up into smaller textures and do complex reconstruction really made it so that MW couldnt get the most out of the D3D API.
now Project2 and the S3Engine on the other hand are a different story.
while it will work /best/ with a SM2.0 card, it has been designed from the get-go with 3D hardware constraints.
currently we are seeing normaly 300 FPS in a large windowed mode.
(this /is/ on a 64bit athalon with a Radeon x800PRO)
and this is without any major optimizations, the difference is that the S3 engine system allows the majority of the work to be offloaded to the graphics card, which is the way 3D hardware likes things, Morning's Wrath tended to suffer from a restrictive API interface and the fact that it used 2D game techniques which didint transfer well.
Morning's Wrath used an engine that was developed with running on a 2D api in mind, it was later on that a 3D api was utilized to that we could have alpha blending. however the point at which the api could be integrated (the engine uses it's own api which was translated via DLLs to the real api) did not give us enough informat to do a really good job with the Morning's Wrath Direct3D adaptor.
for instance, with a 2D api it is VERY common to submit a number of 'blits' every frame randomly.
however since the 3D system had to emmulate this, vertex data could not be cached, thus dynamic vertex buffers were required which hurt performance a lot, that coupled with things like having to break large images up into smaller textures and do complex reconstruction really made it so that MW couldnt get the most out of the D3D API.
now Project2 and the S3Engine on the other hand are a different story.
while it will work /best/ with a SM2.0 card, it has been designed from the get-go with 3D hardware constraints.
currently we are seeing normaly 300 FPS in a large windowed mode.
(this /is/ on a 64bit athalon with a Radeon x800PRO)
and this is without any major optimizations, the difference is that the S3 engine system allows the majority of the work to be offloaded to the graphics card, which is the way 3D hardware likes things, Morning's Wrath tended to suffer from a restrictive API interface and the fact that it used 2D game techniques which didint transfer well.
April 05, 2006 03:05 PM
Looking very nice EDI..,
Don't use Fraps, Fraps is slow , give Gamecam a try, you will fall in love by it.
Don't use Fraps, Fraps is slow , give Gamecam a try, you will fall in love by it.
April 05, 2006 03:23 PM
Advertisement
Latest Entries
Whoa, it's dusty in here
2285 views
Porting Static:IT - C++ to HTML5
3566 views
What am I up to?
3119 views
96 Mill is now on Steam!
3382 views
First Youtube Review of 96 MILL
3587 views
First Youtube Review of 96 MILL
3578 views
96 MILL Released!
3283 views
96 Mill Nearing Completion
2893 views
Advertisement