Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It is an invalid operation because you must have a context bound to each thread. More importantly, all of the GL window system APIs enforce a strict 1:1 mapping between threads and contexts... no thread may have more than one context bound and no context may be bound to more than one thread. What you would need to do is use shared contexts (one context for drawing and one for each worker thread), things like buffer objects and textures will be shared between all <strong><em>shared</em></strong> contexts but the state machine and container objects like FBOs and VAOs will not.</p> <p>Are you using tiled rendering for this map, or is this just one giant texture?</p> <p>If you do not need to update individual sub-regions of your "chunk" images you can simply create new textures in your worker threads. The worker threads can create new textures and give them data while the drawing thread goes about its business. Only after a worker thread finishes would you actually try to draw using one of the chunks. This may increase the overall latency between the time a chunk starts loading and eventually appears in the finished scene but you should get a more consistent framerate.</p> <p>If you need to use a single texture for this, I would suggest you double buffer your texture. Have one that you use in the drawing thread and another one that your worker threads issue <code>glTexSubImage2D (...)</code> on. When the worker thread(s) finish updating their regions of the texture you can swap the texture you use for drawing and updating. This will reduce the amount of synchronization required, but again increases the latency before an update eventually appears on screen.</p>
    singulars
    1. This table or related slice is empty.
    1. POA way of generating chunks
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndon M. Coleman
    1. USAndon M. Coleman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POA way of generating chunks
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOh I haven't tried to instantiate the RenderTexture before sending it to the threads, might be a good idea !
      singulars
      1. PO
      1. UStho
    2. COThat still will not work if you do not implement context sharing. The term `Render` in `RenderTexture` implies you are actively going to use OpenGL to render into it. You would either have to share contexts between threads, or unbind the context from the drawing thread and give it to worker thread before doing these things (and this is almost never practical). My point was actually that if you use shared render contexts, then the worker threads can actually create the textures for use in the main drawing thread.
      singulars
      1. PO
      1. USAndon M. Coleman
    3. COBut honestly, **0.5** ms is not an unreasonable amount of time for an update, you have a full **16** ms to work with if you want to achieve 60 FPS. It does become unreasonable if your software is written in a way that it has to do these updates serially instead of in parallel or limited to a few-updates-per-frame.
      singulars
      1. PO
      1. USAndon M. Coleman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload