Ticket Created
over 5 years ago

WERETECH-8406

DC content is not persistent between onUpdate on real VA4 but it is persistent in simulator

In simulator (VA4) is DC content persistent between onUpdate calls and it is possible to draw only changes. On real VA4 is DC content cleared before every onUpdate and it is necessary to draw whole display content.

VA4: 3.80, SDK: 3.1.6

  • It happensd on more devices. I have reports from FR45 as well. 

    If it is "by design" , explain what is the "design goal" to clear the screen with every frame and why it is the "design goal" just for 2 devices, while for all other devices is the "design goal" exactly opposite – to persist the image. 

  • Thank you. Has current behavior some benefits? I see only disadvantages: more inconsistencies between devices, more work for developer to maintain, slower display update becouse on every onUpdate I must update everything, and then more power consumption (imho)

  • To be absolutely clear, the original ticket (WERETECH-7828) was transferred to another team and was closed as by design. The new ticket WERETECH-8406 may result in more discussion and maybe a change in behavior. At the very least we should update the simulator to match the expected behavior. I've added notes to this effect, so hopefully we'll get some consistency either way.

  • Thanks for the reply. Could someone explain this newer page management system and why dc must be cleared before onUpdate? Is there any documentation about this? And in simulator is different behavior.

  • Thank you Travis. If this is by design and the ticket was closed, you should let us know Slight smilenice if I could support these devices. In the Maze Game it's not realistic to do a full redraw every frame, the rendering would drop from 10 FPS to 1.