[edofloat]

Originally Posted by zmm12345

Have you been able to verify that anti dazzle works? I coded anti dazzle back on, and the dashboard now shows the brights going on pretty often. However, i cant seem to tell them difference on the road, as opposed to when i flash my brights manually. I am wondering if the visual part and sensor is working, but I missed something causing it to not actually work.

I went from 03/2019.30 to 11/2019.40 and they still work and it is very obvious too. I will say that they are a bit more conservative as they don’t come on as quickly as before and seem a bit less active in some situations. It is easy at lower speeds to see them active and light up sidewalks or ditches as you approach traffic or traffic approaches you. It is also obvious that is creating tunnels around cars when you follow them as well. Sounds like you may have missed something.

[zmm12345]

Originally Posted by edofloat

I went from 03/2019.30 to 11/2019.40 and they still work and it is very obvious too. I will say that they are a bit more conservative as they don’t come on as quickly as before and seem a bit less active in some situations. It is easy at lower speeds to see them active and light up sidewalks or ditches as you approach traffic or traffic approaches you. It is also obvious that is creating tunnels around cars when you follow them as well. Sounds like you may have missed something.

Thank you
I will try to code it again and see if that helps

[LexxM3]

Originally Posted by zmm12345

Thank you
I will try to code it again and see if that helps

The "obviousness" of anti-dazzle in operation depends on the driving environment and driver attention. For example, 2 lane roads with trees on each side are likely to provide some of the most obviously observed behaviours. A well lit intra-city freeway, less so. Recoding won't hurt, however.

[LexxM3]

Originally Posted by randybobandy

Not sure if it was already mentioned on here, since it's quite the thread...but for your Spotify people, you have it as it's own source when selection your media source. There's another option called "connected audio" or something like that...not sure if anyone knows what that is.

I am off my infuriating weeklong CarPlay re-trial — CarPlay is shit and dangerous, nothing improved, done with it. CarPlay now turned off in car and on phone again, just using iDrive and BT with an iPhone.

But to the comment, I also do have Spotify and Connected Audio new options in the Media/Personalize settings, but have no idea what if anything either does :

[LexxM3]

Originally Posted by ifr

What about auto lane change? You gotta notice the difference in that

My comments on ALC improvements in software 11/2019.xx here for completeness: https://www.bimmerpost.com/forums/sh...php?p=25598726

It is much improved. Thanks for staying on me to re-try :-).

[LexxM3]

To re-baseline the camera R/F view vs R/D gear selection discussion, what we now have appears to be:

- whether view change works properly depends on camera selection being in A (auto)
- on AU 11/2019.34, camera A is remembered and thus camera view switching works correctly
- on CA 11/2019.40, camera A is NOT remembered and thus camera view switching is broken

Wondering where to go from here ...

[randybobandy]

Originally Posted by LexxM3

I am off my infuriating weeklong CarPlay re-trial — CarPlay is shit and dangerous, nothing improved, done with it. CarPlay now turned off in car and on phone again, just using iDrive and BT with an iPhone.

But to the comment, I also do have Spotify and Connected Audio new options in the Media/Personalize settings, but have no idea what if anything either does :

I have to mess around with iDrive as my default over CarPlay. I just get pissed at the message handling, but I haven't really fiddled with it in a few months. The new audio sources are strange, I need to dig into that as well. I feel like one of the Hardy Boys when going through iDrive settings/options.

[homerrr]

Originally Posted by LexxM3

To re-baseline the camera R/F view vs R/D gear selection discussion, what we now have appears to be:

- whether view change works properly depends on camera selection being in A (auto)
- on AU 11/2019.34, camera A is remembered and thus camera view switching works correctly
- on CA 11/2019.40, camera A is NOT remembered and thus camera view switching is broken

Wondering where to go from here ...

Finding the difference in the CAFD file is where, there's got to be an easy way to force A as default

[LexxM3]

Originally Posted by homerrr

Finding the difference in the CAFD file is where, there's got to be an easy way to force A as default

Yap. Haven't been successful yet against my own working 03/2019.45 as a) I am a rank amateur at coding discovery so don't yet have an efficient process flow, b) it's time consuming and no time, and c) there are a fair number of FDL parameters differences between the two widely separated versions and if there is a value, it is buried in that.

Would love to get someone's working 11/2019.xx FA, SVT, and all NCD files to compare or happy to provide mine. Asked this a few times without success yet.

[ifr]

Originally Posted by LexxM3

Yap. Haven't been successful yet against my own working 03/2019.45 as a) I am a rank amateur at coding discovery so don't yet have an efficient process flow, b) it's time consuming and no time, and c) there are a fair number of FDL parameters differences between the two widely separated versions and if there is a value, it is buried in that.

