LarsMiddendorf

Member
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

122 Neutral

About LarsMiddendorf

  • Rank
    Member
  1. What about MDX1.1 and D3D9Ex? Will it be supported ?
  2. [.net] Managed layer for Direct3D 10

    Nice. Looks interesting. Too bad it only runs on Vista.
  3. Multiple Devices vs Multiple Swap Chains

    Aha, thanks. That could be a good solution to remove the non-orthogonality between the default and additional swap chains. I hope this doesn't degrade performace. On NVidia cards there is/was sometimes only early-Z on the first FrameBuffer Object (OpenGL.)
  4. Multiple Devices vs Multiple Swap Chains

    Can I delete the default swapchain? For example what should be done if the window with the default swap chain is closed and the other window with the additional swap chain remains open?
  5. Multiple Devices vs Multiple Swap Chains

    Is there a problem when doing the following for a MDI application. 1)Create one backbuffer with the size of the MDI parent window. Use D3DSWAPEFFECT_COPY. Then foreach MDI child 2)Before rendering to a child window, change viewport. 3)Override Window Handle and Rectangle at Device.Present
  6. I encountered the same problem and I've got a list with WeakReferences to the owner object for every opengl texture id. Every time a new texture is loaded and of course at the end, all WeakReferences are checked and if the owner is no longer alive, the texture id is also deleted. The problem with the C# destructor is, that it is called from another thread and opengl rc are per thread.
  7. You can uses the generic GraphicsBuffer<T> that has got a special write method for the generic type. All functions returning a GraphicsBuffer are overloaded and can also return a generic GraphicsBuffer.
  8. DirectX SDK October

    I think it has moved to EffectCompiler.CompileShader(EffectHandle functioname,string target,ShaderFlags flags)
  9. DirectX SDK October

    It seems that they have changed the event handling. Even if Device.IsUsingEventHandlers is set to true, resizing the control doesn't cause the device to be reset like in older versions. Where can I find more information on the new API. The documentation in the SDK decribes only the old MDX.
  10. C# as scripting language

    The only problem using C# as a scripting language is that you cannot unload and update your classes, if the assembly is loaded into the same AppDomain. But creating a secondary AppDomain is also not very usable because calls between different AppDomains are very expensive.
  11. shader system implementation

    [QUOTE]So, plugins are a perfect middle way between old school unflexible pipelines, and the complete abstraction of the rendering system into meta shaders. Once we have well working meta shaders (we will probably need hardware supported JIT compilers for that), we can just trash the plugin approach. And I'll be happy about it, because the system has in fact several drawbacks. Just not the ones you were thinking of :) [/QUOTE] How will your meta shaders look like ?
  12. shader system implementation

    @Yann L: How do you solve the problem with the big number of shader permutations? With PS30 HW you can put 4 or more lights(with shadowmaps) into one rendering pass. But each light/fog should also have its own shader fragment: point light, spot lights, lights with a cubemap, volumetric fog. Combined with some material shaders the number of combinations grows exponentially. Precompiling is impossible but creating on the fly is also slow. Cg's interfaces are nice, but they don't really help here, because the cause a recompilation. Generating asm shaders is doable, but you lose specific compiler optimizations(and it's even impossible with glsl).
  13. [.net] C# 3.0 Specification

    C# is great and becomes even greater with each release. Queries as a language feature is a nice idea. But I'm sceptically about the ML-style features like the combination of lambda-expressions, type interference and generics, which allow to write code, that is difficult to read, because the types are no longer obvious. http://blogs.msdn.com/abhinaba/archive/2005/09/17/469568.aspx
  14. You could also try this. One .cs file(safe), but only .Net 2.0 . http://www.3d-seite.de/csopengl
  15. OpenGL Modern Fast Rendering?

    @zedzeek: This doesn't really solve the problem. I can't specify each shader and I always want render one pass with PS30 to save geometry bandwidth. Each light has got it's own shader and the number of light shaders is not limited or predefined to support all types of light and fog effects. I don't want to and I just can't create a special shader for each type of light/material interaction. So the shaders must be generated dynamically. This works ok, if only doing one light per pass, because the light/material combinations can be often reused. But when rendering all lights in one pass there are too many combinations and recompiling a Cg shader or linking a GLSL shader is not free. Linking a GLSL Shader with NVidia drivers takes ~50ms so it is even impossible to link a large number of shaders at startup. Perhaps deffered shading is the most elegant solution to this problem, because materials and lights are rendered seperate. @Sorting: What about batching in OpenGL. How important is it? When using static index buffers, merging index lists is only possible if two geometry block are lying directly one behind the other.