Auto Select - Satellite Modes.

I also noticed that SatIQ or Autoselect mode was less accurate. I mostly just use the "all the stuff I paid for setting" if I record activities. I have a GPS only activity but that's just to log coordinates I later add to my photos, basic GPS logger function.

Garmin isn't really telling us how it works (how often does it check if another mode is better for example, could be everything between once in the beginning or every seconds, we don't know).

So tried it, wasn't satisfied, will never use it again.

If you are on GPS, you will have a bad pace. 
If you are on Multiband you will have an ok pace. 

When using Auto you will switch between bad and ok pace. 
That’s the way it works. This setting is to safe battery and not

for max accuracy. 
If you want max accuracy you have to use the Multiband option

the whole time. (Or also use an footpod for a good pace display)

When the watch recognizes that the GPS is getting worse and has to switch to Multiband, it has to get a fix first. There is no seamless switch. You will always have a time slot with not so good reception. 

I agree with you there! Because we have paid the greater expense for a watch that has greater a functionality than the rest of the series, I want to use all of the additional functions. I also like to explore the settings to optimise the user experience but this doesn't seem to be an issue that many are discussing on the relevant forums! 

Re: SatIQ/Autoselect modes

It was one of the main selling points for the 7X SS. 

My previous Garmin model was the Instinct - Tactical Solar Edition. That model had no multi-band functionality and could only select between GPS, Galileo and Glonass manually. I never experienced any pacing issues and used that watch extensively! It's disappointing that the autoselect/SatIQ on the Fenix 7 offers such poor data measurements rendering it practically unusable.

There was some discussions when this was a new feature (probably in the beta forum too). Guess now there is just simply not much to add.

SatIQ seemed to work quit good with 9.33 for me. since 10.44 (went from 9.33 to 10.44 directly) I observe those pacing issues too.

While this is correct:

AgentMax said:

There is no seamless switch.

..the implications never were so intense, that I observed it with 9.33 thus I always left device on SatIQ. With 10.44 now I use the all you can eat mode b/o the quality difference to SatIQ is way more observable with 10.44.

I have a case at Garmin open concerning another GNSS related issue,

forums.garmin.com/.../t7ab-update-9-33---10-44-dual-grid-mob-w-o-data-maps-working-ciq-gps-apps-working

maybe there is a connection.

Let's see, what the solution will be and if it will help with other GNSS-related issues as well.

Erik T7 said:

forums.garmin.com/.../t7ab-update-9-33---10-44-dual-grid-mob-w-o-data-maps-working-ciq-gps-apps-working

I have also observed the same issue within the past few weeks. 

The 'SatIQ' must be obtaining the correct data due to the fact that the average pacing remains correct throughout the duration of the activity, I cannot foresee this becoming a persistent issue and hopefully it will be rectified in the next software update. 

If you have the same issue you should open a case with Garmin support. When I did so there was no other case known worlwide with this issue which makes it difficult to sort out.

Also please send Garmin - Chis a PN (https://forums.garmin.com/user/conversations?New=True&UserId=194571) with this issue. He is our outpost towards development and this may help him to prioritize the problem.

The average pace isn't calculated by averaging the pace. It is calculated from the total distance and the total time, so it would always be correct even if when instant pace is completely wrong.