OSD rendered at wrong position

[delfer]

Device

Goggles V2

Trace ID (bototm left)

c980ff15-7390-4a35-9ad8-8593b9308afa

Describe the issue

Hello! I have two files recorded sequentially. Rendered today at https://fpv.wtf/osd-overlay v2.0.0. One file is OK, another one with the corrupted OSD. It's repeats every try. OSD files: https://drive.google.com/drive/folders/1l2qK51dy-as1oOsRThHPJxfaC19AG1VO?usp=sharing DJIG0058.osd - with wrong layout DJIG0059.osd - OK Fonts: BetaFlight Nexus https://sites.google.com/view/sneaky-fpv/home

[Frolv1966]

https://t.me/djifpvru/376476 Друзья, сегодня столкнулся с проблемкой - при наложении OSD на видео само osd оказалось увеличенным в два раза. Как по вертикале, так и по горизонтали. При просмотре видео в очках такая же хрень. Во время полета все было на месте (но было отображено меню самих очков). При пробной записи дома - все нормально, все надписи "на месте". В чем может быть проблема, где искать причину. Не хочется наступить на эти грабли повторно и "испортит" видео.😢 ОСД совмещал с помощью этого (https://knifa-develop.fpv.wtf/osd-overlay).

[fisher1506]

I have the same problem only on airunit but some times it is ok.

[FinalFrag]

I took a look at this issue in the osd overlay code in the configurator, and I can confirm that the .osd file only contains data for the upper left corner 1/4th of the screen.

[stylesuxx]

OK, then it's less of a configurator issue and more an issue of msp-osd - we should probably move discussion to that repo then.

[Ziiiwei]

Same issue here. It seems like it sometimes renders the OSDs in PAL or NTSC mode instead of HD mode.

[Saby1985]

Hi Guys, i got the same problem. Only the top left corner of the OSD show up. Any ideas or fixes?

[axelludwig]

same issue

[delfer]

This issue also reproduces while playback in goggles.

[Bornenjap]

I have the same issues and happen at playback in the goggles too. Any chance to fix this?

[coyotezz]

Hi, just copy the 2 first lines from a OSD file that works right to the wrong file, take a HEX editor todo this. Fotr mi its ok i have some OSD files corrupt if you have all OSD files wrong, you have a problem wrinting files to your DJI Googles SD, may be reflash or update your WTOFS.

[Bornenjap]

Hi, just copy the 2 first lines from a OSD file that works right to the wrong file, take a HEX editor todo this. Fotr mi its ok i have some OSD files corrupt if you have all OSD files wrong, you have a problem wrinting files to your DJI Googles SD, may be reflash or update your WTOFS.

Thank you. I think I found a way, when we connect the battery to the quad, don't arm it immediately, but wait a few moments, maybe 4 to 7 seconds to give the WTFOS font a chance to load data. after that it's safe (When i connect the battery to my quad and see the goggles, the WTFOS process appears in the bottom right corner). I have tried it several times when we connect the battery to the quad and arm it directly, the DVR results will be problematic.

I hope this helps

[coyotezz]

Hi, just copy the 2 first lines from a OSD file that works right to the wrong file, take a HEX editor todo this. Fotr mi its ok i have some OSD files corrupt if you have all OSD files wrong, you have a problem wrinting files to your DJI Googles SD, may be reflash or update your WTOFS.

Thank you. I think I found a way, when we connect the battery to the quad, don't arm it immediately, but wait a few moments, maybe 4 to 7 seconds to give the WTFOS font a chance to load data. after that it's safe (When i connect the battery to my goggles, the WTFOS process appears in the bottom right corner). I have tried it several times when we connect the battery to the quad and arm it directly, the DVR results will be problematic.

I hope this helps

Thanks Bornenjap I Gona to try it, but generally I have to wait to have GPS FIX

[Bornenjap]

Hi, just copy the 2 first lines from a OSD file that works right to the wrong file, take a HEX editor todo this. Fotr mi its ok i have some OSD files corrupt if you have all OSD files wrong, you have a problem wrinting files to your DJI Googles SD, may be reflash or update your WTOFS.

Thank you. I think I found a way, when we connect the battery to the quad, don't arm it immediately, but wait a few moments, maybe 4 to 7 seconds to give the WTFOS font a chance to load data. after that it's safe (When i connect the battery to my goggles, the WTFOS process appears in the bottom right corner). I have tried it several times when we connect the battery to the quad and arm it directly, the DVR results will be problematic. I hope this helps

Thanks Bornenjap I Gona to try it, but generally I have to wait to have GPS FIX

That's gonna work too. The point is don't arm the quad immediately after plugging the battery, to allow the WTFOS fonts do their job.

Happy flying