Jump to content

Leaderboard

Popular Content

Showing most liked content on 05/05/2015 in all areas

  1. Can't you make your own engine? that way you can code everything you need into it right from the get go? While we probably could, it makes no sence to sink hours upon hours into something like that. It would involve creating a whole rendering, animation, shader, asset, etc pipeline in addition to just game logic as well. You'd be better of taking an existing engine so you only need to take care of your game logic. Now that would only leave us (for C&C styled projects) with 2 choices; try to use the RenegadeX SDK that is build on an older engine version and doesn't properly fit the needed requirements, or use a brand new, blank slate and heavily customizable engine that you just need to build on top of and not hack together fixes to get the SDK to do what you want. Seems to me the choice would be rather obvious in that case. Of course, I'd say that if the SDK does exactly what you want/need, it'd still be a valid option, even if the engine is a generation old.
    1 like
  2. I'm going to openly state this....I know the public is excited about Renegade X showing off a few TSR assets in their last patch. I can also understand how this would spark an almost demand for a UDK TSR. But What the public isn't thinking about are the core issues with this idea. TSR has alot of units that have features that Renegade X never planned for. Underground units, Unit detection, Mechs, and Deploy-able vehicles are just a hand full of issues that we would be running into with the Renegade X SDK. One of the biggest issues that we currently have with the W3D engine is that everything has to be scripted in and a lot of what we want to do isn't possible because of that reason. With the Renegade X SDK we would have a lot of those same issues, on an already old engine. So why not spend the time coding our own code on a newer engine that other projects like AR, BFD, and other W3D Hub games can also benefit from? WE do have plans to upgrade engines and we know it's unrealistic to think that the W3D engine will last another 10 years or even be played. NOW please don't misunderstand what I'm saying, WE are not stopping work on the W3D engine, we will finish TSR W3D before adding TSR to a new engine and we would still support the TSR W3D. Also UDK isn't completely out of the question, we could very well have too many issues with a new engine and UDK could end up being the better choice. But wouldn't it be better to try to get TSR into an up to date engine, before settling for an older one. So I guess the real question here is "Would you rather have a brand new car for free ready to run straight off the showroom floor or get a used one that you have to repair and restore to even get it run?
    1 like
  3. So this is an old project of mine I started sometime around July 2012. It was sopposed to be a trading card game similar to modern ones. Detailed game mechanics never really got finalized and you can see from the included screenshots how some design details changed over time. The latest combat card version was the gray one, so all of the others are outdated. The first two images show the earlier versions, while the third image contains a preview of the newer combat card design. I had around 60 cards planned out in surprising detail, but I never got past the half way mark - only around 20 cards were fully made. I still have all of my project files so I might end up completing this sometime in the future, who knows? Though if I did start it up again I would definitely rebuild some things from the ground up since I've gotten better at this sort of thing over the past two years. Also, please note that I never had any intention of selling these, this was all done just for fun. So here, enjoy some of my old creations!
    1 like
×
×
  • Create New...