Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Leadwerks Community

TheConceptBoy

Members
 View Profile  See their activity

  • Content Count

    159

  • Joined

  • Last visited

 Content Type 

Everything posted by TheConceptBoy

  1. TheConceptBoy
    zombie.hzombie.cpp I've tried playing around with setting the functions as public, as per yours and some other posts with suggestions.
  2. TheConceptBoy
    I get this array of errors, mainly for the cpp file:
  3. TheConceptBoy
    I was, then I deleted it, just to see what happens, now added it. Appears to not be the cause of the issue, something else is still up with this.
  4. TheConceptBoy
    Would you mind sharing the acompanying cpp file you have for baseActor? I'm comparing the contents
  5. TheConceptBoy
    Also in addition to the above issue. Can you see if I understand these functions correctly? void Attach(); Is called during instance creation / attachment to an entity, it's a single shot event. void Detach(); Called when instance is destroyed / detatched from the Entity and the engine handle removal of all things related to it automatically. void Collision(Entity* entity, const Vec3& position, const Vec3& normal, float speed); Called upon collision with another instance. void UpdateWorld(); The main loop for this particular instance,
  6. TheConceptBoy
    Ok, on the side note, I've declared a whole bunch of functions in the .h file however I did not specify them in the cpp file for the zombie. Not that it changed anything, just a flashback from my last hair ripping C++ experience: Currently my cpp file looks like this: I'd like to point out that the ; error you see for the void of UpdateWorld is, I'm certain, is caused by the Attach function because if I move that function after UpdateWorld, then Detach will get that error so something is up with Attach. EDIT: as the matter of fact. I can remove Attach and it will move th
  7. TheConceptBoy
    I don't think there is such a thing as: Entity* entity = Entity::Box(); If there is, it's not in the Docs. https://www.leadwerks.com/learn?page=API-Reference_Object_Entity There does not appear to be a Create() or a Box() for Entities. There is a Create for various things that are derived from Entity like Camera, Model, Light, Decal, Emitter
  8. TheConceptBoy
    yeah that same semicolon error in the main.cpp remains.
  9. TheConceptBoy
    Ah, ok, making progress. Would you know why in the zombie.cpp the UpdateWorld is complaining about a semicolon, and that it fixes itself by just moving the function above the Attach function? Both functions are empty and I don't think the order of function declaration in the .h file affects it. Also the semicolon issue has moved on to here and I know for a fact that the issue is not somewhere above as when I delete these two lines, the application compiles just fine.
  10. TheConceptBoy
    Good day, I am writing this in hopes that after 4 minutes of posting this extensive question, I figure it out on my own. So apparently Leadwerks Actors system. from what I understand is an arbitrary method of creating classes that offer better integration within the engine than ordinary classes. If created properly, things like the main loop, creation and what not get executed automatically, saving you the trouble of creating your own main loop and putting in the code to update the main loop of the class yourself manually. I'm experimenting with say a class of zombies.
  11. TheConceptBoy
    Smart move.
  12. TheConceptBoy
    What about doing something node based for shader creation like Unreal? I mean Yes yes, Unreal = Gian Development Team and Leadwerks = One dev Guy. The manpower is colossally different. Just hypothetically. Creating shader using nodes? For core game programming... NEVER xD but for shaders.... hmm
  13. TheConceptBoy
    Ah, I see. Very well then.
  14. TheConceptBoy
    That sounds super useful gem. Why in the world is not NOT documented? How much more is there? Do we need to dive into the engine files to find out? EDIT: Ah... "unsupported" eh. If you use them then aren't they supported? Does it only work on a case to case basis or something?
  15. TheConceptBoy
    Now in this setting, I've basically voided the use of App.cpp and just deleted everything in the Mail.cpp file and used Leadwerks from scratch. I am curious, what is the purpose of all that pre-existing code in a freshly created main.cpp and App.cpp? Debugging routines or something of the sort?
  16. TheConceptBoy
  17. TheConceptBoy
    https://www.leadwerks.com/learn?page=API-Reference_Object_Context_Drawline
  18. TheConceptBoy
    The Description states: Cone? PS: I'm seeing your screen-shot. That looks like a collision mesh for the staircase. I see the precision setting to the right.
  19. TheConceptBoy
    https://www.leadwerks.com/learn?page=API-Reference_Object_Entity_Model_Sphere The sides parameter refers to a Cone, is this correct?
  20. TheConceptBoy
    I'm on it.
  21. TheConceptBoy
    I see, so generally speaking your player character, be it first person or 3rd person should be scaled to that cylinder then? What about vehicles? Things that are much bigger than the character that occupy them, Use rigid bodies in those cases?
  22. TheConceptBoy
    Thanks, Josh. Yeah I got that figured out lat night. The Physics Debug Mode helped me visualize it. So is the Cylinder Width hard coded into the engine? Someone said it's size is used for the navmesh calculation?
  23. TheConceptBoy
    Did you @Abstergo By any chance google this question and this is what popped up? Because I literally just posted this an hour ago. haha.
  24. TheConceptBoy
    Haha. I was experimenting with various shapes after a couple of hours of hair pulling. I got fed up with changing the variable names here and 20 other places.
  25. TheConceptBoy
    Oooh I see, it's a cylinder! that's the character controller collision shape. I see
© 2006-2020 Leadwerks Software
×
×
  • Create New...