...
Hi.
Did you guys receive the scene? I was wondering if you got the same outcome.
Hello lupaz, yes we received it, thank you very much. We are currently investigating it but we are unable to reproduce the slowdown in Corona 4. My colleague even stated that: "(for me) it was the other way around - when I tried IR on the included scene with Corona 1.5 it was very laggy and sometimes it didn't even show anything in the VFB. When I tried the same scene, but with Corona 4 everything worked well and smoothly."
Please what hardware do you use? Do you have some plug-ins installed? We want to test it with the same plug-ins installed to try to find out, if they could cause this slowdown.
Hi Selene,
3Ds max 2016, Win 10.
Ryzen
Plugins: Too many to even know. But some of them are Itoo Railclone and forest pack.
Hardware as from Sys info:
OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name RYZEN-1800X-TAI
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD Ryzen 7 1800X Eight-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P2.40, 4/10/2017
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASRock
BaseBoard Product AB350 Pro4
BaseBoard Version
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume5
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.387"
User Name RYZEN-1800X-TAI\mrpep
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 32.0 GB
Available Physical Memory 23.1 GB
Total Virtual Memory 51.0 GB
Available Virtual Memory 37.2 GB
Page File Space 19.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes