[shadows thru floor]

Is this 3.0 or 3.1? It seems like the floor itself would block all of the light. It's hard to envision this without a screenshot.

[Game running with pauses]

I think they probably updated the Steam app overlay and added a lot of extra debugging messages, which we clearly don't want. However, I want to get Valve's response and see what they say it is.

[Game running with pauses]

I do not observe it continuously printing. I see it printing the same thing a lot of times, but it stops once the game starts running. Then, when the game ends it prints a lot of stuff again.

 

Reported to Valve here:

http://steamcommunity.com/groups/steamworks/discussions/0/558754259370319426/

[Hooking GetOpen/SaveFilename?]

Reported to Valve here:

http://steamcommunity.com/groups/steamworks/discussions/0/558754259370319426/

[Game running with pauses]

It looks like this might be a Steam problem that just started happening for some other applications, too:

https://www.google.com/#q=Hooking+CoCreateInstance%5BEx%5D

[Very little bug when loading resources :P]

Thanks, that's an easy fix.

[Out of Video Memory with Steam running but no steam_appid.txt]

I believe this is a Steam problem:

http://steamcommunity.com/app/221040/discussions/0/828934089859605401/

[Game running with pauses]

• Is this happening in release or debug mode?
  
• What operating system are you using?
  
• Is this the standalone or on Steam?
  

[ZSort + Directional Light + Shadows = Memory Leak]

You really can't evaluate memory leaks in Lua, because Lua is constantly leaking until it runs a garbage collection call. Memory usage will rise and then periodically get cut back down.

[BSP 90° rotation tool : BSP no more grid snapped]

Incomplete, I can't evaluate this.

[Game running with pauses]

This description is incredibly vague.

[Character Controller Falling through solid objects (csg)]

Is this CSG geometry that is being dynamically created? Can you please explain what you are doing?

[[3.0] Lighting and Shadows]

It looks like the lightmap is not being displayed on that material, but I don't know why that would be. I've never seen this behavior before.

 

I couldn't even guess why there are shadows going toward the light and on the side of the "ground." There's only the ground, the box, the torus knot and the light in the map.

That's correct behavior for the old forward renderer. If you want physically accurate lighting, the 3.1 deferred lighting is the only way to do that right.

[Non-buntu distros]

A .deb package is being created for the Ubuntu Software Center, but will not be updated as frequently. We use a custom installer/updater that allows a rapid release schedule without making you re-download the entire package each time a file is updated.

 

Support for other distros will likely be a gradual thing as we gain experience on difference platforms. I know many people are presently using it on non-Ubuntu distros, but for the time being, the official scope of support is being limited to Ubuntu 12.04 LTS (soon to be 14.04).

 

The practical implication for that right now is that bugs or problems specific to non-Ubuntu distros can't be investigated.

[PS4 infamous game technical details]

I believe they draw 11 million simulated polygons per frame. The rest sounds pretty nonsensical. A mid-level graphics chip doesn't magically turn into a high-end GPU just because you put it in a plastic injection molded case.

[Time::GetSpeed() not really useful?]

Don't modulate physics functions by GetSpeed(). When you set the velocity of the character controller, you are setting a value that is measured in units/time. Modulating this by the execution speed will result in incorrect values.

 

If on the other hand, you are manually moving an object each rendering frame, and you want to know how far it should move each time to account for execution speed, then the movement value should be multiplied by Time:GetSpeed().

[Lua explain code]

Emitter::SetVelocity will do the other part.

[Scrolling scene tab still broken]

The draggable tree view is a custom control because a multi-select tree view was needed. It is possible GTK might offer this functionality, but it's already done for Windows and Mac, and writing another pathway for the UI requires more work and ongoing maintenance. This might be something we end up doing, but it definitely wasn't worth delaying the project over.

[Scene panel : move object to Root/Parent]

If you created folders, it would no longer be displaying the scene hierarchy.

 

Although, at the root level, it wouldn't really matter. I suppose root-level brushes could go in a "Brushes" folder, and root-level models could go in a "Models" folder. Even if they have children not in that category, it would still make sense and clear the brushes out of your way.

[Newton 3 ragdoll]

No, animation and rigging are two different things. The vertex weights just work, no matter what you do to the limbs.

[How to make skycube]

The reason we don't have a "skybox" setting is because this is being added through the post-process system. However, the editor only supports shader-based post-processing effects right now, not script-based ones. The reason for this is complicated, but when script post-processing effects are added in the editor, it will allow you to just add an effect, choose a texture, and it will appear.

 

The advantage to this is that it provides a much more versatile sky system, rather than just a simple skybox with no options.

[Folder structure for multi-platform development?]

I recommend keeping your source code in the "Source" folder and allowing all projects to access it.

[[Linux] Run mode slower than debug]

Because Canonical's desktop makes the difference between it working and not working.

[Registration key]

Please check the bottom of the email you received.

[Steam integration]

Yes, I am pretty sure. In fact, I should probably just remove that text file from the templates folder, and make it an opt-in feature.