Replying to:Infiniteguessbut then itd be super laggy and your phone would explode, ma
Phones are not my fucking problem I use a tablet, and almost every fucking one’s been trying to work pass the node limit for like forever now, take explosive bullet as an example, who uses a phone
Replying to:Infiniteguessidk bro, dont seem like a good idea imo
Whatever happens to somebody’s device is their problem, not the app’s, they trusted the device to not overheat and it overheated, their fault, not the lack of a limit
Replying to:🎄🏳️⚧️René (F)🏳️⚧️🎄There are hundreds of various phone models
App has to accom
I don’t even know why we’re talking about all this, my main issue is how a movieclip’s node count raises the more frames you add, this makes no sense to me
Replying to:⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀I don't even know why we're talking about all this, my mai
It’s the same reason projects have this little thing
1 single frame with 100 nodes won’t waste much in terms of memory , but a 1000 frames will most likely lag hardcore , same with Movieclips , it’s put as a counter in order to let you , add movieclips , without crashing your project
Replying to:Ralph (Developer)basically the discussion above ^
in the next update there w
In some future update (if there ever will be rofl), add a device spec detection thing so people can have node limits based on the specs of their devices, which would excuse people with beefy mobile devices or good PCs running emulators. Yet people with crappy devices will still have to obey the lower limits.
Devices are getting much better today yet people still use weak devices so you’d need a detection system to actually make it fair for both.
2021-08-12 19:24:56 UTC 
Node limit, read the whole thing
The node limit was not reached
Wait
WHY THE FUCK DOES ADDING FRAMES TO MOVIECLIPS ADD MORE NODES TO THE FUCKING MOVIECLIP
THIS IS STUPID
node limit
I vote on removing the node limit completely cuz nobody likes it, it doesn’t help with any mobile limitations, and nobody likes it
but then itd be super laggy and your phone would explode, maybe save unlimited nodes for sticknodes pc
Phones are not my fucking problem I use a tablet, and almost every fucking one’s been trying to work pass the node limit for like forever now, take explosive bullet as an example, who uses a phone
same goes for tablets, some even have less MB and or capability
Maybe atleast have an option to turn the limit off, but have a warning for performance issues
I mean, i guess?
It would still cause complications tho, theres probably a reason why theres a limit, your tablet could probably overheat or something idk
That’s why have a warning for performance issues, there are still some fairly beefy tablets and phones out there
idk bro, dont seem like a good idea imo
Whatever happens to somebody’s device is their problem, not the app’s, they trusted the device to not overheat and it overheated, their fault, not the lack of a limit
but they still have the option, itd be better to have a limit, just so it wont happen. Because most of the time people dont read
Just so it won’t happen? Have you seen some of the packs on this site? They’re like 5+ files because the node limit is ass
I mean, its mainly for accessibility, so you can have the body parts properly layered
I’m talking about the gun packs, the shit that’s like 5 files in one pack because the thing can’t be one file due to the node limit
same goes for guns, the magazine, the uhhh, yeah I dont know that much about guns
The magazines, shells and bullets will obviously be separate from the gun but the gun itself can’t be a singular .nodes file because of the limit
cool
@ralph
Ralphs already been @’ed
he uses a tablet
There are hundreds of various phone models
App has to accommodate as many different mobile devices as possible , all having varying amounts of stats
I don’t even know why we’re talking about all this, my main issue is how a movieclip’s node count raises the more frames you add, this makes no sense to me
It’s the same reason projects have this little thing
1 single frame with 100 nodes won’t waste much in terms of memory , but a 1000 frames will most likely lag hardcore , same with Movieclips , it’s put as a counter in order to let you , add movieclips , without crashing your project
That’s a logical explanation but it’s still infuriating as hell because I can’t get an animation to look smooth because of this shit
Well it’s better then having to gauge what your device can handle at all times
Making figures that use a lot of nodes , movieclips with a bunch of frames and figures , etc
Will at one point , over stress your device
Figures you made with high details may not even be able to be put within the same project due to the sheer amount of lag
This isn’t even counting filters , sounds , tween , fps’s and shit like that
This is why you optimize in order to reduce the node count
Then why are you wanting the app limits gone-
Cuz it still doesn’t fucking work
basically the discussion above ^
in the next update there will be an option to double the FRAME node limit if the user wants to opt in
Unacceptable
In some future update (if there ever will be rofl), add a device spec detection thing so people can have node limits based on the specs of their devices, which would excuse people with beefy mobile devices or good PCs running emulators. Yet people with crappy devices will still have to obey the lower limits.
Devices are getting much better today yet people still use weak devices so you’d need a detection system to actually make it fair for both.
Hell yeah that’s like
…..
6400…x2….
Hold on…
-calculating montage-
12,800 nodes
Sheesh