![]() |
1 Attachment(s)
Still buggy
|
1 Attachment(s)
misses 1/2 ram in my system
|
hmm, I give up then on this one.
|
Why not focus now on GPU generation detection?
|
Ok, the problem will be the intel graphics,
I can detect ATI and nVidia. ATI HD 4xxx is SM 4.0 and DX10 ATI HD 5xxx, 6xxx and 7xxx is SM 5.0 and DX11 Nvidia 6xxx, 7xxx 8xxx, is SM 3.0 and DX9 Nvidia 9xxx, 2xx is SM4.0 and DX10 Nvidia 4xx, 5xx is SM5.0 and DX11 Nvidia 6xx and titan is SM5.0 and DX11.1 |
Intel must be marked as unsupported in most cases.
|
Darn, i just noticed that the previews iss your provided that detected the CPU cores has the same ram issue, looks like we will revert to the original version until all fixed.
|
it will be easy to fix the cpu detection but will leave ram for now.
|
Not sure if you got me but the old script has a ram detection issue, it's detecting one stick out of 3.
|
It was a test update, I reverted the changes, ;)
|
Actually i've tried the initial release of yours after the unicode fix and it has the same issue, it's either a bug of the fix you did to make it work with unicode or the script is already bugged by the original developer it self. not sure :/
|
oh, you mean that.
The RAM Detection method used only works on 2GB Ram and nothing more, I guess, the thingy will have a dll file after all. Thanks for noticing. |
I think i will forget about it meanwhile.
|
Can you teach me how to use the CIU is not, when I created using png and bmp, when it was at fault for the button to install the repack of my
|
Hello,
How to compress files inside packed file? i mean let's say i have a .pak file and this file contains lots of files inside, if i unpack it then compress it i will get a higher compression ratio, if i compress the packed file i get less compression ratio. How to tell freearc or srep to detect those files inside the pack and compress them properly with having to unpack the file? |
| All times are GMT -7. The time now is 15:11. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com