majortom100967
Member
Hi.
I apologize if this argument has been already discussed (I didn't find anything through Search option) or of any interest.
As an Apple's fan and technician since 1992 I bought for testing a Mac Mini 2020 M1 with 8 gbytes of RAM and 256 of ssd (the later is of secondary importance). Please mind that I also own an Imac 27" 2020 64/512 with AMD 5500xt. Therefore the comparison is not very right (low level Mac vs high lebel Mac) but this are the Macs I have and for these I can say.
I'll go directly to the end: the M1 MacMini is really impressive. I knew that the unified memory architecture and ARM CPU's where great but I didn't imagine such a performance at 360° and especially in TRS19. Some numbers: Mac OS Big Sur in idle is around 4-4,5 gbytes of ram occupation; after loading TRS19 is 6-6,5. Great and very fast memory swapping (the internal disk is very fast by it's own, by the way).
The overall performance at 2K is impressive and looses a 20% at 2,5K (as you know 4K is no more available, so I can't test). Everything is more smooth than on Intel procs (either on Mac OS or Bootcamp/Win 10). Enhancing quality settings has less impact on performance than on the iMac. If this looks normal because is just at 2K I underline that is only an 8 gbyte machine and handles OS, game and graphics memory like a charm.
These are the settings:
- shadow quality medium
- main shadow resolution: 2048
- shader quality: standard
- texture detail: high
- post processing: high
- water quality: high
- detail scenery: clutter only
- AA: 8x
- detail update rate: ultra (as I don't enable back objects drawing, I want a fast drawing)
///
- maximum draw distance: may vary between 4 and 15 kms depending on the scenario (normally 4-8). The Sebino Lake scenario (20 min from my home, by the way) with 15 km distance drops the frame rate to 20-25 fps. It's nornal also on the iMac. But this is a scenario which needs a long distance, IMHO. For comparison, all Niddderbaltan scenarios (which don't need al long distance view -> 4 Kms) rarely run at less than 45 fps.
- scenery detail: high
- tree detail: ultra
- post processing high
Concluding: I'm far more impressed than I though and I'm confident (and hope) an eventual SP4 version could bring further improvements both in the code and in the Metal implemetation.
Cheers
Simon
I apologize if this argument has been already discussed (I didn't find anything through Search option) or of any interest.
As an Apple's fan and technician since 1992 I bought for testing a Mac Mini 2020 M1 with 8 gbytes of RAM and 256 of ssd (the later is of secondary importance). Please mind that I also own an Imac 27" 2020 64/512 with AMD 5500xt. Therefore the comparison is not very right (low level Mac vs high lebel Mac) but this are the Macs I have and for these I can say.
I'll go directly to the end: the M1 MacMini is really impressive. I knew that the unified memory architecture and ARM CPU's where great but I didn't imagine such a performance at 360° and especially in TRS19. Some numbers: Mac OS Big Sur in idle is around 4-4,5 gbytes of ram occupation; after loading TRS19 is 6-6,5. Great and very fast memory swapping (the internal disk is very fast by it's own, by the way).
The overall performance at 2K is impressive and looses a 20% at 2,5K (as you know 4K is no more available, so I can't test). Everything is more smooth than on Intel procs (either on Mac OS or Bootcamp/Win 10). Enhancing quality settings has less impact on performance than on the iMac. If this looks normal because is just at 2K I underline that is only an 8 gbyte machine and handles OS, game and graphics memory like a charm.
These are the settings:
- shadow quality medium
- main shadow resolution: 2048
- shader quality: standard
- texture detail: high
- post processing: high
- water quality: high
- detail scenery: clutter only
- AA: 8x
- detail update rate: ultra (as I don't enable back objects drawing, I want a fast drawing)
///
- maximum draw distance: may vary between 4 and 15 kms depending on the scenario (normally 4-8). The Sebino Lake scenario (20 min from my home, by the way) with 15 km distance drops the frame rate to 20-25 fps. It's nornal also on the iMac. But this is a scenario which needs a long distance, IMHO. For comparison, all Niddderbaltan scenarios (which don't need al long distance view -> 4 Kms) rarely run at less than 45 fps.
- scenery detail: high
- tree detail: ultra
- post processing high
Concluding: I'm far more impressed than I though and I'm confident (and hope) an eventual SP4 version could bring further improvements both in the code and in the Metal implemetation.
Cheers
Simon
Last edited: