Quote:
Originally Posted by
Cimi
@Simon:
Few Questions (I'm not forcing you to another update :) I'm just asking for your opinions on what can be done in the future):
Cool, no problem. I might come back to Quake/Quake2 in a couple of months. At the moment I'm really enjoying not programming at home! (I program games for a living, so its nice not programming 24hrs a day)
Quote:
1) Is there a change to improve the rendering, gaining more framerate?
Yes, totally. There was a lot of work that I could have done (taking months) but I thought that it was more important to get a release out rather than dragging it out forever.
Quote:
2) Is there a change to avoid the problem of the *white texture*, I mean improving the memory management or making the engine lighter...
Not really. Could be a way to not flash white when you shoot a bad guy though.
Quote:
3) New features (wifi, but do it will reduce the amount of ram available? Like in yours Quake1 build without Exram)?
Yes there are lots of things that I want to get in (I stuck a big list in a post a few pages back)
Not sure how it's going to work with the whole "RAM thing". We'll reach the bridge when we get to it. I want to avoid separate builds, though.
Quote:
4) If I will take a look at the code, which parts you think will need some work on, and which of them you're written well?
I know of some crap bits, but it's really just a case of moving those optimised bits from QDS into Q2DS...
If anything was to be re-done, it'd be some of the levels. 'security.bsp' is a particular good example. Some levels are just massively CPU intensive for no reason.