Quote:

I dont know the memory-requirements of your game, nor the XBox Limitations.
I just want to point out, (If you knew that the game will also run on the X-Box at the beginning)
that before stuffing the levels and creating the content, there should be a strict guideline
for how big the content is allowed to grow.

The optimal choice is to use the limits out to the max, so that it still works, and
not overshoot the limits.
I also dont know, how hard it is to calculate the limits beforehand.
But the easiest way to to this, is to create a test-prototype and stuffing more and
more models, sounds, BSP and slow-loopfuntions into it, to see what the XBox can handle.
(the models can be just some random-highpoly stuff)
With this knowledge, you can estimate how much the game can handle good.
Also the XBox is a fixed system, with little surprises (in contrast to
the many different PC configs)

Given that other very nice looking games can be realized with the XBox,
I have to say, that a Fishing game can be realized for shure too.



The simple fact is that the game in its original design changed vastly. The publishing partners wanted more out of it than was shown at a point about a year ago, and they said they wanted more out of it. At that point, a port would have been pretty reasonable to the XBOX. After that point, the PC product had to be rolled up very quickly since it was already over it's projected completion date. The XBOX project was not addressed until PC was near to beta. It's a matter of time and person allocation. Being done for the size of budget that the game was, it needed to have the full team dedication on the PC product until it was at a further stage of completion. We also were limited to only one devkit for a number of months until we got two more to work with.

It's a matter of how things had to roll, and how we had to adapt with the publishers demands.

-Rhuarc

I no longer post on these forums, keep in touch with me via:
Linkedin.com
My MSDN blog