TO Grauw (and others, of course): YASVL

I have not blamed anyone . Nor grauw . Where you got this impression?
What I Ve done is using some irony about a supposed vdp behavior ( directed, perhaps towards to Yamaha engineers ).
some one here reacted to this as if i ve heavily insulted a person, which is not the case.

so i really do jot understand your message.

The title say "to grauw" because i recognise its deep knowledge of those vdp issues, so I've asked to grauw. When o wrote the post I never considered who was the wiki author. My issue was to ask a confirmation about a so weird vdp behavior that I found suspect . I Asked grauw because i know he the most skilled person concerning this kind of questions.

And he confirmed my suspect that the wiki was not correct in this point without being offended.
I found bizzarre that the hypothetical person who could got offended is not hurtEd while a lot of other person are.

Sorry for the quality of message I am writing from a cell and the word correction is not helping me

@Grauw Would you do an attempt to improve the text?

Exactly!
Fortunately there is no additional weirdness in vdp sat address bit interpretations and it is possible to place the sat anywhere in the full 128KVram space even in screen 4-5-6. that's the essence of the question.

To be able to update the wiki i needed to be sure of the fact the wiki was incorrect. At the time i've wrote the post I WAS NOT SURE. So even if i was able (that's to be proved) to update the wiki, i could not do without the rick of introducing incorrect documentation.
That's the reason i've asked Grauw. And to be honest, to be sure of situation one simple test should be done on the real machine. Even if openMSX is super accurate, there is no 100% assurance that, for those kind of particular behaviours like the one described in the wiki there are no subtle differences between the real hw and the emulation.

However, being assured by grauw on the register usage i can rely that things are as he said.

a simple test program could be done even on msx-basic, by setting to a know value in upper 64K (in every mode) both register r5 and r11 and then vpoking 4 bytes to show a particular sprite in some location checking if it's displayed correctly