Honestly, completely removing every node limit is irrefutable. I think Ralph is aiming too user-friendly with things and it’s time to change things up a bit. We need more functionality and freedom on this app, even if it might scare some people off. I think Ralph heading at least a little bit in that direction is healthy for the app.
Well, we should remove the frame limit for movieclips, although I don’t have a lot of problems with the limitation.
As for the node limit, it should be removed for projects and movieclips. Don’t remove the limit for stickfigures though, it could cause the fig to be unoptimized.
Replying to:Jadey M.Well, we should remove the frame limit for movieclips, altho
I still think that “figs shouldn’t have limitless nodes because of optimization” is not a possible argument to be made; if you are good at making figs, you would already be optimizing them anyway, and it’d be a requirement for uploading your figures to the site.
Replying to:Jadey M.Well, we should remove the frame limit for movieclips, altho
i think so too
i think it would be pretty neat if movieclips had more frames, for example animating instruments, most of the time when animating them i can only animate about 2 measures, since it adds up to 80 frames. if we had more frames though i could probably animate the entire track
Replying to:Jadey M.Well, we should remove the frame limit for movieclips, altho
Agreed. The node limit for figures gives some sort of enforcement of optimization. We should definitely get some limitless potential with projects and movieclips though. Provided there’s a system where you can’t submit movieclips that break a given limit when we do get MC submission.
Replying to:Explosive BulletAgreed. The node limit for figures gives some sort of enforc
Yeah. You’re right about that first part.
It sucked a lot since we have to deal with limitation on projects and movieclips, so removing the entire thing would make things better (but with the cost of performance).
Replying to:Jadey M.Yeah. You're right about that first part.
It sucked a lot s
Cost of performance if you plan to go beyond the recommended limit. That’s where I would be all for changing the current limit to a recommendation as it really becomes an annoyance for higher end devices.
Well Node limit may be a cool idea like we can have near god level tier figures that pretty much look like blender creations, however its just a bad idea due to the Device power and their processing power and it could lag the device due to how much nodes it has probably even effects too. That we have to start selling our mom’s New gen Samsung galaxy’s or iPhone’s just to get another powerful device.
When we on life support
Honestly, completely removing every node limit is irrefutable. I think Ralph is aiming too user-friendly with things and it’s time to change things up a bit. We need more functionality and freedom on this app, even if it might scare some people off. I think Ralph heading at least a little bit in that direction is healthy for the app.
Well, we should remove the frame limit for movieclips, although I don’t have a lot of problems with the limitation.
As for the node limit, it should be removed for projects and movieclips. Don’t remove the limit for stickfigures though, it could cause the fig to be unoptimized.
Am I the only one who think like this though?
I still think that “figs shouldn’t have limitless nodes because of optimization” is not a possible argument to be made; if you are good at making figs, you would already be optimizing them anyway, and it’d be a requirement for uploading your figures to the site.
There’s a frame limit for movieclips?
100
Huh, cool
Yepperonis
Speaking about that, there is a node limit for movieclips too
(Somewhere about 128,000 for the entire clip. Or something).
i think so too
i think it would be pretty neat if movieclips had more frames, for example animating instruments, most of the time when animating them i can only animate about 2 measures, since it adds up to 80 frames. if we had more frames though i could probably animate the entire track
Agreed. The node limit for figures gives some sort of enforcement of optimization. We should definitely get some limitless potential with projects and movieclips though. Provided there’s a system where you can’t submit movieclips that break a given limit when we do get MC submission.
Yeah. You’re right about that first part.
It sucked a lot since we have to deal with limitation on projects and movieclips, so removing the entire thing would make things better (but with the cost of performance).
Cost of performance if you plan to go beyond the recommended limit. That’s where I would be all for changing the current limit to a recommendation as it really becomes an annoyance for higher end devices.
User Banned
Well Node limit may be a cool idea like we can have near god level tier figures that pretty much look like blender creations, however its just a bad idea due to the Device power and their processing power and it could lag the device due to how much nodes it has probably even effects too. That we have to start selling our mom’s New gen Samsung galaxy’s or iPhone’s just to get another powerful device.