How to solve UIStroke appearing too big on mobile devices

[Misterx113]

@SonicFrontiers011

Even if yours is a better alternative, you still have no right to call someone else’s code downright trash. You also never tried tinkering around with the Thickness like I said. That’s on you.

Hey, this is wrong, you have to press play before. The code I send will work when you press play.

@SonicFrontiers011

We’re trying to make the UIStroke smaller, not bigger. Your example looks off.

That is correct, but in propertion as I have said ~5 times. As I’ve chalked up several times before, it’s no good to just chop everything down to 1, especially not for a community tutourial.

@SonicFrontiers011

Edit: Look, do what works best for you, but don’t call other people’s way of doing things trash.
This works fine in Roblox Studio for me.

Use different stroke sizes and fix the code you send in this community tutourial, so it dosnt trow an error and then you see that it maxes every ui stroke to this small size, even when ones at 100 and one UIStroke is at 0.01, all go to 1.

@SonicFrontiers011

It appears to work. For all mobile devices.

I wont test it again. Oh, I can see already that it has the same problem again, but without error ig

@SonicFrontiers011

Even if yours is a better alternative, you still have no right to call someone else’s code downright trash. You also never tried tinkering around with the Thickness like I said. That’s on you.

. You know that you can acces the thicknes of ever UIStroke?

@SonicFrontiers011

Edit: Look, do what works best for you, but don’t call other people’s way of doing things trash.
This works fine in Roblox Studio for me.

Even if yours is a better alternative, you still have no right to call someone else’s code downright trash. You also never tried tinkering around with the Thickness like I said. That’s on you.

@SonicFrontiers011

Even if yours is a better alternative, you still have no right to call someone else’s code downright trash.

You shouldn’t have the right to create a misleading community tutorial that beginners follow and see that the code you put together is buggy and doesn’t work as it should.

@SonicFrontiers011

You also never tried tinkering around with the Thickness like I said. That’s on you.

I can tinker around as much as I want, it would still clump everything together to the value with your FINISHED instruction code - the same problem that I have already pointed out ~7 times.

[SonicFrontiers011 (tsuki)]

@Misterx113

Hey, this is wrong, you have to press play before. The code I send will work when you press play.

I literally did press play. Like over 10 times, and not once did it work.

@Misterx113

You shouldn’t have the right to create a misleading community tutorial that beginners follow and see that the code you put together is buggy and doesn’t work as it should.

That’s crazy.

[Misterx113]

@SonicFrontiers011

That’s crazy.

Yea, I am completely with you, why do you do it then?

When you insert this script in a local script in the correct service and enable it, chnage your screensize to whatever and start the game, it will resize all uistrokes to the correct propertionel size.
l

ocal studiosize = Vector2.new(1600,900) -- change this, I just pick random numbers


local function getratio()
    return workspace.CurrentCamera.ViewportSize.Y / studiosize.Y
end

local function onobject(stroke: UIStroke)
    if stroke:IsA("UIStroke") then
        stroke:SetAttribute("Thickness", stroke:GetAttribute("Thickness") or stroke.Thickness)
        stroke.Thickness = stroke:GetAttribute("Thickness") * getratio()
    end
end

local player = game.Players.LocalPlayer
for _, stroke in pairs(player.PlayerGui:GetDescendants()) do
    onobject(stroke)
end
player.PlayerGui.DescendantAdded:Connect(onobject)

Remember to set the screenSize to a correct value.

[SonicFrontiers011 (tsuki)]

Your clearly over exaggerating if you’re saying that it’s buggy.

[Misterx113]

No, it’s underdone, I should actually say faulty, because if I copy it 1to1 from your tutorial, there’s even an error.
Looks like you changed it now. But the biggest problem is still there.
Btw, why only on mobile? On e.g X-Box you have to scale it up [your code would scale all down to the same value], if you would let it be able to run there to [same problem I told you ~8 times about]

[SonicFrontiers011 (tsuki)]

It literally just prints out the UIStroke’s thickness. It’s the exact same. You sure you tested this yourself?

[Misterx113]

Read my post again or give me more context.

[SonicFrontiers011 (tsuki)]

Don’t recommend this tutorial to anyone if it doesn’t even work.

All I did was:

local Player = game.Players.LocalPlayer

local CurrentCamera = game.Workspace.CurrentCamera

local PlayerGui = Player.PlayerGui.MainUI

local Thickness = 1.5

