You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The debug console is the basis for a lot of useful information and I can already tell that I will incorporate it very well during the testing phase of my games but currently it is rather useless despite how much potential it has and how useful it could be. First, the information (most notably framerate) updates too slowly. I would prefer having a standard for the framerate to update once every second at least with the ability to change this (probably best to have it be in the debug console and for Armory to remember your decision the next time you run the game) so that you can make it update more or less frequently.
Secondly, the actual distribution of the information is a bit confusing. A single word with a colon to the right of it saying "Framerate" and then the updating framerate present to the right of it would be intuitive in giving me the useful information of what framerate it is currently while playing. The current setup gives me that plus two other numbers in parenthesis and a slash in between on top of that and another factor that says "gpu framerate" or something akin to that (I don't remember the specific I'm remembering from memory). The point I'm trying to make is that this system MAY provide me with more useful information but it doesn't tell me what that information is so I'm stuck having to guess and end up either missing some information that would have been useful for me or misinterpreting something which could get me in trouble due to inaccurate data measurements later on. Regardless, this (plus the rest of the debug console) should present itself in a fashion that is easier to interpret and tell what information is present.
Thank you for your time regarding this issue.
The text was updated successfully, but these errors were encountered:
luboslenco
changed the title
[OPTIMIZATION REQUEST]/[FEATURE REQUEST]: better debug console
Better debug console
Dec 9, 2016
Ya, will be nice to see it when it is in the state I described or better. Oh and as I referenced before with the other issue, making it so that you don't have to hover to update the console would be great. Keep up the great work though.
The debug console is the basis for a lot of useful information and I can already tell that I will incorporate it very well during the testing phase of my games but currently it is rather useless despite how much potential it has and how useful it could be. First, the information (most notably framerate) updates too slowly. I would prefer having a standard for the framerate to update once every second at least with the ability to change this (probably best to have it be in the debug console and for Armory to remember your decision the next time you run the game) so that you can make it update more or less frequently.
Secondly, the actual distribution of the information is a bit confusing. A single word with a colon to the right of it saying "Framerate" and then the updating framerate present to the right of it would be intuitive in giving me the useful information of what framerate it is currently while playing. The current setup gives me that plus two other numbers in parenthesis and a slash in between on top of that and another factor that says "gpu framerate" or something akin to that (I don't remember the specific I'm remembering from memory). The point I'm trying to make is that this system MAY provide me with more useful information but it doesn't tell me what that information is so I'm stuck having to guess and end up either missing some information that would have been useful for me or misinterpreting something which could get me in trouble due to inaccurate data measurements later on. Regardless, this (plus the rest of the debug console) should present itself in a fashion that is easier to interpret and tell what information is present.
Thank you for your time regarding this issue.
The text was updated successfully, but these errors were encountered: