Jump to content
Ultra Engine Community

macklebee

Members
 View Profile  See their activity

  • Posts

    3,946

  • Joined

  • Last visited

 Content Type 

Blog Comments posted by macklebee

    Josh

    Posted

    Ctrl+H

    Find: "EntityPosition"

    Replace By: "EntitySetPosition"

     

    oh really? wow thanks :D ... if it was just one command I wouldn't have said anything... but he is talking about changing the syntax for almost every LE command, meaning that if you want to use any previously working code you would have to do this for every single command... which would mean troubleshooting the same code all over again.

     

    I would not count on any of your existing programs to compile verbatim in Leadwerks 3. It's a new engine with some differences in the commands and design.

     

    LE2 will continue to be supported, and any bugs will continue to be fixed. It's not in danger of becoming obsolete. If you have existing projects being written in LE2, I recommend you continue using LE2 and maybe use LE3 when you start a new one.

     

    The documentation for LE3 will not be in the wiki. It will be an entirely new docs system written provided by Leadwerks.

    No, I didn't expect it to compile verbatim since official bmax modules were being dropped, but the change of the standard syntax that we are all used to is kind of a shocker.

     

    And I am going to have to agree with lumooja, but not based on the "global standard". SetEntityPosition() has a lot more of a natural feeling than EntitySetPosition().

    Josh

    Posted

    The engine will be compiled as a DLL or static lib, and C command will be included. You don't need a separate header file.

     

    The commands will just be the class name followed by the method name. For anything that returns a value, the first part of the method name will be "get". For anything that sets a value, "set" will be used. For anything that queries a state, "is" will be used:

     

    entity->SetPosition(x,y,z)

    EntitySetPosition(entity,x,y,z)

    entity->IsHidden()

    EntityIsHidden(entity)

     

    ??So you are actually going to change the command syntax after all this time? Literally invalidating every existing line of code that has been currently written with the current command syntax? So where is the new command syntax going to be kept at? The wiki? So that means every command will have a listing for LE3.0 syntax and LE2.XX syntax?

    Flexman

    Posted

    No, I completely understand. Especially at your stage of development, upgrading the project is a daunting task since moving up from 2.31 will require you to have to reserialize all of your physics bodies. Its little things like this in the versions that can drive people crazy, and having to upgrade is not truly an option. That is why I have been trying to find as many bugs as possible lately and post anything that remotely looks like a bug. Once 3.0 goes into full scale production, getting previous issues resolved may be an impossibility.

    Josh

    Posted

    I've also seen what big money companies did to 3D programs like Hexagon and Bryce, when they took them over and it was very sad. It would be a shame to see the same happen to Leadwerks.

    agreed... fantastic intuitive software that basically just got shelved development-wise once taken over just to basically incorporate their ideas into the company's other software... which left everyone who had hexagon and bryce screwed with no hopes of improvements or bug fixes.

    kennar

    Posted

    The phy file created automatically in the editor is for static objects, which will be fine for your shanty town models. Any model that you wish to have dynamic physics interaction, you will need to use either phygen or obj2phy.

     

    As for getting properties for the models, try adding this to each model's lua script:

    require("scripts/class")
class=CreateClass(...)

    This will add the common properties that you can modify with the object's property dialog. I would set the shanty town buildings to SCENE in the collision option under the Physics tab.

     

    Something that might help you is the Leadwerks User Guide by Aggror. Its a nice resource for new users.

    DaveLee

    Posted

    Speaking of vertex coloring, you need to use it on your vegetation... the grass, leafy cover, and especially the "farn" ferns need to have the base of their models not moving (colored black) because they are attached to the ground. Then the rest of the vertices would be become lighter colors as you moved to the end of plant. Right now it looks like everything is kinda heaving and breathing... The overall looks great, but these little things are distracting from the overall feel of the Zone.

Copyright © 2024 Ultra Software.
All rights reserved.
×
×
  • Create New...