reepblue

I'll be sure to give this a try this week.

Making any app 64 bit will not magically make the run better. It's about memory and thread management. Leadwerks at it's core was supposed to run on mobile devices from 2010-2012 at the start. Turbo is Leadwerks but multithreaded and uses a more modern C++ standard. (And other cool stuff..) Turbo is in beta but it's not production ready yet. It's more for tinkerer's and helps financially support development. I'd stay tuned for more information and to see what happens.

Leadwerks is a 32bit library. You'll have to wait for Turbo Game Engine for 64bit support.

Imo, it should be up to the end user to decide how they want to build their systems. The engine should do just this, allow multiple scripts to be attached to the entire and handle duplications if there is any. Would I personally attach multiple scripts with the same function and value names? Most likely not, but that's my choice as a programmer. Multiple scripts will remove needing to rewrite effects per object type and allow things to be more modular. I see this as another tool in the toolbox. As long as it doesn't hinder what a programmer wants to do (Like if Rick wants to use an event system.) Its fine by me.

I'll probably never use the multiple return value feature and mostly stick with mono-scripting mostly However, it's really cool to have multiple script attachments for those cases in which multiple scripts would make sense. I rarely run into it, but it does happen. Overall the Lua implementation looks much better than it is in Leadwerks. Really stoked about using an entity as a table for other scripts to add, remove or manipulate. You made this much better, hopefully you can hit the same bar with the flowgraph/io system. ?

I've uploaded a new release last night correcting the player's pickup to be much more reliable. It should be very rare for a case in which the player is in a object and releases it causing the player to fly backward. I could have kept objects solid but that caused another can of worms. I also posted this on my OneDrive due to issues of people not being able to download it from this site. Yesterday I was working on implementation of the power balls and the launcher. I've written a rough draft of this a few weeks ago and I had it fully working in normal player code. When I started to work on the VR version, that's when I started to run into some problems. First, I didn't like how the code was looking. It involved a lot of referencing of entities and classes. What made it hard is that the VR implementation was different from the normal players. What didn't help was after too many restarts of my application with VR enabled, the entirety of Steam would just crash. So developing for VR was very frustrating. With Turbo coming a long, I wanted my code to work with little modification as possible. I've written a function wrapper that'll only be called if the application is ran under Leadwerks. This both will save time in replacing these functions when the time comes, and get's me used to the new functions. One thing I'd still have to fix is how Lua is implemented in the new engine. Most of the heavy functionalities are in classes which will defiantly keep self.entity for referring to the entity it's being used on. However somethings will still need to be changed and there are a lot of unknowns right now. With that being said, I think it's safe to say it'll be best to focus on the art and assets going forward. With the amount of time I have to make these assets, I'm sure more clarification with Lua scripts with the new engine will surface, maybe even a beta to play with. But with it being Leadwerks or Turbo, they both need assets. VR mode will also be dropped for now. It'll still be there, just not fully supported. You'll need to run the app with -devmode to see the VR tab now. After the project transitions into Turbo, VR development will continue. I shall be going back to my Linux machine with my ultra wide color calibrated monitor to work on these assets. I've created a lot of Vectronic themed stuff in the past and I'm going to go through it and see what I can savage from it. All my models are done in Blender, and I want to create all textures in GIMP this way my files can be used with free and open sourced tools. Also, if there is any Linux developers who wish to use this package, they don't have to be hit in the face with Maya and Photoshop files. Releases will slow down, but I'll be posting screenshots of my work soon.

The following is included in this release: Fixed player's pick up in which the object will not drop when the player is in the object's global aabb space. Replaced the player's model to shrink player's AABB radius. Disabled the VR tab of the launcher in Linux. Due to issues with the last release, I've uploaded it on my OneDrive. https://1drv.ms/u/s!AunSDJ8Se0vXiTXauNe965YH_H5n

Neat, but will the complete functions be exposed as well? I'm hoping to convert LE scripts to Turbo when this ships.

Will this be in the next beta and how many classes will be exposed?

There is also SetPhysicsPosition()...

Ok, thanks for your input. I'll see if others have an issue. If you can, try another browser. In the meantime, I'll look into other hosting options for alternatives for the next build. Thanks.

That feature is not present under the Linux build. ?

For who those who don't know (or remember) Vectronic was my first person puzzler project I was developing from 2013-2016 starting with the Source Engine and then onto Leadwerks. The goal of the project was to create a puzzle game and allow people the assets to make their own puzzles. Although it never saw it's end, you can still play the demo here. So what happened? Vectronic was how I pretty much learned a lot about programing, art and game design in general. I kept going back working on it for a month or so and then stop because I would hit a road block with assets, code, performance, or time. I made a lot of cool things too that just never saw the light. Over the years however, I also noticed I don't have patience to work on one game alone for months at a time. I do however like to play around with stuff so I began to think: "What if I had a project for me to tinker with and post it publicly every so often?" I'm more busy than I was in the past so time is more limited. However, I've probably written Vectronic game code over 50 times and I now know the right way of doing such. So what's the plan? After some experimentation, I've decided to go ahead and start a new project taking everything I did and learned with Vectronic and making a base template for people can use for their own purposes. My packaged game will be free to download and play (Because it's just me playing around) while the assets and will be posted on the Leadwerks Marketplace for a charge.The package will contain all assets to build your own test chambers, and you'll also get the original source files too! My release game will act as an outlet to my tinkerings and provide as an advertisement to the asset pack. With the code, the idea is that everything will be modular and users can easily create their own power balls to do various of things. The power balls can now be applied to any entity under certain conditions so there is no need for a VecBox.lua script anymore. There will be plenty of examples for many to see how things were done. I learn best by references and examples, and having code, art, and maps accessible should help new users into learning game design, or aiding developers in assets to start their ideas. I've decided to change the name to Vec-Tec as the asset pack will be in the Vec-Tec Research Center. Also with the new approach, I think it's time to drop the name Ive been using for four years. You can give Vec-Tec a try right now here! It's very minimal, there is no art, but the foundation is there. VR is now gonna be a thing with this, If you have a VR HMD, you can play any map in Roomscale VR! I hope this is a start of a remarkable development. I hope you are interested and see value in this project. You can find the project page here for the latest updates and releases.

