No I didnt its a random pic from the web. EDIT: Its always better to model everything and only use the texture/shaders for small details like bolts etc. and keep in mind polys do matter cause you cant predict how many objects are on screen at the same time in a multiplayer game like empires. Im maybee oldschool but performance > grafic in an multiplayer game. Empires is not a call of duty like corridor shooter where you have 100% controll of your budged. (Thats why emptys particles drain so much ) EDIT: Trickster do you still have a pic of my BE med lowpoly?
And every model will also have textures, which I have said twice now, will be the real bottleneck for low end cards. If you lower the tris count (although I believe this depends on how it is coded, but lets assume Source is nicely optimized) either less batches will be sent, or batches with less tris. The first could mean your GPU will be idle, and it could handle a lot more polies, or its wasting batches, where more tris could be sent with every batch. I've seen a few tests done on this, and Duke actually tested different texture sizes and amount. Back then I was using an older graphics card. Textures will be a bottleneck long before tris will be. Even if tris would ever become a problem, it's nowhere near noticable on the scale you're talking about. Lets assume you have 50 tanks on your screen + 50 players + 50 props + 10 turrets + 10 buildings + terrain. The individual model's average being around 20k tris. The total will be above 3 million. THIS IS AVERAGE, games from 5 years ago had this many polygons on screen at a time. It's not the polies anymore, it's all about shaders and textures.
I know tanks don't technically have a viewmodel, but if you define a viewmodel as a specific high poly model designed to be seen only by one player from a certain perspective, tanks quite easily could have a viewmodel. All you need to do is cut out all of the bits of tank that the player driving it would never see, hide the actual tank the player is driving from them (just as you do the player world model) and then render the stripped down high poly instead. As you won't be able to see most of the tank, you can cut out most of the polygons, such as the wheels and tracks, but you can keep the bits the player does see. Given the amount of on-screen space the tank takes, 10k polies or so is pretty efficient for a tank viewmodel.
you dont have to tell ME that i will have to build the highpolys anyway speak to a coder if you want viewmodel tanks
i added nearly all detail that was on the original to the tank i also added a kind of placeholder for a ML reload system but i will have to work it out first before continuing on that i also plan to something like this to the turret
Still looks like something we use now not a tank used in the future. Edit: Is everything on that pic highpoly cause I cant see rounded edges on the chassis and turret? The side of the turret has a very nasty smoothing group.
nothing on that pic is highpoly model although it got 10,680 tris now and yeah i need to fix that: badly stretched triangle anyways: ever looked on the rest of the art design of the mod? it doesnt really look very hyperfuturistic now does it? if im modeling for empires i got to keep that style, otherwise it would look really awkward but perhaps you can convince MOOtant of you becoming design lead (good luck with that) otherwise go play BF2142
for a really decent overhault youll need to build in playstations and monitor on the backseats. also dont forget some epic sound system in the trunk :D
Put the hatch lid back up vertically, all the tanks look better that way. I don't know why, but they just do.
i wont do that, because im fairly sure that most of us agree that they prefer beeing able too shoot in every direction instead of heaving a "better looking tank" ;P
Hey firewarrior nice work on the med there. I hope the APC is next in getting an overhaul (and a different model). Haiku?
