![]() |
|
#1
|
|||
|
|||
![]() Quote:
[rts] ;0 -> all available cpus (default) ;1 -> execute only on CPU 0 ;2 -> execute only on CPU 1 ;3 -> execute only on CPU 0 and CPU 1 ;4 -> execute only on CPU 2 (quad core only) ;5 -> execute only on CPU 0 and CPU 2 (quad core only) ;6 -> execute only on CPU 1 and CPU 2 (quad core only) ;ProcessAffinityMask=2 Did not have any jvm.dll crashes anymore... really too early to tell, but looking good sofar. Please check if other get similar results. Rgs, FP
__________________
Intel Core i7 2600 @ default clocks MSI P67A-GD65A Motherboard Vertex2 SSD Raid1 1 Tb data disk 8GB DDR3-1600 MSI Geforce 680GTX @ default clocks Hotas Cougar X-Fi Music |
#2
|
||||
|
||||
![]()
I'm glad you posted that. I just learned that, all these years, I've been running on just one CPU.
![]() |
#3
|
|||
|
|||
![]() Quote:
![]() I didn't have any java crashes anymore tonight, so maybe's something is going on here. Although, some others reported it works fine when it's only associated with core 1. Afaik, il2 can only run on 1 core, but this extra dll can make a difference. Weird. Rgs, FP
__________________
Intel Core i7 2600 @ default clocks MSI P67A-GD65A Motherboard Vertex2 SSD Raid1 1 Tb data disk 8GB DDR3-1600 MSI Geforce 680GTX @ default clocks Hotas Cougar X-Fi Music |
#4
|
||||
|
||||
![]() Quote:
Promising... |
#5
|
|||
|
|||
![]() Quote:
I haven’t had the chance to really dive into the changes in the patch, but I like what I’ve seen so far and the only real issue I’ve noticed was the CTD. Thanks for all the hard work! ![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|