Would love to get someone's working 11/2019.xx FA, SVT, and all NCD files to compare or happy to provide mine. Asked this a few times without success yet.

What do you have set for
8081\\C_XV3D_COUNTRYVARIANT_NEXTMODE

If 01 then change to 00

[LexxM3]

Originally Posted by ifr

What do you have set for
8081\\C_XV3D_COUNTRYVARIANT_NEXTMODE

If 01 then change to 00

Hm, interesting. Mine is 01 (aka USA). Coding machine and car are not near each other right now, but will try changing to 00 (aka allgemein aka "general") and see what happens.

If this works, why do you think BMW is punishing USA with bugs? Is that for spite? And follow on question please ... besides my personal public attitudes towards BMW Canada, why do think BMW is punishing all of Canada by lumping our camera coding with "those Americans"? :-)

I'll ask more serious questions privately.

[TK421BMW]

Just had 11.2019.40 put on mine and now the pathway lights don't turn on when I get close. I thought there was a setting for that, but I don't see it anywhere anymore.

[LexxM3]

Originally Posted by ifr

What do you have set for
8081\\C_XV3D_COUNTRYVARIANT_NEXTMODE

If 01 then change to 00

Unfortunately, did not help. And I was incorrect, my 03/2019.45 8081 NCD also had this set to 01/USA. :-(

[LexxM3]

While @ifr's suggestion didn't work (yet) for the normal R/D view switch and I've reverted coding back to stock "USA" setting for this, I got to testing more of the camera view functionality. And what do you know, the buggy functionality I was complaining about before regarding view selection when using the PDC activation button now appears to be fixed! That is, when you press PDC button, the camera view is now reliably in A mode and correctly follows D and R gear selection.

You lose some, you win some? But only in some countries? Weird.

[ifr]

That's going to need some more testing as it could depend on another activation switch. The code referenced above is specific to your scenario and the comments align with that, in a dodgy google translate at least
"If true, the restriction applies: The system must always show a view to the rear when reinserting"

You definitely don't want the USA behaviour for that setting. What else did you change to get it working? Was the car allowed to sleep between coding sessions?

I guess I could break mine to confirm it definitively when I get chance.

[LexxM3]

Originally Posted by ifr

What else did you change to get it working? Was the car allowed to sleep between coding sessions?

I guess I could break mine to confirm it definitively when I get chance.

If you mean to get PDC button activation view switching working correctly, I believe it started working with update to 11/2019.40, not any coding. I just didn't look closely enough beforehand.

If you mean the "country nextmode" change from USA to general, then yes, the car was allowed to sleep between coding to general and testing of D/R switch — coded in the evening, tested next day. Didn't realize the deeper reset of sleep might be required in some cases, but I guess makes sense — learning something new every day, thank you.

From your private notes, I agree that USA is not the correct setting. I only reverted back temporarily to get back to baseline for now.

[ifr]

OK. I've not tested the setting as mine works fine, just seemed to fit the scenario.

I'll take a more detailed look over the hols if I get the time. Try to 'control' the behaviour at will through coding.

Sleep isn't normally needed, but its good practice to ensure the relevant ECU(s) have 'reset' before testing. Some coding doesn't take affect until that happens

[mikenyc]

Originally Posted by ifr

OK. I've not tested the setting as mine works fine, just seemed to fit the scenario.

I'll take a more detailed look over the hols if I get the time. Try to 'control' the behaviour at will through coding.

Sleep isn't normally needed, but its good practice to ensure the relevant ECU(s) have 'reset' before testing. Some coding doesn't take affect until that happens

Anyone seen that message after recent update , it asking me to purchase auto high beams option while I already had it for the past 12 months and it's part of my package.

[Xeno]

Do your auto-high beams perform as expected?

[mikenyc]

Originally Posted by Xeno

Do your auto-high beams perform as expected?

Worked just fine and as expected before software update since delivery back in January, I think I had old version something like 10.2018. They basically disabled my auto high beams with this update and as soon as I'm trying to activate this option with our usual button on a left side, I'm getting this error message.

[randybobandy]

Originally Posted by mikenyc

Anyone seen that message after recent update , it asking me to purchase auto high beams option while I already had it for the past 12 months and it's part of my package.

That’s weird. I never saw that before. I tried to check CD’s website store to see if I could find it...nothing!

[W0ut]

My car got upgraded to 11/2019.40 today.

The drive recorder 'as a service' now works. Didn't order it on the car but bought the app on the connected website. With the 07/2019.55 it didn't work. now it does.

First impression is that the surround view is much improved. The indicator bars are much faster/sensitive than before.