Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

Mud-H's Achievements

  1. Not sure if related but with my work on TL I discovered that what make the selection of multiple objects very slow is the inspector which add all objects. In most case, you don't even need the inspector when selection many objects so I added a inspect multiple object checkbox or when the inspector is added, objects are not added which make selection lighting fast. But if the goal is to change variables on those objects then you need some patience :)
  2. Now I can go sleep in peace :D Was good to get back at T3D development.
  3. I just found that the editors no longer use the native MenuBar class but use the GuiMenuBar instead and it have been adapted to work like the MenuBar was. Too late to try for today but seem like my concerns are no more. :)
  4. What happened with the GuiMenuBar? It's mostly commented completly... Is there a replacement or some kind of plan about it? I used it for TorqueLab and now I have trouble to reimplement it, seem to be related to the key accelerator. Could move back to the native menu if someone can help me getting it dark :oops:
  5. I did some experiments with your BrushEditorTool and I'm not sure how it's meant to be used... If I understand it right, it's not meant to do anything as is it now, right? It's just the base for a better editor system but the existing tools need to be adapted, right? So this would allow to call existing tools function from within a single WorldEditorGui instead of having to switch the EditorGui just so it can receive the brush call. It sound like a good idea but I would need more informations about how they should be use before I can do anything with it. Anyway, I don't want to put pressure on you about that, I just want to clarify how the BrushTool should be used. I'm currently giving another development rush on TorqueLab and tought it might be used to unify the MeshRoadEditor and DecalRoadEditor. I will work on something by simply switch the EditorGui depending of what type of road is selected and later I might just switch to the BrushTool once I figured how it work.
  6. I found out yesterday that the TerrainMaterials detailStrength no longer work with the PBR branch. I'm not sure what is causing it exactly, PBR or D3D11 code, is there still a updated PBR branch without D3D11 so I can test it? Or do you have any idea what can affect the detailStrength only? detailSize, macroStrength and all other fields work fine, it's just the detailStrength. I tought it was maybe caused by my custom editor but I tried with the stock editor and I have the same issue. I'd like to find what's wrong but I have no idea about how the detailStrength is used... Could it be a local shader stuff? I made sure to have the same shaders and core than the full template.
  7. Mud-H


    Was it causing a crash? I stopped using the callOnChildren after it caused too much crash, also if I remember right it was not always working correctly when it wasn't causing crash...
  8. In case anyone is considering replying to my partner(s) request, I'm not looking for them anymore since I found some yesterday. 8-) After a nice discussion with Nils and Timmy, I decided to join the Deadly Matter project to help with scripting. I won't dedicate all my time to it now and I will keep working on TorqueLab on the side.
  9. Email sent, I'm curious to know more your scripting needs and that revise editor.
  10. Well your OpenSimEarth project seem quite interesting more than I hear about it. Your previous posts have always catch my attention but I was quite busy and in some kind of game development break phase. I will have a look at your GitHub repositories and see what I can find there. I understand about FlightGear sizing issues but is there a way to test OpenSimEarth as a FPS game? I guess I will find out by looking at your repository. Also, like you said, further discussion on the subject should be moved to an OpenSimEarth thread.
  11. That make sense because those that are in Outbox section are for a user who haven't been active since I sent him PM
  12. So maybe it get sent automatically if you are online but there"s a delay.. :?:
  13. But I just read the Pull Request guide :cry: We like each pull request to have a reasonable revision history - not too many small commits with typo fixes, for example. Sometimes, we may ask contributors to rebase large numbers of commits into a single commit before the request is pulled. Ah, I had missed the too many part. Okay I will try next time, preparing one for the PostFX scripts and manager :)
  14. Typo error found in VignetteP.hlsl Line 31: float4 base = tTORQUE_TEX2D(backBuffer, IN.uv0); Should be: float4 base = TORQUE_TEX2D(backBuffer, IN.uv0);
  15. Did you read it, it's now in my Sent Messages?
  • Create New...