[RELEASED] uTire Dynamic Tire Deformation V2

1. Out of the box it isn't, however adding support for third party wheel solutions is super simple as long as the wheel collider can be resized at runtime, and its radius is available. It's a couple of lines of code, the bulk of the calculations are done automatically.

2. physics-wise tire pressure just determines the wheel collider's size, the deformation is 100% visual, it won't affect physics directly(apart from the fact that the smaller wheel collider will behave somewhat differently). So even though I'm not sure I understand what you mean by drive on top of the wheels, but I can say at maximum tire pressure it's going to work exactly the same as it does without uTire.

Did you import NaughtyAttributes before uTire? This is a completely free, 3rd party tool for managing custom inspectors - I'm guessing some code fails to compile, and therefore "missing". The first update will address this issue - will prompt you to import it if it's not peresent.
You can get it from AssetStore, or directly from their github.

 

Sorry for the late reply. I did import Naughty Attributes before uTire.

 

For Glaucos, it's like the original wheel collider but with bools and modified friction. With WheelColliderS, it does have radius and width, but the collider's center is at the suspension start point. Would the position of the center affect how to aline uTire's radius. Also what I mean by drive on top of the wheels, I mean't like have collision on top of the wheels and not going through an obstacle.

 

Hello, what happens if the device doesn't support Shader model 3.5? Does the app crash or it keep working without the deformation?

 

I’m getting error on 2020.3.22f1

 

@newlife I can't test it now, but my best guess is it would show up pink - it definitely shouldn't crash. Best way to handle this is to provide alternative shaders and switch based on what's available on the target hardware.

@fredastaire this isn't uTire related, make sure you have the correct version of Collections (0.9.0-preview.6 or up) and also Burst 1.3.0-preview.12 or up imported. Mathematics 1.2.1 is fine. I just tested it on 2020.3.36f1(latest LTS), it works without any console logs.

 

Thank you very much for free upgrade from V1. It is looking GREAT!

 

ya I was getting the same error in 2020 and 2021, if you use another jobs version, you will get runtime errors all over the place related to v2 tire. .. So, there is something going on related to jobs possible bug or something out of date here.. b

When I get some free time I plan to dig into this myself, But your not the only one... I tried on 4 new projects just to make sure it was not my project, Math, Jobs, collection burst all update to date, I tried other versions of each as well...

Unity prolly screw something up in jobs by looking at that error. Since V2 relies on it, it won't be usable right now. if someone found a quick fix for 2020.3.36 and 2021.3, let all of us know.

Other wise when I get free time, I will dig into it.. I have tried every version of jobs some older versions where better. So, it may need to be set up for older version of Jobs, until, Unity fixes the newer versions.. That is my guess with out digging into it.

 

Math 1.2.1, I tried new version too. burst 1.6.1 collection 1.2.4 0.2.10 jobs. if you , use anything newer, it will cause runtime UV2 tire errors . to many to list, but all in the runtime script.

You need to use older version of Jobs, if you update you will get all sorts of errors, the developer may want to try this as well... curious what version of jobs, and other plug ins he has installed, version wise. 2021, is even worse..... with errors.

Curious how the developer got it working in the same Unity version.

https://issuetracker.unity3d.com/is...nmanaged-structs-as-containing-nullabe-fields

ya as I thought, Unity bug, awesome they claim its fixed in 2021.2, its not... I tested in 2021.3, its still broke..

going to ditch UTire, v2 for now, and go back to my old way using sims.until Unity fixes this crap.. in the next few years.:

 

@Recon03 can you send me an example of this issue please? The pretty much empty project I'm using to upload to the store has the following versions(I realize these aren't the latest for these packages, however they are newer than the ones you listed). Running on Unity 2020.3.36f1, no errors whatsoever.

• Mathematics 1.2.5
• Collections 1..2.3-pre.1
• Burst 1.6.4
• Jobs 0.50.0-preview.8

I'm going to update everything to the latest and fix any potential errors that surface.

 

I pretty much explained it, as the other user, that error pops up, in that version of Unity, older versions its does not. I tried with many new projects just to make sure it wasn't project related. I tried every version I could use for Math, Collections, Burst, jobs, some gave different errors, but the ones you listed did not.

Now, this is something Unity reported as a bug on there end and said they fixed it, its not fixed. , which is why I posted about it. I ended up using the V1 instead, since V2, i'm unable to get that error fixed no matter what I do. my TIME is limited as it is, as i'm a professional developer so I'm working on other things, so I been unable to spend anymore time, which is why I added V1.. So not sure what other info go provide for you than I already had.

I do believe this is related to jobs though, not on your end.. if you got it working. plus This has been reported and is the error I got with every new project I tried over 10 new projects I had tried on. They all got that same error. The other user also had this.



