testing

testing

Shanii2
Collaborator Collaborator
1,111 Views
6 Replies
Message 1 of 7

testing

Shanii2
Collaborator
Collaborator

The test level feature is taking to much time loading the test. even though its not loading all the resources and only the ones of the current level.. aalthough level a simple test level for prototyping.. Is this is normal for new release or are their any settings that needs to be configured

 

Reply
Reply
0 Likes
1,112 Views
6 Replies
Replies (6)
Message 2 of 7

__ben__
Alumni
Alumni

We do not expect any performance regressions in the new Stingray 1.4 release.

 

Launching the basic_project level takes about three seconds on my system, an i5 laptop with a SSD hard drive. What are your approximate system specs and roughly how long does loading basic_project take?

 

Regards,

 

Ben

 

Reply
Reply
0 Likes
Message 3 of 7

Shanii2
Collaborator
Collaborator

 here are my specs.. I had 4gb Nvdia 920m series gpu. with 8gb ram.... i observed that new updates of nvidia is causing lot of trouble.. and that in v1.3 i just cant test the level anymore.. when i downgraded then it worked. out but now with  new update and in newer version.. it just uses 100% cpu on test level and it takes forever to load. although i end the session my self. but. what could be the problem exactly.. does downgrading again to a bit older version would work. 

Reply
Reply
0 Likes
Message 4 of 7

__ben__
Alumni
Alumni

Are there any suspicious messages in the log window after the level finally launches?

 

 

Please try closing Stingray and then clearing the cache by deleting the folder:

 

C:\Users\[your windows username]\AppData\Local\Autodesk\Stingray

 

Also, create an entirely new project from the basic_project template instead of using your existing project.

 

Failing that, in the absence of any obvious problems, please do try downgrading to an earlier version to confirm that the current Stingray 1.4 release does not contain a regression related to your configuration.

 

Regards,

 

Ben

 

Reply
Reply
0 Likes
Message 5 of 7

Shanii2
Collaborator
Collaborator

Thanks. alot i worked it about..  And this Ill show the solution how i did it..

Apparently  the new driver updates On Nvidia are directx12 supportive.. but it seems its not much picking up heavy applications working in directx11. which is one main problem in latest releases. 

Ive downgraded my driver upto before 7 july. and which was the last driver update at which stingray was working properly. without unnessary. memory leak and high cpu usage.

For all those who might came across i would suggest to downgrade the nvidia drivers untill you get perfect and balance fit . and to resolve high CPU. by keeping the stingray editor to use Nvidia GPU.. make sure that adapter index is set to '0' to use default set gpu.. it will take some ram and cpu usage on starting up project and on test level. but the cpu usage wont be high consistent....  by keeping un nesassary applications off. 

Reply
Reply
0 Likes
Message 6 of 7

__ben__
Alumni
Alumni

Which version of the nVidia drivers worked and which failed? I'll pass that information to our QA team who can determine whether there is an issue within Stingray. 

Reply
Reply
0 Likes
Message 7 of 7

Shanii2
Collaborator
Collaborator

Well i believe it was version 368.22 Nvidia 920m series driver . then after the latest release at july 7 and onwards. the stingray perform well. in its default nvidia:gpu and cant test the level as well. i believe it was the earliar support of directx12..  but now its working fine though. but its not perfect solution as new release v1.4 there's significant drop in framerate.. at average level working containing terain with textures it was near 52-55fps. but now in same situation it droped to 25-30fps. propably because ive downgraded my drivers long way to before july...

Reply
Reply
0 Likes