Jump to content
WilliamTheConqueror

What I think needs to be said about the new renderer.

Recommended Posts

People yell that they want to now where it is. Hicks talks about needing to code out the legacy renderer, yet people keep asking. I have a solution. Why don't the devs just talk about what files are left for removal of the old renderer, and which parts are done. Not a list of each and every file, but more in general. Maybe even a percentage of files left. Brian, I think what people really want is to know exactly how much progress it will take for the renderer and new engine. Any news about the possibility of me getting more than 5 frames a second is good news.

Share this post


Link to post
Share on other sites

Did you read the latest status report? https://forums.dayzgame.com/index.php?/topic/228936-status-report-15-sept-15/

 

 

For 0.59, and 0.60 both - we're looking at a good amount of engine work being merged into the main branch. Part of this work includes the beginning of basic QA passes against portions of the new renderer. This is internally only, but requires some DLL changes to be present in the main distribution, so don't get to worked up if you see some DLL's referencing Enfusion, or Direct X 11. Past the programmers merging these engine changes in, they still need to be properly configured within the areas of the title that use them by the design team, tested by QA, bugfixed, regression testing, and so on. So don't expect massive changes all at once (a general good approach to the whole of Early Access, in general)

 

 

I do not think there is a whole lot more useful info for the public that they need to share at this time.

 

Maybe when the renderer hits experimental they might tell us more about whats happening but they usually just throw the build up and see what breaks.

Share this post


Link to post
Share on other sites

Did you read the latest status report? https://forums.dayzgame.com/index.php?/topic/228936-status-report-15-sept-15/

 

 

 

I do not think there is a whole lot more useful info for the public that they need to share at this time.

 

Maybe when the renderer hits experimental they might tell us more about whats happening but they usually just throw the build up and see what breaks.

 

I missed this status report. Thank you. This is the stuff I am talking about. I just hope that they get into detail like this more often.

Share this post


Link to post
Share on other sites

People yell that they want to now where it is. Hicks talks about needing to code out the legacy renderer, yet people keep asking. I have a solution. Why don't the devs just talk about what files are left for removal of the old renderer, and which parts are done. Not a list of each and every file, but more in general. Maybe even a percentage of files left. Brian, I think what people really want is to know exactly how much progress it will take for the renderer and new engine. Any news about the possibility of me getting more than 5 frames a second is good news.

erm, when programming, you don't exactly switch out "file for file" when refactoring a projects code, thats not how it works

 

of course they could post something like "CheckVisibleHandler.c/.java" has been redone and implemented wtith the functions/methods of the new renderer Class, but that wouldn't tell you anything, take time away from people actually working on important things, and just rub the communities impatient belly... which has no value whatsoever

  • Like 3

Share this post


Link to post
Share on other sites

erm, when programming, you don't exactly switch out "file for file" when refactoring a projects code, thats not how it works

 

of course they could post something like "CheckVisibleHandler.c/.java" has been redone and implemented wtith the functions/methods of the new renderer Class, but that wouldn't tell you anything, take time away from people actually working on important things, and just rub the communities impatient belly... which has no value whatsoever

That and the names of the files and the entire architecture can change. The current house may have a living room, kitchen, bedroom, bathroom, and garage. The updated house (renderer) may have an open concept single room for the kitchen and living space, a full bath and a half bath, a master bedroom, and guest bedroom, and a car port. Or said another way, what's there now and what will be there when they've refactored it may be entirely different in form and function.

Share this post


Link to post
Share on other sites

Personally, I think the dev team has given us more information, reasoning, and updates than they need to. Especially during the last couple stable updates. So beans to them. 

  • Like 1

Share this post


Link to post
Share on other sites

erm, when programming, you don't exactly switch out "file for file" when refactoring a projects code, thats not how it works

 

of course they could post something like "CheckVisibleHandler.c/.java" has been redone and implemented wtith the functions/methods of the new renderer Class, but that wouldn't tell you anything, take time away from people actually working on important things, and just rub the communities impatient belly... which has no value whatsoever

I see the reason in your argument, but that is why they have a community guy to put together the status reports, right. They don't make the programmers do that. I am not asking for a file by file list. I just want them to talk about what they have done with the new engine in every status report. Stuff like, "We've been working on ______ lately, and ________ is making progress." This is a generalization, but they should have more info like this.

Share this post


Link to post
Share on other sites

Every report would read "We've been working on __the engine____ lately, and __the engine______ is making progress."

People have a hard enough time grasping the concept of different departments working of different area let alone understanding specific modules of the engine.

Also it's unlikely that only one or two parts are being worked on so would you like them to list every single module that is being altered on some level?

Edited by stinkenheim

Share this post


Link to post
Share on other sites

Every report would read "We've been working on __the engine____ lately, and __the engine______ is making progress."

People have a hard enough time grasping the concept of different departments working of different area let alone understanding specific modules of the engine.

Also it's unlikely that only one or two parts are being worked on so would you like them to list every single module that is being altered on some level?

 

They wouldn't need to put all the small parts that they are working on. Things can be generalized. If they are working on grass, trees, water, buildings, etc. they could just say Enviroment. Infected and animals = AI. Weapons, food, clothes = Items. ETC. I think the lack of understanding of what the engine really is and why it needs so much work is because all we have is it takes a lot of work to code out the legacy renderer. I just would like to know what is currently being worked on, and what needs to be done. Not out of impatience, but out of curiosity of the progress of the game I supported in it's early stage of development. Reading the newest status report, I realize it may be sooner than I originally thought. This kind of detail may not be necessary very soon.

Share this post


Link to post
Share on other sites

I think the lack of understanding of what the engine really is and why it needs so much work is because all we have is it takes a lot of work to code out the legacy renderer.

 

 

No, your and almost every other players lack of understanding comes from not being a programmer. Me and you, we both have no clue what it takes to develop a renderer, what components it has and how much work needs to be put into it. Your post is a perfect example for that, because all the things you've mentioned have nothing to do with the renderer.

 

So even if they told what they are working on it probably wouldnt help you in understanding how far the progress is. Do you even know what a legacy renderer is?

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×