109k PlanariaLab Comments

  • Arm tracking test 2.4 years ago

    @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.

    +5
  • Arm tracking test 2.4 years ago

    @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.

    +4
  • Game of Life(galaxy) 2.4 years ago

    @V

    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.

    +3
  • Thoughts on using 1PartsHud in VR 2.5 years ago

    @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.

    +1
  • F-16 Falcon 1.11 FIXED 2.5 years ago

    @Bryan5
    I confirmed it as of yesterday. Just in case, I am seeking instructions from other curators.

    +1
  • F-16 Falcon 1.11 2.5 years ago

    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.

    +1
  • 1Parts HUD 2.5 years ago

    @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.

    +2
  • Kotonoha-sisters 2.6 years ago

    In addition, since it is set not to receive comment notifications, there is a high possibility that you will not be able to reply.

  • 1Parts HUD 2.6 years ago

    @Chaka
    The problem is caused by the undefined variables, as in the comments of many others. Read the explanation

  • 1Parts HUD 2.6 years ago

    @AtlasSP
    1
    2
    If you don't understand this, I can't give you any more advice

    +1
  • 1Parts HUD 2.6 years ago

    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

  • 1Parts HUD 2.6 years ago

    Please read the explanation once before asking a question. Writing the same reply over and over is very tiring

  • 1Parts HUD 2.6 years ago

    @AtlasSP
    The tag is broken because the variable is not defined. Read the description on this page for details

    +1
  • 1Parts HUD 2.6 years ago

    @CalebRepublic
    "if" has a ternary operator (A? B: C). There is no "for", but I think it can be reproduced using some variables.

  • 1Parts HUD 2.6 years ago

    @derlurje
    I don't know, but I think some parts are missing when copying

  • 1Parts HUD 2.6 years ago

    @derlurje
    I don't think the scale can affect the behavior ... Did you change anything else?

  • 1Parts HUD 2.6 years ago

    @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.

  • 1Parts HUD 2.6 years ago

    @ShinyGemsBro
    Please read the explanation. Did you forget the existence of variables? I'm tired of writing this word

  • 1Parts HUD 2.6 years ago

    @Amirabadi

    ---Variables list---

    • 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?

    +1
  • 1Parts HUD 2.6 years ago

    @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?

  • 1Parts HUD 2.6 years ago

    @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?

  • 1Parts HUD 2.6 years ago

    @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

  • 1Parts HUD 2.6 years ago

    @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.

  • 1Parts HUD 2.6 years ago

    @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.

    +1
  • 1Parts HUD 2.6 years ago

    @OtakuNekoToT
    You can remove unnecessary parts from the code, but I don't want to do it because it's quite annoying

    +1
  • 1Parts HUD 2.6 years ago

    @AtlasSP
    I'm not sure of the current situation, can you send me a build of the problem?

  • 1Parts HUD 2.6 years ago

    @AtlasSP
    Make sure the variables are copied / set correctly.

  • 1Parts HUD 2.6 years ago

    @Assassindragons

    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?

    +1
  • 1Parts HUD 2.6 years ago

    @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.

  • 1Parts HUD 2.6 years ago

    @Kronkcrete
    I made it this size to make it easier to calculate the coordinates, but if necessary, use overload to change the scale.

  • 1Parts HUD 2.6 years ago

    @AtlasSP
    If you have a pc, open xml with Notepad and use the replace all function TAS → GS

  • 1Parts HUD 2.6 years ago

    @Yehia
    Same in the sense of Asian, but I'm Japanese

    +1
  • 1Parts HUD 2.6 years ago

    @edensk
    Oops. I'll upload the fixed one later unlisted and put a link in the overview

  • 1Parts HUD 2.6 years ago

    @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.

  • [Beta] Passcode Lock 2.7 years ago

    I couldn't have done it without the buttons and variable functions.
    I made it in a short time, so it's rough.
    Build is here

    +3
  • 1.11 Beta is now available 2.7 years ago

    Variable system!!! I'm overexcite and crazy!!!!!

    +1
  • Fairy Map (comming soon) 2.8 years ago

    @TheVexedVortex
    actual map.

  • Evangelion - 02 a trailer 2.8 years ago

    Excellent modeling!
    I can't wait to see it in action.

  • Small Feature Wish List for v1.11 Update 2.8 years ago

    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.

    +4
  • AV-98 INGRAM 2.8 years ago

    @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.

    +2
  • AV-98 INGRAM 2.8 years ago

    @210100
    The real thing is folded in the arm and quickly replaces the dummy on the leg or shield

    +2
  • HOS boot screen 2.8 years ago

    Link(use Mod parts)
    From "PATOLABOR The movie"
    I made this on the spur of the moment at midnight high.
    Production time: 5~6 hours.
    .
    This is just a joke video, not a teaser for AV-X0 or any other HOS-related work.

  • Small Feature Wish List for v1.11 Update 2.8 years ago

    A character label that supports the Funky Tree string format.
    This will be useful for displaying the name of the selected armament, data with units, mode switching of the aircraft, etc.

    +7
  • Who's your favorite SP Builder? 2.8 years ago

    KarlovyVary, Ceska, Ian_Yashima and Suica.

  • SimplePlanes VR - Coming 2021 to Steam and Oculus Quest 2.8 years ago

    Hey, are there any plans to add a FunkyTree function for the position and angle of the HMD and 6DoF controller?
    I think it will be very helpful in creating works like JHMCS and powered suits.

    +6
  • Mannish Chang 2.9 years ago

    @VolcanicAsh
    No problem, at least for me.

    +1
  • Thank you for platinum! 3.2 years ago

    Congratulations!

    +1
  • About complex Funky trees code on builds 3.2 years ago

    Try changing the machine gun activation group or reducing the number of turrets.
    The test machine is like a kind of demonstration, packed with an unnecessary amount of features.
    .
    Also, my little brain can't simplify the formula any further because it takes a lot of calculations to deal with the tilt of the cockpit. (We need to create a completely different calculation method)
    .

    +1
  • RB-79_BALL 3.2 years ago

    @MAHADI
    Change the value of the "opacity" item in the Transparency section.
    Depending on this value, two different flashes can be made.
    .
    The first is to increase the value of the opacity (more than 2).
    By setting the color Metallic to less than 10%, the glass will emit light.
    In this case, the glass will be opaque.
    .
    The second method is to set the opacity value to a negative value (-200 or less).
    Select a color that is the opposite of the color you want, and reduce the brightness of the color to make it glow.
    You can change the transparency of the color Metallic.
    The glass will emit light while maintaining transparency. (Like a hologram in a sf movie, for example.)
    However, please note that this method may not display well on mobile devices.

  • Evangelion Mark.44B 3.2 years ago

    @Jaspy109
    It has already appeared at the beginning of 10 minutes 40 seconds 00 frames released at last year's notice event.
    In addition, at the same time, the material images of these machine were released on the khara official Twitter account.
    So I thought this was harmless.

    +4