local ViewportRatio = CurrentCamera.ViewportSize.X / CurrentCamera.ViewportSize.Y

local UserInputService = game:GetService("UserInputService")
local TouchEnabled = UserInputService.TouchEnabled


for i, v in pairs(PlayerGui:GetDescendants()) do
	if v:IsA("UIStroke") then
		if TouchEnabled then
			v.Thickness = v.Thickness / (Thickness * ViewportRatio)
		end
	end
end

Are you gonna bother trying it?

[Misterx113]

And again, 2 problems
~9 times: Proportion
And again, this script will error you forgot the end

@SonicFrontiers011

Are you gonna bother trying it?

I did, this came out:

How to solve UIStroke appearing too big on mobile devices

After I fixed your script, you see exactly the problem that I saw and explained to you all the time without testing it and you were too ignorant to see it. After having a proper look at the code I have to say: it is simply absolute trash. tbh Your script: [Screenshot 2024-08-14 181632] Orginale: [Screenshot 2024-08-14 181645] The script I send in this topic: [Screenshot 2024-08-14 181715] Without any script [Screenshot 2024-08-14 181750]

[SonicFrontiers011 (tsuki)]

I literally put the end there but alright. Are you too lazy to put an end yourself?

[Misterx113]

Please dont say or express “I DID I DID, YOU LIER”, when you obviously edited it there.
To your edit:
If you send code into community tutorials [obviously untested at the time] with bugs, it’s up to you to remove them. This is lg a tutorial, not a bug tutorial. It shows quite a lot about your learning ability that you even forget to write an ending, even after correcting it in another post.

[SonicFrontiers011 (tsuki)]

So what you’re saying is, you can’t properly put an END there when there are LITERALLY red lines that show if a format is incorrect. And you literally didn’t even say

local

properly up there

Shows a lot about your learning ability that you even forget to write an ending, even after correcting it in another post.

[Misterx113]

@SonicFrontiers011

show if a format is incorrect. And you literally didn’t even say

local

properly up there

you might notice that in my new post with the code that was cut off.

@SonicFrontiers011

So what you’re saying is, you can properly put an END there when there are LITERALLY red lines that show if a format is incorrect. And you literally didn’t even say

Even bigger shame if you still don’t manage to write your code correctly and send it to a community tutorial. #resources:community-tutorials should be high quality and the OP should know smt about that.

[Misterx113]

@SonicFrontiers011

Shows a lot about your learning ability that you even forget to write an ending, even after correcting it in another post.

Why do you quote me on this? I did not forgot that.

[SonicFrontiers011 (tsuki)]

You quoted me like 9 times earlier just to prove a point and did I say anything.

This topic is over. So PLEASE, stop responding to it.

[Misterx113]

No, I was asking why you wrote an empty statement that wasn’t even true.

@SonicFrontiers011

Shows a lot about your learning ability that you even forget to write an ending, even after correcting it in another post.

@SonicFrontiers011

Are you too lazy to put an end yourself?

I have nicely shown you a better method several times and found errors in your code, and then this happens.

[SonicFrontiers011 (tsuki)]

It’s as simple as pressing enter/return but alright. And here’s the thing I fixed it, and you still haven’t tried it so…

Why are you still bringing that up? Did you test it yet? Your code also did not work, and I did it word for word, so explain that. The UIStroke was exactly the same and nothing changed.

[Misterx113]

@Misterx113

Even bigger shame if you still don’t manage to write your code correctly and send it to a community tutorial. #resources:community-tutorials should be high quality and the OP should know smt about that.

Same asnwer to this. #resources:community-tutorials is a place for high quality content. And then you cut of you code cuz you are to

@SonicFrontiers011

lazy

to

@SonicFrontiers011

pressing enter/return but alright.

@SonicFrontiers011

Why are you still bringing that up? Did you test it yet? Your code also did not work, and I did it word for word, so explain that.

Hi, it works completly fine How to solve UIStroke appearing too big on mobile devices - #7 by Misterx113.
Also its not my code as I wrote. Maybe you are not able to read my small set up guide or to follow it correctly.

[SonicFrontiers011 (tsuki)]

Do you really have to keep responding at this point? Cause your becoming annoying.

[Misterx113]

@SonicFrontiers011

Why are you still bringing that up? Did you test it yet? Your code also did not work, and I did it word for word, so explain that. The UIStroke was exactly the same and nothing changed.

You can view in my post the difference beetwen your and @bluebxrrybot 's script. I quoted it once and replied it here smw.
And now good night.