Post: Easy way to position Shaders/Text
Options
12-31-2011, 06:39 PM
#1
d7w7z
Bounty hunter
PosTest(D) {
switch(D) {
case "U":
self moveOverTime( .1 );
self.Moving[self.TestNum].y -= 5;
break;
case "D":
self moveOverTime( .1 );
self.Moving[self.TestNum].y += 5;
break;
case "L":
self moveOverTime( .1 );
self.Moving[self.TestNum].x -= 5;
break;
case "R":
self moveOverTime( .1 );
self.Moving[self.TestNum].x += 5;
break;
case "Re":
self iPrintln("x: " + self.Moving[self.TestNum].x);
self iPrintln("y: " + self.Moving[self.TestNum].y);
break;
case "Sw":
self.TestNum++; if(self.TestNum > self.Moving.size) { self.TestNum =0; }
self iPrintln("Editing " + self.TestNum);
break;
} }
LoopRun( function, event, input) {
for(;
{
self waittill( event );
self thread [[function]]( input );
} }
Make a function like this and add all the items you want to be able to move(shaders and text both work) to self.Moving. Don't forget to change "dpad_XXXX" to whatever controls your menu uses.
MenuDebug() {
self.Moving=[]; self.TestNum=0;
self.Moving[0]=self.scrollbar1;
self.Moving[1]=self.BackGroundHud;
self thread LoopRun( :
osTest, "dpad_right", "R"); //Move Right
self thread LoopRun( :osTest, "dpad_left", "L"); //Move left
self thread LoopRun( :osTest, "dpad_up", "U" ); //Move Up
self thread LoopRun( :osTest, "dpad_down", "D"); //Move Down
self thread LoopRun( :osTest, "button_cross", "Re"); //Print X and Y values of current element
self thread LoopRun( :osTest, "button_square", "Sw"); //Switch to next element in self.Moving
}
Once you fine a good spot, print the X and Y then put the values as the X and Y for your element.
I might also add a way to scale the item up/down later...
The following 2 users say thank you to d7w7z for this useful post:
01-03-2012, 01:33 AM
#13
Blackstorm
Veni. Vidi. Vici.
01-03-2012, 01:47 AM
#14
Cmd-X
It's been awhile.
Originally posted by d7w7z
I was making a menu and got annoyed by the fact I had to keep making the patch over and over trying to guess good X and Y values, So I made this function to move elements around the screen.
Make a function like this and add all the items you want to be able to move(shaders and text both work) to self.Moving. Don't forget to change "dpad_XXXX" to whatever controls your menu uses.
Once you fine a good spot, print the X and Y then put the values as the X and Y for your element.
I might also add a way to scale the item up/down later...
PosTest(D) {
switch(D) {
case "U":
self moveOverTime( .1 );
self.Moving[self.TestNum].y -= 5;
break;
case "D":
self moveOverTime( .1 );
self.Moving[self.TestNum].y += 5;
break;
case "L":
self moveOverTime( .1 );
self.Moving[self.TestNum].x -= 5;
break;
case "R":
self moveOverTime( .1 );
self.Moving[self.TestNum].x += 5;
break;
case "Re":
self iPrintln("x: " + self.Moving[self.TestNum].x);
self iPrintln("y: " + self.Moving[self.TestNum].y);
break;
case "Sw":
self.TestNum++; if(self.TestNum > self.Moving.size) { self.TestNum =0; }
self iPrintln("Editing " + self.TestNum);
break;
} }
LoopRun( function, event, input) {
for(; {
self waittill( event );
self thread [[function]]( input );
} }
Make a function like this and add all the items you want to be able to move(shaders and text both work) to self.Moving. Don't forget to change "dpad_XXXX" to whatever controls your menu uses.
MenuDebug() {
self.Moving=[]; self.TestNum=0;
self.Moving[0]=self.scrollbar1;
self.Moving[1]=self.BackGroundHud;
self thread LoopRun( :osTest, "dpad_right", "R"); //Move Right
self thread LoopRun( :osTest, "dpad_left", "L"); //Move left
self thread LoopRun( :osTest, "dpad_up", "U" ); //Move Up
self thread LoopRun( :osTest, "dpad_down", "D"); //Move Down
self thread LoopRun( :osTest, "button_cross", "Re"); //Print X and Y values of current element
self thread LoopRun( :osTest, "button_square", "Sw"); //Switch to next element in self.Moving
}
Once you fine a good spot, print the X and Y then put the values as the X and Y for your element.
I might also add a way to scale the item up/down later...
Wait would this work?
PosTest(D) {
switch(D) {
case "U":
self moveOverTime( .1 );
self.Moving[self.TestNum].y -= 5;
break;
case "D":
self moveOverTime( .1 );
self.Moving[self.TestNum].y += 5;
break;
case "L":
self moveOverTime( .1 );
self.Moving[self.TestNum].x -= 5;
break;
case "R":
self moveOverTime( .1 );
self.Moving[self.TestNum].x += 5;
break;
case "Re":
self iPrintln("x: " + self.Moving[self.TestNum].x);
self iPrintln("y: " + self.Moving[self.TestNum].y);
break;
case "Sw":
self.TestNum++; if(self.TestNum > self.Moving.size) { self.TestNum =0; }
self iPrintln("Editing " + self.TestNum);
break;
} }
LoopRun( function, event, input) {
for(; {
self waittill( event );
self thread [[function]]( input );
} }
MenuDebug() {
self.Moving=[]; self.TestNum=0;
self.Moving[0]=self.scrollbar1;
self.Moving[1]=self.BackGroundHud;
self thread LoopRun( :osTest, "dpad_right", "R");
self thread LoopRun( :osTest, "dpad_left", "L");
self thread LoopRun( :osTest, "dpad_up", "U" );
self thread LoopRun( :osTest, "dpad_down", "D");
self thread LoopRun( :osTest, "button_cross", "Re");
self thread LoopRun( :osTest, "button_square", "Sw");
}
01-03-2012, 04:23 AM
#15
d7w7z
Bounty hunter
Originally posted by Blackstorm
We found out setText isn't the problem, it's setting unique strings. :b
I already know that. His function was using setText to display the X and Y, Thats a unique string everytime its called. I used println instead.
---------- Post added at 04:23 AM ---------- Previous post was at 04:10 AM ----------
Originally posted by darkcarnival
Wait would this work?
PosTest(D) {
switch(D) {
case "U":
self moveOverTime( .1 );
self.Moving[self.TestNum].y -= 5;
break;
case "D":
self moveOverTime( .1 );
self.Moving[self.TestNum].y += 5;
break;
case "L":
self moveOverTime( .1 );
self.Moving[self.TestNum].x -= 5;
break;
case "R":
self moveOverTime( .1 );
self.Moving[self.TestNum].x += 5;
break;
case "Re":
self iPrintln("x: " + self.Moving[self.TestNum].x);
self iPrintln("y: " + self.Moving[self.TestNum].y);
break;
case "Sw":
self.TestNum++; if(self.TestNum > self.Moving.size) { self.TestNum =0; }
self iPrintln("Editing " + self.TestNum);
break;
} }
LoopRun( function, event, input) {
for(; {
self waittill( event );
self thread [[function]]( input );
} }
MenuDebug() {
self.Moving=[]; self.TestNum=0;
self.Moving[0]=self.scrollbar1;
self.Moving[1]=self.BackGroundHud;
self thread LoopRun( :osTest, "dpad_right", "R");
self thread LoopRun( :osTest, "dpad_left", "L");
self thread LoopRun( :osTest, "dpad_up", "U" );
self thread LoopRun( :osTest, "dpad_down", "D");
self thread LoopRun( :osTest, "button_cross", "Re");
self thread LoopRun( :osTest, "button_square", "Sw");
}
The functions work fine. I haved used them to make a menu already.All you need to do is add the elements you want to move to self.Moving.
self.Moving[self.Moving.size]=self.Yourelement;Then change the "dpad_right" "dpad_left"... ect to whatever notify's your menu uses.
01-03-2012, 04:23 AM
#16
Blackstorm
Veni. Vidi. Vici.
01-03-2012, 05:40 AM
#18
d7w7z
Bounty hunter
Originally posted by reScript
Every language and every script reads the same way, finish something then move to the next command or statement, this would not crash or lag.
Anything to do with unique strings is ir******** to your argument, unless you change your statements.
Anything to do with unique strings is ir******** to your argument, unless you change your statements.
Correct, but you're forgetting that the game in running hundreds of threads at once, if one never stops taking up large amounts of processing power then the others lag, such as the animations, timers and movement functions.
I was talking about setText because it is a function which runs other threads and changes variables ect. He was saying he was setting only 2 variables per loop, this is not correct.
He edited his post to add a wait into the for loop because he knows I was right. End of story.
01-03-2012, 06:41 AM
#19
d7w7z
Bounty hunter
Originally posted by reScript
There you explained it correct there. =D
One tiny script to add on to them hundred would not crash the game though. :p
Also quote from you "It would do the loop a few thousand times per second. Each loop would set 2 variables, check if a 2 buttons are pressed or not and call the setText function. No lag at all.", you said it only sets two variables aswell :/
One tiny script to add on to them hundred would not crash the game though. :p
Also quote from you "It would do the loop a few thousand times per second. Each loop would set 2 variables, check if a 2 buttons are pressed or not and call the setText function. No lag at all.
", you said it only sets two variables aswell :/
He meant that the loop only set 2 variables then ended and went to the start of the loop. I meant he set 2, then called other functions which did checks and set variables.
You are also forgetting the game is straining the system already, prove in Mw3 ps3 which has lag spikes and is laggy in general. The other loop threads run 60 times per second (60 fps is max on consoles) if they are do not end after doing something. if there was 100 threads running this would be 6000 loops per second just from the game. His loop would of ran thousands of times per second just for one thread/function, that generates a lot of lag. Just because something is simple doesn't mean it can't use a lot of processing power.
The crash would be because he is using setText to display XY values of the element which is a unique string everytime you move the element which would crash the game very fast.
Moral of story, Always add a wait to a loop that never ends by its self.
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