This is the initial version of Vec-Tec, the reincarnation project of Vectronic. The goal of this project is to build a asset package for education and experimentation. The following is included in this release: Launcher app: This window calls before the game loop starts. Here is where you set your map, settings, and VR mode. The player is interchangeable, one player for spawn for VR and non-VR. Both players can move around the world and pickup objects. The VR teleport is nerved from the template to be more closer with the physical movement of the non-VR player. If you have an issue with Linux, make sure you use chmod under super user (sudo) to allow you to execute the program. VecTec-180923.zip

Line 280: Change: #ifdef USEPOSITIONBUFFER //VR Sheared mprojection vec3 screencoord = texelFetch(texture4,icoord,i).xyz; s creencoord.y *= -1.0f; #else vec3 screencoord = vec3(((gl_FragCoord.x/buffersize.x)-0.5) * 2.0 * (buffersize.x/buffersize.y),((-gl_FragCoord.y/buffersize.y)+0.5) * 2.0,depthToPosition(depth,camerarange)); screencoord.x *= screencoord.z / camerazoom; screencoord.y *= -screencoord.z / camerazoom; #endif To: #ifdef USEPOSITIONBUFFER //VR Sheared mprojection vec3 screencoord = texelFetch(texture4,icoord,i).xyz; screencoord.y *= -1.0f; #else vec3 screencoord = vec3(((gl_FragCoord.x/buffersize.x)-0.5) * 2.0 * (buffersize.x/buffersize.y),((-gl_FragCoord.y/buffersize.y)+0.5) * 2.0,depthToPosition(depth,camerarange)); screencoord.x *= screencoord.z / camerazoom; screencoord.y *= -screencoord.z / camerazoom; #endif ?

Try waking it up with entity:AddForce(0,0,0). The physics must be awake to call the collision function.

Luawerks has been updated to 1.2.6, making some small adjustments and fixes to the system. If you have previously purchased Luawerks, this update is available for free on the Leadwerks Marketplace. Following changes include: Fixed flag typo correcting LUAWORKS to LUAWERKS Moved error.mat/tex to the Materials/Common folder Added a useuisystem boolean to disable the menu, Adjusted VR mode not to call any UI elements. At this time, this update is only exclusive to the Leadwerks Marketplace. About Luawerks Luawerks is a Lua framework for video games developed on the Leadwerks Game Engine. It supplies developers with additional functions, handles the game loop and allows them to debug their code with a developers console. With all that out of the way, you can focus on making your game fun! You can purchase Luawerks from the Leadwerks Marketplace for $9.99. For documentation and bug reporting, please visit the GitHub page.

Very cool. Glad you're back in the States. Although Turbo is still the priority, I hope this NASA contact benefits LE4 while Turbo is being worked on. Would be nice to see bugs fixed and more VR options soon. Also hopefully this means you're not tied to that Gigabyte box so I also hope to see AMD and Linux support with the new engine. (And continued support for LE4.) Congratulations, and continue making cool stuff!

It sounds like he is having issues with the editor. I was having issues running game executables after installing the dev libraries. You sure all you did was install steam and Leadwerks? If it's a new install please provide any other apps/packages that might cause conflicts.

Other software can prevent full screen from working too. I had the Samsung Magician running that did something similar to what's happening here. Try going back to 4.5 first as 4.6 beta hasn't been updated in months.

A long time ago, there was an app on Steam called The Leadwerks Game player. It's goal at the time was to allow people to upload their lua games to an audience without going through Greenlight at the time. The app used the workshop system to achieve this. In order for this to work, Valve required that no games should be able to modiy the users system to prevent malicious code, hence why sandbox mode was created. Although cool, the app bombed. Sandbox mode is a relic of that time and just gets in the way these days. You don't need to really worry about this when it comes to publishing as a stand alone app id.

If there is an editor and C++ is more of a focus, I see it as "functional enough for development." With VR in Leadwerks today, there seems to be less control with the API than other options. No rotation support, can't change the controllers, idk how to hide the sensors, and my previous bug report. I also got random screen issues with the right eye. Best way to describe it it's like being half way underwater but it's vertical. When you are near your VR setup again, let me know, I'll send over the project. Could be AMD also, idk. And with the Rift, Steam VR keeps crashing randomly; taking Leadwerks and Steam with it but that's really not your fault.

I'm not sure why that was written there. Those files were never included.

At this point, do you think Turbo be ready to be developed for or you plan to show and release Leadwerks with the new forward rendering system? I hope VR is improved in the engine and has a few more features at this point. I was playing around with it with my Rift and it was quite a chore to develop for. Not sure if this goes for the Vive. Oh, one thing you can also do is show all this running on Linux. Not many options have a native Linux editor and tools. ?

You do not want to have the actual map file, rather snapshot the current values of a point in time and have the game reload all that information upon a restart. The best save system imo is with Source Engine games in which everything is saved, but most other games just worry about player data and npc count.