Author Topic: Now that jpct is Multi-threaded, Why Not Update the Software Renderer?  (Read 947 times)

Offline AGP

  • quad
  • ******
  • Posts: 1518
    • View Profile
Like shadows (maybe limited to a texture size of 512x512 or something)? Or how about a second texture stage, for environment mapping? The extra work could be unloaded on a thread of its own... The software renderer is really very important, for compatibility.

Offline EgonOlsen

  • Administrator
  • quad
  • *****
  • Posts: 11748
    • View Profile
    • http://www.jpct.net
The software renderer has a pretty low priority these days. Desktop jPCT has been surpassed by the Android version in terms of popularity and released projects anyway and the software renderer is being used even less. About second stage for environment mapping: You can already do that by doing setBlending(true); and assign a plain gray (128, 128, 128) bump map texture.

Offline AGP

  • quad
  • ******
  • Posts: 1518
    • View Profile
I'm sure that the Android version is more used than the desktop version, but that's no reason give the desktop version any less priority. Do we want desktops and laptops to be entirely replaced by tablets? And the software renderer is also very useful for quick prototyping, both for Android and desktop apps.

Offline EgonOlsen

  • Administrator
  • quad
  • *****
  • Posts: 11748
    • View Profile
    • http://www.jpct.net
but that's no reason give the desktop version any less priority.
But i somehow have to set priorities, or otherwise, this would be a full time job. Which wouldn't be that bad, but i can't find anybody who's willing to pay me for that... ;)

Offline AGP

  • quad
  • ******
  • Posts: 1518
    • View Profile
We talked about that via e-mail once. You told me that the reason you didn't do this professionally is the idea that it would become less fun for you. Do you still have the same job you had back then (some three years ago)?

And an argument can be made that just because you don't see published desktop projects, it doesn't mean they're not being made. Yet another would be to emphasize my point about easy of prototyping (even when a game is built specifically for Android it could still be getting started on the desktop--especially with the Android emulators being what they are).

Offline EgonOlsen

  • Administrator
  • quad
  • *****
  • Posts: 11748
    • View Profile
    • http://www.jpct.net
I see your points and i'm not arguing against them, but i just don't have the time to do all that. That's why i'm focussing on the features with the most benefit and the software renderer (as useful as it might be and as much as i like software rendering) doesn't belong to those IMHO. In fact, the hardware renderer is actually better suitable for creating an Android prototype, because it's more similar to jPCT-AE (not just feature- but also API-wise).
« Last Edit: June 10, 2013, 05:59:36 pm by EgonOlsen »