@Lake
As WolfHunter9111 is right.
This is the "ロポリこん(Low Poly Kon)" of the avatar model sold for VRChat.
It is a good avatar that suits everyone and is easy to handle.
If you're talking about my work, here is what I made when I was talking about another topic before.
Since multiple Alpha tags are used for partial display switching, it is necessary to access all of them in order to turn the whole on / off.
@TRD6932
That video was something I was building to reproduce the motion tracer in AV-98 INGRAM.
It has been stagnant because other hobbies have been taking up my time, but I will finish it someday.
I did, on an old account that had already disappeared.
(the account name resembled my real name, and there was no ability to change the name at the time)
I'll leave it to you to decide if you believe me or not.
@PlaneFlightX
Things that are more than half a year old are almost gone.
At that time, the published works, including past works, were a source of strong stress.
@JoshuaW
The information is based on the controlbase.
The control of the arm is calculated by inverse kinematics.
However, the control around the wrist is still in the realm of my academic ability to handle, so I use the variable output of the free hinge to get the angle directly.
At the bottom of the variables section, I think there are some variables that have "~ sum (Activate1 + 1) ~" in the activator.
.
They are variables for the initial condition, and each variable creates a cell at the coordinates corresponding to the name.
@xiaofootball
If I can find a better way to improve it, I may make one, but it will probably be a while before I do. Someone else may do it before then.
I found the throttle lever to be very tilted.
(This makes your wrist look like the back of your hand is pointing inward in VR, which leads to wrist fatigue and discomfort.)
Also, the pedals seem to be a little too close together.
.
The rest of the work is fine, at least as far as I can tell.
@2Papi2Chulo
I just want to know how my parts are being used in the work through notifications and ego searches.
So an description or comment is enough.
@FeatherWing
I don't know the specific position. However, if you have a text editor with bulk replace (for example, Windows default Notepad), you can replace Altitude and AltitudeAgl with any expression.
HudDistance
This is used to properly position the TD BOX and other displays.
Enter the distance between the HUD and the view point.
If you have changed the scale of the HUD distance/scale.
The distance between the parts is 0.6 and the scale of the HUD is 0.15.
If you do what it says in the summary section
distance=0.6 scale=0.15 idistance/scale 0.6/0.15=4
It should look like this. Why does it have to be 0.5?
@Amirabadi
HudDistance needs to be set correctly according to the distance from the camera.
If you change the scale of the HUD, you need to set it to reflect the change.
Maybe you are copying the default value of 2?
@Amirabadi
Due to the specifications of the parts, it is impossible to change the behavior by changing the scale. Also, we have confirmed that changing the scale works many times during the production process.
Have you copied the TGTPOS_Local variable and set the HudDistance yet?
@Amirabadi
It is possible, or rather recommended to reduce the default size as it is too large.
If you change the scale, please reflect the effect of the scale in HudDistance as noted in the overview.
@FeatherWing
I think you can do this by replacing TAS * 3.6, Altitude, AltitudeAgl with the appropriate expression and [TAS] with the appropriate name using a bulk replace function such as Notepad.
I don't know the specific unit conversion formula, so please do it yourself.
Check the copy of TGTPOS_Local and the Hud Distance setting.
If that doesn't work, you can't figure out the cause without looking at the real thing, so can you post the build in question unlisted and mention it?
@CalculatorBoi
I'm not going to change the speed display, but it's certainly a problem that the display disappears when the speed is completely 0, so I'll fix it as soon as I find the cause.
@CalebRepublic
Rich Text Format in Unity's TextMesh Pro. However, a little unusual, you can include FT in a format similar to C # but slightly different. FT (Funky Tree) is an in-game format, and I personally feel that Excel has similar functions.
Please change the reference point of Altitude Agl to the center of the cockpit.
The current reference point is the center of gravity on the build screen as seen from the cockpit, which makes it inconvenient to work with Altitude, which uses the center of the cockpit as its reference point.
@Ian_Yashima
Thanks!
I personally like it, but I don't know if it can be applied to other builds in the future because the procedure tends to be complicated.
@Kangy
+2He noted that PONG was the first computer game in the world to be released to the public.
@Lake
+2As WolfHunter9111 is right.
This is the "ロポリこん(Low Poly Kon)" of the avatar model sold for VRChat.
It is a good avatar that suits everyone and is easy to handle.
To those who find this creepy.
I heartily agree.
If you're talking about my work, here is what I made when I was talking about another topic before.
Since multiple Alpha tags are used for partial display switching, it is necessary to access all of them in order to turn the whole on / off.
@SheriffHackdogMCPE
No, it has little to do with what I'm making here.
Over there, we mainly make costumes and accessories rather than the main body.
+3@TRD6932
+1That video was something I was building to reproduce the motion tracer in AV-98 INGRAM.
It has been stagnant because other hobbies have been taking up my time, but I will finish it someday.
Congratulations!!
I did, on an old account that had already disappeared.
(the account name resembled my real name, and there was no ability to change the name at the time)
I'll leave it to you to decide if you believe me or not.
@Cleopatra
As you can see in the gif on this page, It should have already been implemented...
@Lancelot1230
OK to use.
@PlaneFlightX
+5Things that are more than half a year old are almost gone.
At that time, the published works, including past works, were a source of strong stress.
@JoshuaW
+4The information is based on the controlbase.
The control of the arm is calculated by inverse kinematics.
However, the control around the wrist is still in the realm of my academic ability to handle, so I use the variable output of the free hinge to get the angle directly.
@V
At the bottom of the variables section, I think there are some variables that have "~ sum (Activate1 + 1) ~" in the activator.
+3.
They are variables for the initial condition, and each variable creates a cell at the coordinates corresponding to the name.
@xiaofootball
+1If I can find a better way to improve it, I may make one, but it will probably be a while before I do. Someone else may do it before then.
@Bryan5
+1I confirmed it as of yesterday. Just in case, I am seeking instructions from other curators.
I found the throttle lever to be very tilted.
+1(This makes your wrist look like the back of your hand is pointing inward in VR, which leads to wrist fatigue and discomfort.)
Also, the pedals seem to be a little too close together.
.
The rest of the work is fine, at least as far as I can tell.
@2Papi2Chulo
+2I just want to know how my parts are being used in the work through notifications and ego searches.
So an description or comment is enough.
In addition, since it is set not to receive comment notifications, there is a high possibility that you will not be able to reply.
@Chaka
The problem is caused by the undefined variables, as in the comments of many others. Read the explanation
@AtlasSP
+11
2
If you don't understand this, I can't give you any more advice
For example, in C language, (A?B:C) works like
if(A == true)
B
else
C
.
A can be a comparison or Boolean value, B and C can be in any format
Please read the explanation once before asking a question. Writing the same reply over and over is very tiring
@AtlasSP
+1The tag is broken because the variable is not defined. Read the description on this page for details
@CalebRepublic
"if" has a ternary operator (A? B: C). There is no "for", but I think it can be reproduced using some variables.
@derlurje
I don't know, but I think some parts are missing when copying
@derlurje
I don't think the scale can affect the behavior ... Did you change anything else?
@FeatherWing
I don't know the specific position. However, if you have a text editor with bulk replace (for example, Windows default Notepad), you can replace Altitude and AltitudeAgl with any expression.
@ShinyGemsBro
Please read the explanation. Did you forget the existence of variables? I'm tired of writing this word
@Amirabadi
---Variables list---
This is used to properly position the TD BOX and other displays.
Enter the distance between the HUD and the view point.
If you have changed the scale of the HUD
distance/scale
.The distance between the parts is 0.6 and the scale of the HUD is 0.15.
+1If you do what it says in the summary section
distance=0.6 scale=0.15
idistance/scale
0.6/0.15=4
It should look like this. Why does it have to be 0.5?
@Amirabadi
HudDistance needs to be set correctly according to the distance from the camera.
If you change the scale of the HUD, you need to set it to reflect the change.
Maybe you are copying the default value of 2?
@Amirabadi
Due to the specifications of the parts, it is impossible to change the behavior by changing the scale. Also, we have confirmed that changing the scale works many times during the production process.
Have you copied the
TGTPOS_Local
variable and set theHudDistance
yet?@OtakuNekoToT
The part shown in your image is actually this part.
And I'll send it to you because it was surprisingly easy to do when I tried it.
Here
@Amirabadi
It is possible, or rather recommended to reduce the default size as it is too large.
If you change the scale, please reflect the effect of the scale in HudDistance as noted in the overview.
@FeatherWing
+1I think you can do this by replacing TAS * 3.6, Altitude, AltitudeAgl with the appropriate expression and [TAS] with the appropriate name using a bulk replace function such as Notepad.
I don't know the specific unit conversion formula, so please do it yourself.
@OtakuNekoToT
+1You can remove unnecessary parts from the code, but I don't want to do it because it's quite annoying
@AtlasSP
I'm not sure of the current situation, can you send me a build of the problem?
@AtlasSP
Make sure the variables are copied / set correctly.
@Assassindragons
Check the copy of TGTPOS_Local and the Hud Distance setting.
+1If that doesn't work, you can't figure out the cause without looking at the real thing, so can you post the build in question unlisted and mention it?
@CalculatorBoi
I'm not going to change the speed display, but it's certainly a problem that the display disappears when the speed is completely 0, so I'll fix it as soon as I find the cause.
@Kronkcrete
I made it this size to make it easier to calculate the coordinates, but if necessary, use overload to change the scale.
@AtlasSP
If you have a pc, open xml with Notepad and use the replace all function TAS → GS
@Yehia
+1Same in the sense of Asian, but I'm Japanese
@edensk
Oops. I'll upload the fixed one later unlisted and put a link in the overview
@CalebRepublic
Rich Text Format in Unity's TextMesh Pro. However, a little unusual, you can include FT in a format similar to C # but slightly different.
FT (Funky Tree) is an in-game format, and I personally feel that Excel has similar functions.
I couldn't have done it without the buttons and variable functions.
+3I made it in a short time, so it's rough.
Build is here
Variable system!!! I'm overexcite and crazy!!!!!
+1@TheVexedVortex
actual map.
Excellent modeling!
I can't wait to see it in action.
Please change the reference point of Altitude Agl to the center of the cockpit.
+4The current reference point is the center of gravity on the build screen as seen from the cockpit, which makes it inconvenient to work with Altitude, which uses the center of the cockpit as its reference point.
@Ian_Yashima
+2Thanks!
I personally like it, but I don't know if it can be applied to other builds in the future because the procedure tends to be complicated.