Sign in to follow this  
vir2007

Draw objects in real time

Recommended Posts

Hi all,

I have [b]glutDisplayFunc[/b]() to draw the environement

And I [b]receive [/b]data from [b]network [/b]that contain [b]position [/b]of [b]objects[/b], I have a [b]thread [/b]that treats that kind of data

So here my problem

I tried to store data into [color=#ff0000][b]vector<data> [/b][/color]to be drawn in [b]glutDisplayFunc [/b]each time, this way [b]slow down [/b]my computer and [b]moving objects is not [color=#ff0000]smoothly[/color][/b]

Then I tried to not use vector<data> and want to draw objects direclty from "[color=#ff0000][b]thread[/b][/color]" that receive data, and nothing happened

so is there way to make moving objects in [b]real time[/b], and if possible draw them from that [b]thread [/b]instead of [b]glutDisplayFunc[/b]

Thanks

Share this post


Link to post
Share on other sites
hi,

first of all make sure you are not reciving data by TCP/IP... as this may be to slow for real time Game.
Use UDP instead.
But the basic setting is right. the Network Thread should write to a Object or what ever is your data container.
And than inside your glutDisplayFunc() you just draw as you would always do ...
You may track how many times per second you update the data from network .... as this needs to be close to your framerate .

cu
uwi2k2

Share this post


Link to post
Share on other sites
[quote name='vir2007' timestamp='1343846032' post='4965268']
so is there way to make moving objects in real time, and if possible draw them from that thread instead of glutDisplayFunc
[/quote]
This is not possible because all rendering has to happen within the thread of the OpenGL context. First you need to ensure that the access to the data received from the network thread happens in a synchronised way. Otherwise all kinds of funny effects may occur due to concurrency issues.

You can achieve this by various methods such as employing the [url="http://en.wikipedia.org/wiki/Producer-consumer_problem"]producer-consumer-pattern[/url] (the network thread would represent the producer role and your rendering thread would be the consumer role).

The term "real-time" must be treated in a relative way when dealing with network communication, due to the fact that network connections are prone to lag for various reasons. You can compensate for this by using motion vectors and prediction algorithms instead of absolute object positions.

Take for example a car. Instead of updating the car's position on the server side and transmitting its updated position, you can instead transmit a movement vector along with the current velocity. This way you can update the car's position on the client side in real time while waiting for updated information (like vector or velocity changes) from the network. In order to keep things synchronised you can also throw in a full state after a certain number of packets to force the client side to update the actual position, for example.

Note, however, that it's far from trivial to achieve satisfying results - a good real time solution can be quite a challenge.

Share this post


Link to post
Share on other sites
I was making some mistakes which are corrected now, thnx for help anyway :)

@darookie: thnx for that explanations :) Edited by vir2007

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this