Might not be used in game dev but its referred to data stored in either memory or disc representing an asset.
Explore data points, discrete units of information. The term is equivalent to datum, the singular form of data. See how they're measured and used in various settings.
whatis.techtarget.com
Anyway... filling the thread with loads of arb crap so cool you win, whatever e-p contest your holding.
It isn't a data point. Period.Has sweet f all to do with points or data.
It is refer to a game element, it is a either a trigger as an example for external or internal code found with in the engine or external code, either via script or DDL.Data point has f all to do with a game element, a trigger, an asset or any game object for that matter. Data stored, is just that stored data, whether game elements not being rendered or a raw texture or asset file. What you do get is pointers, a pointer is basically some thing that tells whatever program is running where data is stored, ram, GPU or disk even swap file, so that game engine knows and keeps track of what is stored where in which memory address, of course the engine does have it's own pointers it wouldn't function otherwise., but again pointers has nothing to do with data points, nor is it the same thing.
Textures and models are loaded into ram or streamed from disk in this case disk and processed by GPU/CPU in a raw format easily accessible by the GPU memory for processing. Which is why you have certain industry standard graphic/asset formats and while for example DDS textures are common and extremely popular due very little resources used in processing the format and the GPU having native support for it.However it is still up to the DX/ vulkan/ openGL ect layer to pass on the information and process the information as needed. Dx is basically the communication layer between the game engine and the GPU/CPU
To the point if you were to use a dds texture vs a jpeg texture, the jpeg texture would require more resource to process as well as use more ram, it is still not called a data point it is, raw data, or rather the game element or asset or whatever it is processing in a raw format the GPU can process easy.
For example the engine I am using, support a file format of dbo, which is akin to x file format which already has the asset in a raw format making storage and processing extremely quick compared to other formats, of course it has some limitations with regards to embedding textures, animation, bones, and overall polygon count the format allows, compared to fbx as an example.
Still isnt a data point........It isn't about epeen, just so happens I do game development for a living.Not sure what is arb about talking about game engines, its processes and explaining why it isn't a data point, and pointing out what it is actually called. I would ask you what a pbr surface map is and in what channels metalness, AO, and roughness maps go and would likely call that a data point too you and would have to use google, and yes channels refers to the rgb channels of the surface texture, where you place grey scale textures of the ao, metalness and roughness maps, which a compatible shader can read, additionally you can a depth map as well, but not many shaders support the addition of that.
The car is an asset, the coordinate information broadcast, whether on a 2D or 3D plane will be required to be saved and updated akin to a temporary database if you will, that is actually data structure commonly known as an array. Data point actually refers to a point in statistical information and unit of measurement, "data point" actually has nothing to do with game engines or programing as pointed out by the link. In programming you would refer to data structures by there given name, and in this case with unreal a data array is most likely to be used, then of course you get linked, tree, or stack data structures. The object in this case the car, and the array information is still two different things. The array could get corrupted which would result in the car still being rendered but not where it is suppose to be.
Again not about epeen just so happens to be my line of work.
