Win10, VisualStudio w/C4D as background process?
-
On 11/11/2015 at 13:16, xxxxxxxx wrote:
User Information:
Cinema 4D Version: R16+
Platform: Windows ;
Language(s) : C++ ;---------
While I can simply open the Task Manager and kill it, is there any way to stop Windows 10 from adding Cinema 4D as a background process (I imagine for startup speedup after it sees it being opened a lot)? When it does this, Visual Studio, for some reason, will error out on the build. Cinema 4D is not listed in the Settings->Privacy->Background Apps. Nothing critical - just annoying interruption of my development.
-
On 11/11/2015 at 23:54, xxxxxxxx wrote:
Originally posted by xxxxxxxx
<ADDRESS>
User Information:
Cinema 4D Version: R16+
Platform: Windows ;
Language(s) :
C++ ;---------
</ADDRESS> While I can simply open the Task Manager and kill it, is there any way to stop Windows 10 from adding Cinema 4D as a background process (I imagine for startup speedup after it sees it being opened a lot)? When it does this, Visual Studio, for some reason, will error out on the build. Cinema 4D is not listed in the Settings->Privacy->Background Apps. Nothing critical - just annoying interruption of my development.Strange - we don't use any of the background APIs and don't use a manifest to declare Cinema 4D as background app (which should be the only way to add a background process). Do you use VS 2015 or 2013?
Best regards,
Wilfried
-
On 12/11/2015 at 13:28, xxxxxxxx wrote:
I am using VS2012 with the R16 SDK. I've been trying to recreate the circumstance to post the exact build error but to no avail. Probably a fluke thing. If it re-occurs, I will save the error to be more thorough.
-
On 13/11/2015 at 01:46, xxxxxxxx wrote:
it happens here too, VS2012, win8, R16
Cinema4D is added to background processes "totally random".. -
On 13/11/2015 at 04:15, xxxxxxxx wrote:
I sometimes have the same problem, but for me it seemed related to Team Render. It doesn't occue when TR is disabled in the prefetences.
I also always thought that it would be the very same process which already has all GUI closed but won't actually end/terminate.My guess was that TR tries to reach the clients to inform that the server shut down, since, as far as I remember, it didn't happen when the only
client in my TR machine list was available. -
On 13/11/2015 at 06:28, xxxxxxxx wrote:
Team Render is disabled in my preferences. Still no idea.