Beta 21 High CPU

Noticing quite higher CPU main. Normally with an empty scene it would be like 2 or 3 MS on 4.6
But in 5 it's upto 14.5 to 15.2 in just an empty scene (with realtime GI and all disabled). or at least I think i disabled it through the lighting tab.

(Should I go back to the most tested version)? To at least make a little playable demo game?
Not sure if the versions make that much of a difference in things or not.

 

Main thing is WaitForTargetFPS at 95%.

I'm on a Windows 7 64 Bit, 8 gigs of ram, 2.4 Dual Core I3. Intel HD 3000.
if it helps, my dxDiag says I have 4 cpus (I don't know how when I have a dual core). But yeah.

 

Oh yeah the WaitForTargetFps is at 12.42 MS

 

Sounds normal to me, (its a laptop).

Perhaps my laptop just needs a break after 3 weeks of constantly being on lol.
(Sorry for wasting your time).

I'm just used to 4.6 giving a lower MS with an empty scene.
Maybe it's just the way things are set up now and stuff.
I've noticed a lot of different ways things are done, like changing the skybox and stuff.

But I'll try again later tonight when I wake up and see if I can do better

Thanks buddy!

 

Please look at this thread (probably same problem) : http://forum.unity3d.com/threads/high-cpu-consumption-with-no-explainable-cause.293645/

 

I didn't quite understand what I was supposed to do with that? I saw scripts that did a bunch of stuff like making cubes, but is there are barebones one?

Here is another photo, it's just one plane with Parrallax Mapping, nothing else.
Getting horrid results.



CPU Main 55.3 MS and 18.1 FPS at 55.3 MS.

On 4.6.1 I could still get like 19 MS and 40+ FPS.


profiler says Gfx.WaitForPresent is 95.8%

Edit - the profiler is also showing the Rendering is the highest, I guess that's what Gfx is, is rendering?

 

Try this :
- add an empty gameobject with the script in this post attached to it
- build a standalone player
- quit every app on you PC (including Unity and MonoDevelop or Visual studio)
- launch the player
- let it run for 30 seconds
- look at the log of the player (output_log in _data folder). You will get FPS and CPU stats
- post the log here

 

I really do appreciate you help!
I'll try it in a few minutes. And also where may I find the log at?
I've never had a reason to look at the log sense i've started using Unity in the past year lol.

 

here is my log

Code (CSharp):

1. Initialize engine version: 5.0.0b21 (e285fa5f42d9)
2. GfxDevice: creating device client; threaded=1
3. Direct3D:
4.     Version:  Direct3D 11.0 [level 10.1]
5.     Renderer: Intel(R) HD Graphics 3000 (ID=0x116)
6.     Vendor:   Intel
7.     VRAM:     128 MB
8. Begin MonoManager ReloadAssembly
9. Platform assembly: C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\UnityEngine.dll (this message is harmless)
10. Loading C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\UnityEngine.dll into Unity Child Domain
11. Platform assembly: C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\Assembly-CSharp.dll (this message is harmless)
12. Loading C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
13. Platform assembly: C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\UnityEngine.UI.dll (this message is harmless)
14. Loading C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\UnityEngine.UI.dll into Unity Child Domain
15. - Completed reload, in  0.062 seconds
16. desktop: 1366x768 60Hz; virtual: 3286x1080 at 0,-196
17. <RI> Initializing input.
18.  
19. <RI> Input initialized.
20.  
21. <RI> Initialized touch support.
22.  
23. Platform assembly: C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\System.Core.dll (this message is harmless)
24. Platform assembly: C:\Users\easy2own\Documents\R.H.D. - Run-Hide-Die\Scenes\TestScene_Data\Managed\System.dll (this message is harmless)
25. NtQueryTimerResolution success=0 currentResolution=10000
26. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
27.  
28. NtSetTimerResolution success=0 currentResolution=10000
29. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
30.  
31. 0.1 FPS
32. 0.0 %CPU
33. 1ms TIMER RES.
34.  
35. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
36.  
37. Setting up 1 worker threads for Enlighten.
38.   Thread -> id: 2c5c -> priority: 1
39. 36.7 FPS
40. 1.9 %CPU
41. 1ms TIMER RES.
42.  
43. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
44.  
45. 47.3 FPS
46. 2.5 %CPU
47. 1ms TIMER RES.
48.  
49. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
50.  
51. 47.3 FPS
52. 2.6 %CPU
53. 1ms TIMER RES.
54.  
55. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
56.  
57. 47.3 FPS
58. 2.4 %CPU
59. 1ms TIMER RES.
60.  
61. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
62.  
63. 47.4 FPS
64. 2.4 %CPU
65. 1ms TIMER RES.
66.  
67. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
68.  
69. 47.4 FPS
70. 2.1 %CPU
71. 1ms TIMER RES.
72.  
73. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
74.  
75. 47.4 FPS
76. 2.3 %CPU
77. 1ms TIMER RES.
78.  
79. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
80.  
81. 47.0 FPS
82. 2.2 %CPU
83. 1ms TIMER RES.
84.  
85. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
86.  
87.  

 

Well now it's Camera.Render.

But I don't see a GPU usage anymore (like in 4.6.1 Trial), all i see is CPU Usage, but I took pic of entire profiler.



{edit}

I mean most of the time I don't full screen Unity while testing game on my 1080P TV, but I do know in 4.6.1 I would still keep with Vsync around 30 to 40 FPS at around MAYBE TOPS 25 MS. But averaged around 18 or 19. So jumping from 18 - 19 to 53, bit difference lol.

(I just figured y'all should see this) just so you're aware. I mean maybe it's just my computer.
I was told before in the past that it's still should be the same system requirements though.

 

Oh I'm sorry!

Here is two photos - 1 profiler, 2 - what I am rendering.
Here it is now.

 

It's all just the Camera.

 

I just don't get it though, it's only one single plane, that's it. Even with no plane it's still just as high.

 

it just says Box001_Mesh 15.2%
and GPU is 12.263

 

Just the standard shader.
But then again (even with no mesh whatsoever) it's still high, however, I do know removing the skybox helps with a couple hundred frames (with Vsync) off.

 

Where may I find the editor log at?
I've never had to use logs before, so no idea where to find them lol.

 

@Tautvydas Zilys
I found it, I'll just upload it, it will only let me select Notepad and it's hard to read it with Notepad lol.

I think i noticed *failed* stuff.
(I had to zip it)

 

@Tautvydas Zilys Did you ever look at it?

 

Hey, well, these rates are coming from completely empty scenes, there are no (shaders) except what yall make of them for the Skybox and stuff.

I have posted 3 photos
Unity 4
Unity 5
Temperature stuff.









Again these are completely empty scenes,
the only thing(s) I have open are my normal programs (Fire fox and 3ds max and Paintshop Pro)
I ALWAYS have them running, 4.6.2 runs perfectly fine, well could be stronger if I had a better cpu lol. But yeah.

 

I've been searching and searching, apparently Sony VAIO doesn't allow users to change fan settings.
I've downloaded tools, I've went through the power and settings in control panel, it's just nowhere to be found.
Heck I don't even see it in the BIOS.

 

It went up just a little bit.

I'm averaging 48 frames at 20 MS.
Keep in mind all these tests are at 1920 x 950
(I'll never be testing or even playing games at that resolution, I just so happened to notice the difference, by mistake because occasionally I just do it to see something better and noticed that the game was running slower than normal.
You know, it's just one of them things if you do something enough you just can tell it's not *normal* feeling.
I'm not sure if it's that big of a difference from 48 frames(Mildly full scene) to 60+ frames.
I can just *feel* the difference.

or if it's even the FPS that's my issue, I wonder if it could be a more *underlying* issue causing this that neither the stats or profiler are picking up.

 

Oh your poor computer! Every night, shut down your computer properly, using the official method. Crap knows how many web page hooks and viruses are just sitting in memory. It doesn't take long to boot up, you can make a coffee while it's doing it. And run Malwarebytes occasionally or do virus scans.
Don't forget to update your graphics card drivers, if you can.
You know, at that normal sensible stuff.

 

I used to shut it down, until Unity stops saving my project and erases entire scenes as if they have never had an object onto them, I've tried reporting it, but like most of the time, you never heard back lol.
it actually just did it to me yesterday, I saved my scene 4 times (saved, resaved, saved a backup, saved backup again, then saved project 3 times to make sure) well little do I know, they are both completely empty, no matter if I save a scene 1 time or any other number, shutting down my cpu = 90% fatality rate of scenes. I can shut down Unity, but I just can't shut down cpu, I don't understand that one lol.

As far as I know it's all updated, but it can't hurt to re-check lol.
But who knows, it could just be the way it is, but as you said, Mobile devices will get better fps than this cpu lol.

 

Okay I know for a fact it isnt nothing to do with my PC.
Nothing but U5 running (updated my Gfx Card)

I decided to do a little test, just a flat terrain with a cube (thats it)
Well I put the resolution to 268 x 201 (FREAKING SMALL) lol.
I'm getting less than 40 FPS at 25.2 MS, I tried with grass it was 8 FPS lower. So Roughly 30 FPS with just a small
patch of grass.

(I mean I know this is a Beta and all)
But I don't want this to never be thought about again,
because lets get real 268 x 201 - That's like horridly small, can't even remember the last time I see something that small lol. It shouldn't have any problems whatsoever period ever rendering something that small.

Even tested at 244 x 183 (As small as it gets) I'm getting 42 fps. at 23.5 ms.

here is Image.


Now that my music is off, I can actually hear my fan speed up actually.

 

@Tautvydas Zilys
@Ostwind
I MAY HAVE FOUND THE PROBLEM!
It must be a bug with the Scene view and Game view, I just moved them around now I'm getting 100 / 200 fps at 10 MS.
(Which is more normal on my end looking, maybe a bit higher on U4, but all the extra stuff on here of course will make it lower).

Again took a photo.





EDIT - Also re-did the above posts test, now I'm getting 400+ FPS at smallest screen size at 2.2 MS.

It has to be a bug with the scene view and game view.
Because All I did was move them around and bam, it's acting more normal

 

Hmm interesting.

 

Hah I know right? It's working like a charm lol.
I did update my Gfx Card, played around with U5 for like an hour no change, than a few hours later I decide to mess around with it more, still had issues, but moved and resized the scene and game view (By mistake actually) and been working sense (scared to cut it off haha).

 

I've had a few times I suddenly got stuck at 8fps, then noticed the new lighting system was baking. 2 hours later it finished. I've disabled the real time baking still to bugged in beta. empty scenes shouldn't need to take hours to bake.

 

Heh yeah, well i was still expieriencing these problems with every virtually possible to cut off - off lol.
But now it's just working lol.

 

I have had the same problem here, and I believe that moving the tabs is not really a solution.
@N1warhead you filled a bug report? I think before we have a final release of Unity 5 this should be resolved definitively. Is being really annoying to use Unity this way...

 

No idea, I just know sense then it's been working like a charm.
It's spiked a couple times, but that was just from messing around with things.

No I saw no reason to file a bug report as it would happen with completely empty scene, what's to look at with a bad project if all I did was just hit the play button lol.

Unless I'm mistaken and it really does give them something?

But you are right, it truly was annoying, I had pretty much given up with Unity 5 ever working on this Laptop of mine, I decided to give it one last shot after going back to 4.6.1 at the time, and still didn't work, then accidentally move the tabs and started working.