평점 만점의 리뷰가 11,000개 이상
8만 5천명 이상의 리뷰
10만명 이상의 포럼 멤버가 선호하는 에셋
유니티에서 모더레이팅하는 모든 에셋
1 - 10 / 54개 표시
사용자 리뷰
정렬 기준
T
fkdup my project
2 months ago
TuffCookie버전 4.4.4
i know i am not using the right version but i didn't expect this depricated for Unity 6 version to fuckup my project this bad, i cant even remove it, i will probably start new project, that so annoying
이 리뷰가 도움이 되었나요?
0
2
퍼블리셔 답변:
2 months ago에 답변됨
It is always good to have source control to store the state before any change. It is not deprecated for unity 6, just there is some apis that unity plans to change, but there is no exact decision on that part yet. What exectly the issue are you having, I recommend reaching me via discord I could help you.
I needed an upgrade from units NavMesh system, since agents weren't properly avoiding each other for my RTS game. This integrated and worked perfectly. It was also well documented and had great examples.
Best of all, I encountered an issue at 3am on day, and the dev gave me a solution within minutes of my post. I'm lost for words on how awesome that is!
이 리뷰가 도움이 되었나요?
0
0
No complaints about features or performance.
Support is fine, also.
=====
OLD REVIEW
=====
If you can't wait weeks or months for him answer simple questions, don't buy.
I asked him simple questions on Discord and months, I'm still waiting for response.
이 리뷰가 도움이 되었나요?
0
0
퍼블리셔 답변:
10 months ago에 답변됨
Hey,
Sorry to hear that. Maybe your question got lost in Discord, since I get a lot of them each day. Feel free to poke me again if that happens.
t
Great asset - does what it says it does.
a year ago
titch_stewart이전 버전 4.1.1
This is exactly what I needed for combining NavMesh and Dots. In addition support was great. I had an issue getting the samples to appear in Unity 6 and Lukas helped me resolve it very quickly.
이 리뷰가 도움이 되었나요?
0
0
w
very good
a year ago
wechat_os_Qy03Bweq-YW3izcXJNY7zbB8k이전 버전 4.1.1
Thank you, the issue was resolved using the old version created by the author, which provides excellent support
이 리뷰가 도움이 되었나요?
0
0
퍼블리셔 답변:
a year ago에 답변됨
Yes you go into UPM versioning hell here, I am sorry to hear about that. So solution is quite simple here what you can do is bump Rukhanka Animation System 2 package version dependency from 1.0.16 to 1.3.4. You can do it by opening the package folder there should file called `package.json` and modify the line with `com.entities.graphics` with version 1.3.4.
I hope it helps, if not I could look into alternative of downgrading version from my side (I also sent you in DM downgraded version). I personally want to avoid this path as it means the hybrid users would have older version of ecs out of the box with less fixes. I hope it helps, let me know, if there are still issues for you.
H
Excellent pathfinding solution
a year ago
HeronHuang이전 버전 4.0.15
A highly excellent pathfinding solution that perfectly adapts to ECS and Hybrid modes, highly recommended for purchase.
이 리뷰가 도움이 되었나요?
0
0
How does your asset achieve dynamic obstacles in the navigation grid in the ECS system? I don't want to use Agent Collider because it has jitter issues. In my scenario, I hope to implement a feature where there is a wall that, once destroyed by bombing, monsters can pass through.
In addition, if there are multiple different NavMesh Surfaces, the NavMesh Agent based on MonoBehavior can cross the navigation mesh through the Wrap function. However, does this feature support the functionality of this asset?
이 리뷰가 도움이 되었나요?
0
1
퍼블리셔 답변:
a year ago에 답변됨
Hey, for this case you can use unity navmesh carving feature. Etc then you add Navmesh Obstacle with carve flag one. For different surface crossing I recommend using the navmesh links. Also for the different surfaces u can use different agent type and simply move transform that will archieve similar to Wrap funcionality.
This is almost perfect. Easy to understand, easy to extend. I learned a lot about DOTS just from reading the code. My only issue with this asset is that it allocates a lot of garbage. At least in my use case - I spawn and destroy a lot of units often which causes frequent TransformAcessArray re-allocations. My target platform is mobile so I'd prefer to be as close to zero GC allocs as possible. Other DOTS assets I use work around the same problem by using TransformAccesArray's RemoveAtSwapBack() and Add(). Hopefully something similar will eventually be implemented in Agents Navigation, too.
이 리뷰가 도움이 되었나요?
1
1
퍼블리셔 답변:
a year ago에 답변됨
That is really good suggestion. Could you reach me out in discord about it. I could look into it.
Quality assets
Over 11,000 five-star assets
Trusted
Rated by 85,000+ customers
Community support
Supported by 100,000+ forum members
