Studio testing takes a long time to stop without errors or warnings

This has always happened to me, every computer I use
Started in early 2019

2 Likes

Thatā€™s interesting about FastCast, I had been experiencing this issue in some of my games but not all.

So I went in and found that the games having the issue did indeed have FastCast module so I removed that module and the issue is GONE!

@chippermonky I think this issue is related to the Luau type checking included in FastCast module, but while the owner of that module should indeed look into why it might be causing this, perhaps on Robloxā€™s end you guys could do a little looking into it as well.

@EtiTheSpirit You might want to look into this as well, it seems several of us have had this issue and when we removed FastCast, it resolves it for us.

2 Likes

This is something out of my jurisdiction completely, as far as the core concept of the script goes. Itā€™s not impossible, however. Itā€™s only a violation of the standards the script wants to follow.

If I want to completely nuke standards - and this is a solution you could implement yourself too - I could change the --!strict at the head of the script to --!nonstrict or even --!nocheck (though nonstrict should be more than enough) and it would likely fix the problem. I do not have the capability to test this right now, and unfortunately cannot relay any results to you. This is a known fix for other type checker related problems however, so I have some score of confidence that it will work.

I will be honest with you, I am not happy with FC in its current state and plan to rewrite the entire module from scratch in the coming weeks. This should address some of the foolish mistakes Iā€™ve made (there are a couple) and fix some of the bloat the module has acquired over its lifetime.

3 Likes

Hey! By no means was I pointing a finger at you and the FastCast module. Though this is an issue that has impacted my productivity since February and has gone unresolved until now, my hope was that Roblox staff would be able to look at your module and discern why their engine was not liking it.

And while I am not versed in the totality and depth of FastCast, I had hoped/assume it was well enough written to not be the cause. Its quite popular and is used in notable production games.

I guess I would ask you, does type checking add more value than the cost? I personally havenā€™t had much cause to worry about types in my code design, especially not when using a module such as FastCast with an API. Perhaps the rewrite you propose could do away with type checking?

As a note, Iā€™m not using FastCast right now, its amazing but is far more than I needed in my current case. Therefore it was easy to remove and I dont need any quick fixes right now. THANKS!

Mostly I use type checking as a thing of etiquette. Itā€™s not even functional in the script itself, itā€™s exclusively for the editor.

1 Like

Thanks for the updates folks. This is very helpful. Iā€™ve updated the new information in our internally filed ticket.

4 Likes

Thanks for the details @EtiTheSpirit FastCast sounds like an awesome library.

Was anyone able to confirm that disabling strictness in FastCast resolved the issue? Anyways, hopefully someone on the luau team here will be able to repro and resolve.

5 Likes

I dont even use HTTP request and I still get the error, if you or anyone else has an answer or a good solution to this please let me know ( im new )

try this; remove all Local Script then test the studio or remove Script then do it again(Play), and try that method in other, like gui, sound, assets, particle

A lot of strange stuff has been happening with Studio for some users lately. Ever since the Refresh Update I have not been able to use Studio to finish my game. And the issues are so different and exclusive/varied from user to user. It almost feels like Roblox is practicing shadow banning devs from being able to use the platform efficiently by some sort of hardware specific flagsjust how i feel not that i believe.

October 29 was the last day I could use studio and i havenā€™t heard anything since. Iā€™m sure people can understand how discouraging it is to be forced away from your work. Most likely forgetting the workflow of everything in the 4 month long project i was working on. Itā€™s upsetting how all of a sudden it could be something in your system. You know how things transpired. I ended up with an entirely upgraded windows (from 10 to 11) and studio still froze during play testing. Its not my system but it is something IN STUDIO that is affecting my specific device because i can use another cheap laptop and studio does not freeze. And my main laptop is a decent gaming laptop with a 1650. Was using studio for about a year with no major changes that would require me to basically dismember my laptop in order to get studio to work after it updated to the Refresh Update.

I hope it gets fixed soon but by then i will have lost the passion and know how to continue my project. Why cant Roblox Studio be like Unity or Unreal and allow developers to use the version their most comfortable using or better yet a version that doesnā€™t break certain devices

Hi,

Is this still an issue? Weā€™ve made improvements to the Play since this was originally posted.