Jump to content

AggrorJorn

Members
  • Posts

    4,816
  • Joined

  • Last visited

Everything posted by AggrorJorn

  1. Can you elaborate a little on what you are trying to achieve?
  2. I thought I had added this to the docs a few weeks ago, but as it turns out there are 2 places that talk about the flowgraph editor. http://www.leadwerks.com/werkspace/page/documentation/_/user-guide/object-scripts-r631 http://www.leadwerks.com/werkspace/page/documentation/_/user-guide/flowgraph-editor-r17
  3. Updated the docs function Script:RandomValue()--arg return math.random(1,5) end Also check out here:
  4. I second this. My main project exists out of 3.8 GB of sound and that is just speach and not even music. I think ogg support is something that should be part of the core leadwerks functionality.
  5. AggrorJorn

    FlowGUI

    I have rewritten FlowGUI entirely with panels, buttons, checkboxes, sliders, text areas, textboxes and dropdownlists. I am waiting for the Steam workshop to accept payed items though. Depending on its popularity I want to expand it even further.
  6. Are you opt in to the beta? So if you create a new project (lua?) and try to run it, it immediatly freezes and crashes?
  7. Tutorial 19: Displaying the picked up bottle and handling keyboard input.
  8. Tutorial 18: Picking up a model for the inventory:
  9. Any chance you are subscribed to workshop items? That process happens in the background but can still cause leadwerks to freeze.
  10. There doesn't seem to be an option for it in the editor. Seems like something we need to request. In the mean time you can edit the .mat file in notepad. Simply remove the line containing the shadow shader.
  11. I have added them to the documentation, although I do not know what the xbuttons are. http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/key/key-r629
  12. No need to be embarrassed, those window controls are very sensitive. It has happened several times to me as well.
  13. It has happened to me that the window is hidden in the sides of the script editor. If you move your mouse closely to the edges of the editor, you can find it again.
  14. Just tested the buttons on the side of my mouse, but they don't trigger it.
  15. Some mouses have extra buttons on the side, maybe that is what they are. These 2 pages are now updated: http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/window/windowmousedown-r456 http://www.leadwerks.com/werkspace/page/documentation/_/command-reference/window/windowmousehit-r457
  16. Like shadmar said, you are create two windows. Remove this line: //Create a window window = Leadwerks::Window::Create("hi?");
  17. Commenting code means putting two slashes before the code, so that it is ignored during compiling. //if (window->KeyHit(Key::Escape));
  18. what happens if you comment out this line: if (window->KeyHit(Key::Escape));
  19. How to deal with models that contain animations:
  20. When you fill in Collision.Scene, the pick will only work on objects that collide with Collision.Scene and not objects that are of Collision.Scene. At least that is my current understanding.
  21. If you set it to that Scene, it will return all types that collide with scene. With character collisions it is better to use hitboxes. from the docs: collisiontype: if specified, the entity collision type will be tested against this, and only colliding entities will be tested.
  22. http://www.leadwerks.com/werkspace/topic/7091-unofficial-leadwerks-3-faq/
  23. 2 solutions: Use a cylinder and scale it to the distance. Create meshes from scratch. Advantage is that you make a mesh that has less polies.
  24. Topics appear on the top when a new reply has been given or when someone voted on the poll. No big deal really. I am removing the poll though.
×
×
  • Create New...