https://issuetracker.unity3d.com/is...nmanaged-structs-as-containing-nullabe-fields

 

fixed.. So, newer versions of jobs, and collections, will break it... So, you have to use

Jobs 0.50.0-preview.8 must be used all other versions broke it and you would not get any other errors. Until you make sure this is installed.




When you do, you will see Naughty Attibutes errors.. ( I honestly never heard of it until today.) So I googled it and notice you are using this for your custom editor. So, I had to download this on its own. Those errors would of never came up, if I didn't use older versions of jobs, etc.

https://assetstore.unity.com/packages/tools/utilities/naughtyattributes-129996

So you may want to make this clear to users. ( Not saying its your fault) but I didn't see this on your docs either.. ) I checked a few times for things needed to download.(free asset on the store) so I recommend to add it to your docs.... SO we know that it was needed in order for it to work... I used Unity a for years and never heard of it..


Its working after some digging into it more. a bit of a hassle though.


by the way this is for 2021.3/2020 versions. people will want to use new jobs, etc...So something that needs to be looked into and can't. So if someone wants this asset to work, they will need to use older versions of jobs for it work. . Unity claims its fixed in 2021. well its not. ..Fixed in 2021.2.X ..... Unity its not.. I reported it to Unity though, others with the issue should do the same...

 

I have fixed that issue, so follow what I said above and it will work for you as well.

 

@Recon03 The dependencies are listed on the store page under the Package Dependencies tab and on the bottom of the Technical details tab as well, where I provide an AssetStore and a Github link for NaughtyAttributes - however NaughtyAttributes won't be required for long as I'm in the middle of rewriting the UI.

