Feature: Displays
H
igh-quality 3D experiences are not new to embedded devices, but until now the technology has been limited to premium products. Aſter all, high-
performance components, high-powered processors and GPUs are pricey. Fortunately, this is beginning to change;
as technology matures it allows 3D interface benefits to be brough to the mid- and low-end products, too.
Becoming 3D Te drive to 3D content is primarily fuelled by a much-improved user experience. In some applications, 3D is vastly superior to a standard graphical representation; for example, in an industrial setting, a failed device or part in a system can be located more easily. Tis can be equally true in consumer
electronics, where a 3D image can guide how to fit or connect a device. A rotatable, zoomable 3D image is far more informative than a simple text message or a one-size, one- angle picture. Generally, we are more adept at distinguishing a three-dimensional image than reading a text. Of course, 2D images are useful, but to get
to a similar level of detail compared to 3D, 2D renderings require more memory, leading to a more expensive device. What helps implement cheaper 3D are
embeddable TFTs, since their prices have dramatically dropped – so much so that it is oſten cheaper to put a display on a product than to implement a sophisticated touch mechanism. Tere is a middle road between having the
EV charging station charge screen
Developing 3D representations By Jason R. Williamson,
Marketing Vice President, Altia 46 September 2023
www.electronicsworld.co.uk
experience of a video game versus a simple 3D representation. Also, adding greater 3D functionality to a simpler device will either be too expensive or hamper its performance. With the right design approach, both 2D and 3D images can be used strategically to enhance the user experience and convey the right amount of information. Still, the hardware and its 3D readiness
must be carefully considered. Even when hardware is capable of rendering 3D content, it doesn’t mean it can support any type of 3D. For entry-level 3D support, a device must have the following:
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60
