Yes, several, but they have not completely solved the issues seen with high-frequency print()s. We are committed to supporting this use case and will keep working on performance.
After pressing a few buttons in the consoles settings, you cant scale down the console less approximately 220 pixels. And ends up taking more space on the screen than before.
Also in the final version, i think we should have the option to change bewteen the expressive output, and the original one. As the expressive console can take up quite a bit of space for smaller screens
4 Likes
Iāve been using this for a while now. My biggest complaint right now is itās slow. I get major performance slowdowns whenever I need to output a lot of information, regardless of how complex the information is. Iāve gotta switch back to the old version for now because itās unusable for my current projects that require a lot of logging for the sake of debugging.
Outputting information should be a background task. It shouldnāt be causing framerate to drop.
Otherwise, I like where itās going. Being able to filter things is nice.
6 Likes
I strongly agree. It even runs in the background while disabled, which means when this is enabled fully I wonāt be able to make my own plugin that does the same thing but is much more optimised. Something really needs to be done about optimisation, it shouldāve been top priority.
Some suggestions (that Iām using for my own plugin I plan to make):
- All UI elements ever used created on initialisation, including icons
- A rendering system that only updates UI elements (by changing properties) which are in view of the scrolling frame, or closely outside
- Re-render at fixed intervals (e.g. 1/60 or 1/30), if there are any changes (not on message outputted - no one checks output hundreds of times a second)
- Donāt use Roact
1 Like
Any reason(s) for removing the columns? I find it harder to parse the output now. Now we have this weird middle ground between the old format (log mode, which seems to of been removed), and the new format.
The window appears to be a little broken nowā¦ Not sure if removing the columns was intentional but Iām disabling this for now since it leaves the output kinda messy. Iām sure this is gonna be fixed, but I just thought Iād post here.
Performance is also still a major issue, and these performance drawbacks are far too noticeable when the output fills up. Fingers are crossed that this particular issue is resolved before the output is out of beta.
I kind of like this new output window. However, my main problem with it is the excessive lag I get. I have a beefy computer, one capable of running some very powerful programs, and even I see upwards of 30fps lost simply because I decided to print some debugging info. I will not be using this feature for the foreseeable future, as the heavyweight, computationally intensive algorithms and scripts that I tend to run simply donāt function with this window.
1 Like
Todayās Studio release has a bunch of upgrades for the Expressive Output Window, most importantly fixes for all known performance issues! Details can be found here: [Beta Feature] Expressive Output Window Improvements
Give it a go and please let us know if any issues persist!
2 Likes
I was trying to manually set the PrimaryPart of a model and found that the Output Window canceled the action while navigating through it.
Not sure if this has been reported yet, but I found a formatting error for tables (amazing feature, btw):
As you can see above, the [5] part is being printed to the far right instead of in-line. Seems to be some discrepancy between a non-displayable empty table and a table with displayable contents.
When printing identical things in the output it stacks using the (x4023). However, as long as these are visible in the output window it will cause increasing lagg for each new print added.
The video below went from 60 heartbeats per second to 9, and back up to 60 when I cleared the output window of the identical prints. Since the video doesnāt load for me Iāll put a link to gyfcat just in case.
The base plate is by default a locked part.
Make sure the property Locked is unticked first.
Hello, thanks for your reply. I would like to clarify this issues has nothing to do with the baseplate. I have not clicked anything within the view. I clicked the PrimaryPart in the properties and tried to move my mouse to the model. The Output Window automatically deselects my action without any input on my end (besides moving my mouse towards the Model within the view).
I recreated the scenario again in the latest version of studio, so indeed this still exists. An error in the output would deselect the action the mouse is doing while navigating through it.
You can replicate this by creating a script and having error(āTestā), then hovering your mouse over it when you are trying to set the PrimaryPart.
1 Like
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.