Thanks for this. I will give it a go some point this weekend.
So basically I did the crosshair as parent, as when I crouched with it as a child of player it would always resize it, so I made the crosshair a parent and this fixed that issue of it resizing when crouching. I was then advised on #bolt-beginner-help on discord by TowerCrow and I think someone else to always do everything as parent objects, this way its easier and faster to obtain the gameobject and run the code in bolt, I think thats what was said anyway... trying to look over messages and can't remember / make much sense of this. I think unless I can better describe why I am doing this, is reattach the main camera as a child object to the player, as it don't seem to be breaking anything, including the crouching, this still works as intended.
I think figuring out how and why I am using a raycast is the best step forward, I usually look in the unity documentation for this, but I don't know exactly what I am looking from in the unity documentation respective of raycasts and what I am looking to achieve on the crouching?, from there I willl research how to apply a bool to such effect.
The hide crosshair is working on mine, I am not sure why, but if I don't put a bool and tick the box it don't seem to work then, not sure why it was a bit of guess work to be honest.
Scene file attached. Please note it also has probuilder in it from the package manager inside unity.
To fix documentation error I uninstalled visual studio 2017 and ms build tools. Then I installed visual studio 2019, I was then able to generate the documentation fine.
I posted these errors somewhere in Discord. I am no longer getting the error unfortunately I don't have either the build tools or visual studio 2017 anymore just visual studio 2019 and everything now works fine (as I posted below) I do know, for people who develop game engines and tools like this in the past I know one person who got round issues like this by developing there product in the preview version as well so they were always one step ahead this way.
UPDATE: I now have sorted this by wiping everything visual studio related from my system then installing visual studio 2019 with all .net versions and now it works fine. The issue still remains with 2017 though I think.
I am currently having this issue. I have discussed it in great length on the Bolt discord under #bolt-beginner-help I have tried fresh installs of everything including unity, as well as setting up a brand new blank project in unity each time. I currently now have the build tools and visual studio 2017 installed on my system. Before the release of 1.4.4 on v.1.4.3f2 it worked fine with just visual studio 2017 installed on my system. As a way around this on your end, I can't see how you develop bolt, but would an idea be to set it up as a relative I think its called, path then add an environment variable or batch file to search for the right path as well? Or is this not something wrong with 1.4.4 is it more due something on my own system I am missing? If you check #bolt-beginner-help on the discord server you will see over a 24 hour period how I tried to resolve this issue, it is very difficult to collate everything I said including the screenshots here. Please note I am not using Visual Studio 2019 at all on my system neither have I ever installed it.
Customer support service by UserEcho