|
|
Post by antoripa on Jan 23, 2018 15:04:21 GMT
Hello. I am getting low perfomance. Below the profiler from a dev build. Using latest shooter template and there is only the player on the scene. If I enable the NPC ( around 20 ) is really worst. Been testing for 2 days and I cannot find something wrong at my end. What would you suggest ? Has someone reported similar issues ? Am I doing something not properly ? Scene has only a player moving in a maze
 image hosting website free |
|
|
|
Post by Invector on Jan 23, 2018 15:07:55 GMT
It's the AI sphere sensor they are really expensive on performance the bigger the value is.
We already create a new verification for the new AI v2.0.
|
|
|
|
Post by antoripa on Jan 23, 2018 15:27:55 GMT
Nice hear that you are working on improvement for AI. What is you ETA for AI 2.0 ?
But in the picture I am profiling with only the player.. I can see that you are using FindObjectOfTypes in the main update for few scripts In my humble opnion that is too expansive as eat around 2 ms for each monobehavior.. I have been not using your controller for almost one year so I would be sure that I am not doing something wrong at my end. Thanks a lot for your help
|
|
|
|
Post by Invector on Jan 23, 2018 15:55:48 GMT
If you open the tpInput, meleeInput or shooterInput you will see that the only FindObjectOfType is mentioned to find the tpCamera if it's null, so you probably forgot to add the tag "MainCamera" into your camera and the update is trying to find one.
|
|
|
|
Post by antoripa on Jan 23, 2018 18:38:08 GMT
If you open the tpInput, meleeInput or shooterInput you will see that the only FindObjectOfType is mentioned to find the tpCamera if it's null, so you probably forgot to add the tag "MainCamera" into your camera and the update is trying to find one. mmm . .nope . .cannot be .. and i double checked ... and again ran profiler but from the editor ...my workstation is pretty powerful and I would say that the build runs about 50 FPS .and of course i checked profiling what is the bottleneck .. ![]()  |
|
|
|
Post by antoripa on Jan 23, 2018 18:50:24 GMT
I was thinking that issue could be because 2017.3 .. I had a small issue with another TPC and solution was to change a rigidbody setting to cinematic ( up to previos version i left unchecked both gravity and cinematic for that case .. just to report my experience )
|
|
|
|
Post by Invector on Jan 23, 2018 20:43:10 GMT
antoripa can you try on 5.6.1 or similar? we do have some issues with 2017.1 and perhaps .3 is also on the list.
|
|
|
|
Post by antoripa on Jan 24, 2018 2:03:44 GMT
antoripa can you try on 5.6.1 or similar? we do have some issues with 2017.1 and perhaps .3 is also on the list. sure . i can clone the project and test .. i use the 5.6.1p2 for development as my support start from that version .. |
|
|
|
Post by antoripa on Jan 24, 2018 18:55:53 GMT
Ok . now perfomance for the player control are better I can hit 100 FPS in a indoor scene production like..
Still perfomance issue with the AI. But Invector is working to improve AI.
I am gonna open another thread about AI where I need support
I would say Invector TPC is a great asset
Keep up the good work
|
|