Jobs is still under development so incompatibilities are bound to happen every now and then, it's just a nature of using in-development code(regardless of how production-ready it is supposed to be), but this isn't a dead end, Unity's API changes rarely require a ton of work to adapt to - the only reason it's not fixed yet is because personally I don't use anything but LTS versions of Unity, so simply I wasn't aware of the issue(also I'm not active on the forums lately, but I tend to respond to support emails in a matter of hours).
In the following days I'm going to update every package to the latest version on the latest LTS and see what needs fixing.

 

Ya, I bought V1, so, I have not went to the store since V1, nor needed to, typically I look at Docs. So, I would recommend in the future to add it there. Also Unity asset store sucks, its hidden.. So if your adding to the store only, users who used the old version won't know, I don't live on the asset store i'm busy developing, so. Please, in the future like most developers, just add to docs.

So just saying make it more clear, is all. Since you had two support posts in a row with the same issue......



but like I said those errors for that would of never came up, for most users, they would assume the asset is broke, due to new jobs versions... this asset only works with that one version only... So, I would also add that to your docs and tech info for now. ( not your fault) but to help support and so users don't waste time.

Thanks.

I'm a professionally developer for 30+ years so aware of the nature for programming, API's and Unity..

, which is why if you read I didn't blame you for the Jobs issue...... Gl

I only use LTS versions, IE 2020.3, and its broke with new jobs.. as myself and others reported, but this is a Unity issue, as I said a few times now.

Anyone developing should only be using LTS versions... This is something I promote to all developers I would mentor and advise today and in the past.. I don't use beta versions or Alpha, or even releases that are new, I tend to stay back a few versions since Unity cant release anything worth a S*** , since Unity 5.


Unity don't make games, so they have no idea what they are doing, so things break more than normal.. Which is why I use other game engines more for professional work these days... Unity is a nightmare.. I used to make a great living fixing Unity issues for companies..

Ya, I would give the asset when you have time another look. for the current LTS versions.

Those are the issues I found, and reported them. users can how ever get it working with what I said though .,.

Also your GUI, for the testing of the example scene is missing by the way. in V2, figured to let you know, there is nothing there it says you should be able to adjust the value in the GUI, but there is nothing.

. Not a big deal for me, as I used this since V1, but some new user may be annoyed by it.


PS:its rare I come to the forums myself, I cant stand Unity forums.... or the asset store itself. I rarely buy anything anymore.... I rather just in a project and work, so if you do anything in the future that is required, just please add it in the docs, it will save support questions and hassles for you and all of the users.

Most assets I own, I own different ones and many I never ever asked any support questions, its rare, I tend to figure it out myself. Yours was a bit tricky, at first until I got a better look and you shared the jobs version you had working.

Thanks for your replies.

 

@Recon03 I'm not arguing with you, I'm just looking for a way to reproduce the issue on my end so I can fix it. I just updated to latest LTS versions for both 2019 and 2020, and apart from a non-related error in 2020(No Cloud ProjectID Found for Analytics) it run perfectly fine as is.

2019.4.40f1

• "com.unity.jobs": "0.2.10-preview.13",
• "com.unity.mathematics": "1.2.6",
  
• Burst(according to the package manager) 1.3.0-preview.12 May 07, 2020
• Collections(according to the package manager) 0.9.0-preview.6 June 16, 2020

2020.3.38f1

• "com.unity.jobs": "0.70.0-preview.7",
  
• "com.unity.mathematics": "1.2.6",
  
• Burst(according to the package manager) 1.6.6. June 08, 2022
• Collections(according to the package manager) 1.4.0 August 02, 2022

I'm not sure how to proceed from here to be honest, can you share the exact Unity version along with the packages you are having trouble with?

Your point about mentioning the dependency in the documentation is completely valid, frankly I thought the reason the asset store specifically asks for dependencies is to handle them for the end user, but either way it should be written in the docs, no question about that. I'm going to submit a version soon which doesn't rely on NaughtyAttributes, moving forward this is not going to be an issue - but again, I'm sorry for the unnecessary trouble.

 

Ya not trying to argue with you either. but making it clear so you know what is going on, rather than not telling to proper info..


There is nothing you can do. but make it clear in the docs, its on Unity end. Which is what I was trying to say, but since its your asset, and you don't want support issues as myself and someone else did, thankfully i'm a professional developer, I do this for a living and was able to find the issue as i'm used to Unity's lazy, buggy crap... over the years of working with hundreds of clients and my own projects.

but many users don't do they will just give you a bad review since it don't work.... even though its really not your fault. So this way you can send them a fix... or point to this thread .... better to add to docs, so the user knows.

So, just add this on your docs, is all i'm saying. I was trying to do your a favor, by rather than just fixing it and ignoring the other user having a problem, and you seem to not know, I took the time to look at it further, to see what the problem was..

This is the fix and the problem for that other user and anyone else who may use the new jobs version. or may miss the UI editor tool..


Also, not sure your experience, but I worked with thousands, and just because you don't have the issue, don't mean others don't.. . if that was the case, I would ignore 80% of my support tickets for some of the larger companies I had worked for..... So, when you have more than one person reporting the same issue, you have two choices.

Say I can't reproduce it and they continue to not be able to use your asset, and be pissed off give a bad review since they can't use , or send them a fix, on some known issues reported by other users. You can decide its your asset.

11 new projects was unable to work with new jobs version. Same error as the other user, so there prolly is others who just gave up. So just because it works for you honestly from experience really don't mean much. if I was the only one with the issue, then It would have to be on my end. But that is not the case.

So, simple fix, add known issue to your docs, if a user has that error, they can use the old jobs. That is what I would do, to save support problems and stuff like this. Anyways, I only posted to help the other user and in hope if you had other users with the problem, they aren't stuck on there projects with this same issue. Which happens alot with Unity, Unity assets, which is why I tend to try and help some of the next generation of developers.

Be well.

 

as far as this, typically when buying an asset you are correct, but many of us had V1, why would I want to baby sit, an asset I already been using and some times the store is down, so then I have to waste more time... a developer who does this for a living, time is money. . So, since the 90's I have seen proper docs. So Unity asset store to many assets are lacking, and get pissy when we give feed back about things missing. No idea why this is a big deal I knew that something was missing, due to my experience, many Unity devs, that are learning, would of had no idea what the heck was going on and just spammed your reviews with 1 stars... I didn't do that nor would I.. .SO not sure why this is even mentioned .


.. This is what I hate about Unity and the store, every asset developer is all over the place..... I'm a UX/UI Designer, programmer, being consistent is important in development, so those that do this for a living, don't want to search all over the place for info related to the docs. . and others have docs, it makes us not want to use any of them, I use way less assets since I retired, as they are annoying for this reason.....

But your statement would be valid, had I just bought V2..... but many of us didn't. You already had docs, so not sure why that was not added, so not sure the point to that statement. to be honest. I would of just added it and that would of been the end of that.


No reason to be sorry your human we all make mistakes. . I'm not the type to spam your emails with hate and 1 stars, just because of a mistake... Part of this isn't your fault anyways, it was more about making other users aware and your self, since two that we know of in a row had the same issue.

 

Hi, is there a detailed tutorial for the v2 setup, could not find one, thanks.

 

Im still interested in this but its got too many dependencies. Are they really necessary?

 

@Pecek This asset no longer works with NWH. There are compile errors due to some changes in NWH. Still after updating the code to support the current NWH, it does not work correctly.

In addition, there is a bug with Gizmos in Unity 2022.2. If you select a uTire runtime object during playmode it will scale to 0 very quickly. Only if it is selected. Commenting out the Gizmos code stops this bug.

 

Hi!

I just bought the V2, but couldn't make it work. I cannot use those specific Jobs version because I have other assets that don't work with that old version.

What can I do?

Thanks!