Polygon Collider 2D - unable to view/edit points

Unity Engine
1

I posted this over on Unity Answers, but didn’t get any response, and am hoping someone here knows what is going on.

https://answers.unity.com/questions/1865622/polygon-collider-2d-unable-to-viewedit-points.html

Since then, I gave my friend a copy of the project, and he was able to load it up and see/modify these points without a problem. I also created a blank project, and the same issue exists there as well, so that makes me think something went wrong with my unity install… Is my best bet just to uninstall all my unity versions and re-install? I’m worried that won’t fix the issue.

In addition, while following along with the Brackeys “Introduction to AUDIO in Unity” video, I noticed another similar scenario: I created a “Sound” class, which is as follows:

using UnityEngine;
using UnityEngine.Audio;

[System.Serializable]
public class Sound
{
    public AudioClip clip;

    public float volume;
    public float pitch;
}

Then on my AudioController object, I defined a public array of this class:

public Sound[] Sounds;

Within the editor, I now have an array that I can change the size of, but none of the fields appear inside of it. When he does it in the video, there are 3 items inside each element, and he can set the audio clip, volume and pitch.

7594177--941920--upload_2021-10-22_8-36-0.png
7594177--941920--upload_2021-10-22_8-36-0.png1254×288 11.6 KB

Am I missing something super obvious here or what? I haven’t been able to find anyone else with a similar issue.

2

Still dealing with this issue… Essentially any expandable list like in the screenshot above just shows as empty.

3

Ok, I think I figured out what is going on. After uninstalling all my unity versions and removing all unity data from my machine (including the registry), it worked when using it in Unity 2021.2.0f1. Then it stopped working again. However, I noticed that it works fine on my laptop screen (unscaled 1920x1080), but disappears again on both my 4k and 1440p monitors, I would guess because of windows scaling.

So, if anyone else runs into this, it’s likely a scaling issue.