This performance issue needs to be addressed. They should be re-rendering the output in fixed intervals, not on the update, to avoid this kind of crash and ensure it is always running smoothly.
The new output window should not just be on par with the old one in terms of performance - we should be looking to improve performance. I believe there is still much more that can be done to improve the performance.
The “-Client” and “-Server” tags can be optionally turned off from the options menu.
They did it!
Let me tell you a funny story…
I was doing some testing and decided to print in the wrong place. It would print 1. 9 × 9 × 100 × 100 times.
Now that’s alot of prints. So naturally Roblox studio freezed and two seconds later I got my first blue screen of dead…
So I’m glad that my computer doesn’t have to die every time I’m stupid.
This is amazing. Thank you so much.
This made my week. I have some complex tables and sometimes visually viewing the table kills me inside so, this helps.
Fellow vsc user I see. Consolas is a nice font.
As much as I like what you’re trying to do.
I hate Roact, and you should not be using Roact for an output window
I think I’ll be sticking with the one that comes built into Studio because that wont nuke my computer the second I’m doing some logging
also this is the 1000th announcement post, thought I’d put that out there
There’s no Roact in the output window, it’s native Qt just like before.
I really really can’t wait for this to be smooth! It will make developing a lot easier!
Previously to print tables you could have used HttpService:JSONEncode() which would convert the entire table into a string to be printed. Though this new features make it look a lot cleaner and saves me time having to type that line everytime I want to print a table.
This is a minor problem, however the text indicator for the filtering textbox keeps blinking even after the window/widget is unfocused.
Anyway, this caused me confusion as I didn’t know whether I was editing a script or the text field before I began typing.
I would love if it instead of saying “… - Client/Server/Studio”, it would have a highlighted tag to the left of it 
I’ve been playing a little bit with the Expressive Output & RunService loops for a while, after and before the improvements and there is a little strange thing…
So when you repeatedly print the same message, the framerate starts going down but when you print different messages, there isn’t that much lag, I would dare to say that there is not even performance impact but that may really depend on the computer. So that’s a point that should be checked, otherwise the improvements are pretty good.
A million times yes!
My biggest happiness is printing tables!
Until now I either had to make 10 for in pairs loops or deal with just guessing if stuff is going my way as someone just learning the details of tables. This is going to be so helpful!
I do have a suggestion though…
I do not know exactly why, but some errors are able to be clicked and to redirect to the source and some are not. Maybe look into this in the future.
This is happening for me as well. I get a really bad framerate when printing repeat messages, when I hide the output window the lag goes away.
yo poggers this is sooooo helpful
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.