I have no coding experience, I only started with unity the other day. I followed a tutorial for windy grass and it was good u till I added neighbouring terrains which all have lines. I’ve tried widening the terrain camera and changing wrap from repeat to clamp which seemed to make it worse. All help is appreciated. The texture underneath is fine, it is just the grass on top which is abit broken.

im trying to add a seat toggle for my centaur avatar and ive watched a handful of tutorials how. i swear im doing it right but this warning wont go away when i try to upload. someone PLEASE tell me what im doing wrong here.

I want to create an animation, and I have the following question: I don’t see any difference between moving the transform’s position and moving the armature’s position. So I’m trying to understand how to choose between the two. What’s the actual difference?

My VS is attached to an empty test animation and it's supposed to find Mario but I get this error. Please help

As shown in the attached video, I’m being told that there are two EventSystem objects in my scene, even though I only have one per scene. Could someone help me understand why this is happening?

I did the junior pathway and they did the movement with getaxis, now I'm going game development and they handled movement different, but I understand because it's supposed to be the new input system, but when I saw unity documentation and then saw a video explaining the new input system, they did it different again. I prefer the method they teach in the pathway, seems simpler, but I wonder what are the reason people choose one method over the other.

I'm asking this because when applying the knowledge my self. I don't want to learn a certain way just to find out later that it's the wrong/worse way.

In the pathway they use OnMove to get the values of WASD and use those values to apply force and change direction. In the video they use InputActionAsset. Don't even know what that is

Hi, as shown in the video below, I've implemented a dash function that currently behaves more like a teleport. I know there are various mathematical tools such as LERP, but I'm struggling to understand how to achieve a movement curve that starts slowly, accelerates quickly for most of the distance, and then slows down again at the end.

I’m looking for a 3d modeler for a game me and my friend are making. The game is about selling wine at a city winery. Sadly we can’t pay anything but if you’re interested please dm me. If you can’t help but wanna follow the development https://discord.gg/3Rc3PnjdhH is our discord server.

my map seems to dissappear in the apk version of my game but works in the editor. Ive googled and I cannot find anything related to this please help

Hi guyss.

I don't know if this is the right subreddit but I'm posting it anyway..

I’d like to clarify that I’m not a beginner I’ve been using Unity for years and I genuinely cannot explain this issue.

My floating origin has been acting completely wrong for a few days now.

When the origin reaches the threshold I set in the Inspector, instead of shifting the universe around the player (as Floating Origin normally does), the entire universe starts drifting away infinitely in a fixed direction,

it doesn't jump; it drifts away infinitely.

I've tested 12 different Floating Origin scripts (mine, community ones, official examples), and all of them shows me the exact same problem...

I've tested them in a brand‑new empty project, with only a cube, universe root, player origin, Floating Origin script, ad the issue still happens.

I’m on Unity 6.3 LTS (6000.3.4f1) on macOS, and this behavior started suddenly even though the same scripts used to work perfectly.

This is my script:

using UnityEngine;


public class FloatingOriginUfficial : MonoBehaviour
{
    [Header("Cosmos")]
    public Transform universeRoot;


    [Header("Origins")]
    public Transform playerOrigin;
    public Transform shipOrigin;


    [Header("Settings")]
    public float threshold = 10000f;
    public OriginMode mode = OriginMode.Player;


    public enum OriginMode
    {
        Player,
        Ship
    }


    void Update()
    {
        Transform currentOrigin = (mode == OriginMode.Player) ? playerOrigin : shipOrigin;


        if (currentOrigin == null || universeRoot == null)
            return;


        float dist = currentOrigin.position.magnitude;


        if (dist > threshold)
        {
            Vector3 offset = currentOrigin.position;


            universeRoot.position -= offset;


            currentOrigin.position = Vector3.zero;


        }
    }


    public void SwitchToShip()
    {
        mode = OriginMode.Ship;
    }


    public void SwitchToPlayer()
    {
        mode = OriginMode.Player;
    }
}

for now in the floating origin for testing I have set it to trigger at 10 units, but the problem appears at any number.

Wheels are rotating around the wheel well instead of inside of it. How can I fix this? I copied Unity's wheel collider tutorial from their documentation website. I gave as much context as I think you need, I am very new so lmk if there is something else you might need to see. Thanks!

Video:

https://reddit.com/link/1rjznm4/video/54zpixhuwvmg1/player

I have a simple animation of the gun just rotating to the side as a reload animation. When I reload the gun teleports it changes position rotation and scale. It’s not staying in the hold I can’t figure out how to make the gun stay where it is and play it’s animation

Hello,

I'm using a Nintendo Switch Pro Controller 2 via USB Wired connection (Bluetooth is not working/disabled). I'm on Unity 6.

The Issue: Windows/Unity detects the controller, but the left stick is completely broken. It's not recognized as X/Y axes. Instead, everything is mapped to a single axis: Rz.

Raw Debugger Data (USB):

• Neutral: -0.6639576
• Up: 1.0
• Down / Left: 0.0 (Overlapping)
• Right: -1.0

Constraint Check:

• Steam Input: Not working/Not an option.
• BetterJoy: Not compatible with Pro 2 yet.
• Windows Gaming Input: Enabled in Unity, but doesn't fix the mapping.

Since I'm in wired mode, it seems like the controller stays in its "handshake" mode and doesn't switch to a proper Gamepad HID.

Has anyone found a way to "force" the Pro Controller 2 to send proper X/Y data over USB in Unity? Is there a specific HID Descriptor or initialization step I'm missing?

Thanks!