Forum Discussion

4 years ago

No shadows on Parallels Desktop on M1 Pro mac

Hiii hope someone can help me out. I own a Macbook Pro M1 pro and I run Parallels Desktop 17 with Windows 11. The game runs amazing and smooth but they have no shadow (see screenshot). It runs better...

mac

technical issues

NykoIaz

2 years ago

Thank God I found this!

But whenever I edited the graphics files, found the vendor name and changed it accordingly in the GraphicsCard.sgr files, the TS3.exe would not launch, and causes an Access Violation error, according to the xcpt error files.Then, my Device Config.log file would be completely emptied, with no words in it at all.

Can anyone help?

These are my device config, GraphicsRules and GraphicsCards are attached.

puzzlezaddict
Hero+
2 years ago
@NykoIaz Please try using each of the edited files separately, to see whether the problem is one of your edits or just the fact that you're changing the files at all.
- NykoIaz
  2 years ago
  So I did a little testing. The problem is the rules added to GraphcisRules.sgr. It prevented the game from starting. So I changed it here and there, following the advice in this thread, Now my game will start, but the options.ini and DeviceConfig.log are empty. Meaning the rules did not make the game recognize my GPU.
  A quick tour of reddit tells me that this is because of a corruption of the GraphicsRules file. So this means that the rules doesn't work for me... I must have done something wrong...
  - puzzlezaddict
    Hero+
    2 years ago
    @NykoIaz Start over with the default GraphicsRules file, and test the game to make sure DeviceConfig populates. Then only make the recommanded change to VRAM (called texture memory), nothing else. For reference, it's changing this:
    
    if ($textureMemory == 0)
    seti textureMemory 32
    setb textureMemorySizeOK false
    
    to this:
    
    if ($textureMemory == 0)
    seti textureMemory 1024
    # setb textureMemorySizeOK false
    
    As in, you're changing the 32 to a 1024 and putting a # and space in front of setb. The idea here is to make an edit known to be acceptable, to see whether the problem is the edits you're using or the fact that you're editing the file at all.
    
    DeviceConfig should still populate and should list your card as Found but not Matched, since the device ID will be in GraphicsCards but not in GraphicsRules.