I'm having to write a new hardware instancing shader to replicate the meshes, as once I hit about 1,000 trees, my frame-rates drag down to the depths of hell.
I'm working to get them integrated before moving on to clouds. Last night I went out and purchased some low-poly 3D models to use - trees and ground clutter mostly, a couple of buildings. Everyone who works for me is an avid gamer, so it's not like I'm facing any serious resistance when I say "maybe we should try our hand making games." The guys at work are cutting me slack this week so I can spend some extra time exploring this unexpected change in direction. Wait until I have clouds done and a proper horizon w/ skybox.
My VP said "I looked at that damn water for a half hour!" He asked me to upload a youtube video so he could see it move. Things changed recently when I sent him the last screenshot last night. But, I checkpointed the app at that point in time so I'd have something to review if I ever wanted a space combat starting point. I shot that image to off to work last weekend, and my VP said "yeah. I tossed some fighter models on it and had just finished working out the cell selection math - still didn't have my camera model completed so moving around was. Hard to believe just 9 days ago (5 of which I didn't do anything with the engine, as I was working my real jobs) I had just finished the first non-textured wireframe version. difficult rules set to chew up and spit out.
Inevitably though, that'd lead in to vehicles, which would put me back at point A. I was a big fan of xCOM way back when, and would like to do something squad level along those lines some day. I could also go another route entirely and get more intimate with a ToW - just picked it up last week and finished reading through it. I do have SO though, so perhaps time to learn? I haven't played BF yet, don't know if I'd be the right person to make it.
0 kommentar(er)
