klepto2

Nice suggestions Lazlo. - Scilexer.dll doesn't need to be distributed as it is just for the scripteditor and not needed for the engine itself. - Currently i notice that a lot of bmx users also distribut engine.dll --> not needed in bmx. - I remember a chat with Josh about having Scripts in a pak file and I also rememer that this should be possible with > 2.32. @Rick he means the model scripts, not the general script folder. - I have a Batch Asset creator in the works. I have already converted > 300MB Packages from Arteria and Dexsoft in less than 5 minutes. Currently it is just a prototype, but it already let you convert from GMF, FBX, Obj to GMF format. Rescaling is implemented and it autogenerates materials if it can't find proper materials. It also generates normalmaps and simple scripts. Currently the pipeline is not that easy as it sounds, but this is what i'm currently working on. Least it packs the converted models into a clean ordered Folder. Otherwise +1 for the other things.

Which engine.dll do you use? If i remember correctly you need the 2.3 dlls and not the 2.4 dlls.

You need to copy the engine.dll, newton.dll, jointlibrary.dll, shader.pak and if you use scripting the whole Script Folder into the Output Folder of your app (both, debug and release)

Rick, here is a new version:Klepto.Controls.dll Changes: - Added an AfterFrameworkRender eventhandler, please test if this helps and works - Fixed MouseZ bug. btw, its no problem that you find bugs thats why i call this beta. PS: the FPS thing is something i need to work on. Somehow the TKcontrol limits the rendering speed and the timer is a also a bit weird. Currently I'm experimenting with BackgroundWorkers which should work better. [Edit] Changes: - Changed Timing from timer to backgroundworker. RefreshRate works now correct, set RefreshRate to -1 for fullspeed.

Ok, here we go last update for today changes: MouseX/ MouseY will update now after mousemove experimental MouseRelease the behaviour of MouseHit and MouseDown is different. Whereas MouseDown just checks if a button is pressed, Mousehit returns the number of clicks since the last time the given button was clicked. Klepto.Controls.dll

ups, you're right. the MouseMove indead is hardcoded to the middle of the screen. I knew why i called it beta Well, ok, it was one of the last commands i added so i was a bit unconcentrated. Fixed Control assembly: Klepto.Controls.dll

This happens if you don't have all LE dlls in the bin/Debug or bin/Release folder. Copy the engine.dll, newton.dll and jointlibrary.dll into these folder. I will maintain both, Forms and WPF. WPF is just the Forms control hostet in WPF. I also had trouble to come into WPF but once you get into it its beautyfull. OK useless for Editors which needs highperformance, but other applications are done much easier and faster with WPF.

Hi, here is a new Version of the LE-TKControl (binary only currently). The Sample has a subfolder containing all needed assemblies (excluding regular SDK dlls). Whats new: - Framework compatibility - Polled Input What to do: - Cleanup the code - Fix some minor issues (update timing) - Porting it to WPF - Add some overloads to the current polled input functions Changes: - Namespace has changed to Klepto.Controls because i have added it to my own GameEngine. I will go back to Leadwerks Namespace as soon as it is stable enough - Instead of 1 Render Event there are now 3 Events (Pre, Main and After) makes handling of Framework drawing easier - Handles the Framework rendering automatically if you use rendercontext.InitFramework(useLua) Download : LESDK Control.zip Have Fun!

sorry Rick, it takes a bit longer as i thought. I need to fix a bug with the release of the control. But i hope that i can upload it today.

Hi, I just want to inform you that i will release a newer Version of this Control Thursday or Friday. There will be a lot of new small functions in the control which will make the handlicng of the Control much easier. A short summary: Handling of PolledInput with the same function like the raw version of Leadwerks MoveMouse, KeyDown, KeyHit, MouseHit, etc. You will be able to assign a Framework directly to the control so the buffer rendering is done internal And this is how the current Cam View code looks like in the control: if (RenderContext.MouseDown(MouseButtons.Left)) { //Camera look mx = Maths.Curve(RenderContext.MouseX() - RenderContext.Width/2, mx, 6); my = Maths.Curve(RenderContext.MouseY() - RenderContext.Height/2, my, 6); RenderContext.MoveMouse(RenderContext.Width/2, RenderContext.Height/2); // Leadwerks.Mouse.Move(RenderContext.Width / 2 , RenderContext.Height / 2 ); camrotation.X = camrotation.X + my/5.0f; camrotation.Y = camrotation.Y - mx/5.0f; Leadwerks.Framework.Layers.Main.Camera.Rotation = camrotation; } move = Maths.Curve( (float) (Convert.ToDouble(RenderContext.KeyDown(Key.W)) - Convert.ToDouble(RenderContext.KeyDown(Key.S))), move, 20); strafe = Maths.Curve( (float) (Convert.ToDouble(RenderContext.KeyDown(Key.D)) - Convert.ToDouble(RenderContext.KeyDown(Key.A))), strafe, 20); Leadwerks.Framework.Layers.Main.Camera.Move(new Vector3(strafe/10.0f, 0, move/10.0f)); This code gives the same smooth results as the original one. Also the MoveMouse method already takes the control offset into acount so no offset is needed.

This looks like it was mine You need VisualStudio Professional if I remember correctly. In VS Pro you have a button called 'View Class Diagram' in the solution explorer for each project. This will generate the right picture (well some adjustments may be needed).

Ok, the buffer thing maybe due to wrong timer initialisation. So it tries to update the buffer before LE is initialised. This should be a minor issue and easy to solve. The issue with using events is a bit more complicated. The problem is that the events and the redraw maybe asyncron. So you press the key, update the camera but the next frame will not be updated. To solve this you can do the following: private bool KeyW = false; private bool KeyS = false; private bool KeyA = false; private bool KeyD = false; private void RenderContext_PreviewKeyDown(object sender, PreviewKeyDownEventArgs e) { if (e.KeyCode == Keys.W) KeyW = true; if (e.KeyCode == Keys.S) KeyS = true; if (e.KeyCode == Keys.A) KeyA = true; if (e.KeyCode == Keys.D) KeyD = true; } private void RenderContext_KeyUp(object sender, KeyEventArgs e) { if (e.KeyCode == Keys.W) KeyW = false; if (e.KeyCode == Keys.S) KeyS = false; if (e.KeyCode == Keys.A) KeyA = false; if (e.KeyCode == Keys.D) KeyD = false; } And in the main loop do the standard Move code move = Maths.Curve((float)(Convert.ToDouble(KeyW) - Convert.ToDouble(KeyS)), move, 20); strafe = Maths.Curve((float)(Convert.ToDouble(KeyD) - Convert.ToDouble(KeyA)), strafe, 20); Framework.Layers.Main.Camera.Move(new Vector3(strafe / 10.0f, 0, move / 10.0f)); I will add a similar eventhandling like the original LE Polledinput later. eg: LETKControl.KeyDown(Key.A) or something like this.

Are you using the latest R5 dll? Graphics doesn't need to be called, as it would create an own gfxcontext which we don't want.

Yes it should. Well i havn't tried it yet, but others already have used VB.Net with this control. I'm also working on a WPF Control. But this is a bit more difficult as WPF uses DirectX natively and i need to wrap the Forms Control to a WPF control.

Its exactly the same control which is contained in the SVN Version. So you don't need a prebuilt one.

After revisiting the TKControl again I wasn't able to find a big bug or anything else i have made wrong (ok the refreshrate calculation is buggy) but then i have tried to get the Framework to work with the LETKControl and : Success!!! As said, there is nothing wrong with the Control itself, but something small is needed to get the Control working with the Framework. Here is the code: using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using Leadwerks; namespace Leadwerks_FormsFramewerk_Test { public partial class Form1 : Form { private Leadwerks.Buffer buffer; public Form1() { InitializeComponent(); } private void RenderContext_Init(object sender, EventArgs e) { Leadwerks.FileSystem.AbstractPath = @"D:\LESDK232r5"; //Create a render buffer buffer = new Leadwerks.Buffer(RenderContext.Width, RenderContext.Height, (int)(BufferType.Color | BufferType.Depth | BufferType.Normal)); RenderContext.Start(); Leadwerks.Framework.Initialize(true); Leadwerks.Framework.StatisticMode = StatisticMode.Detailed; Leadwerks.Scene scene = Scene.Load("abstract::Test.sbx"); Framework.Layers.Main.Camera.Position = new Vector3(4, 3, -4); Framework.Layers.Main.Camera.Point(new Pivot()); } private void RenderContext_Redraw(object sender, EventArgs e) { //Set the created renderbuffer as current buffer and let LE render to it Leadwerks.Buffer.Current = buffer;//Leadwerks.Buffer.Back; Leadwerks.Framework.Update(); Leadwerks.Framework.Render(); //Set the buffer of the Control as current and draw the flipped image of the 'framework' buffer Leadwerks.Buffer.Current = RenderContext.Buffer; Leadwerks.Drawing.Image(buffer.GetColorTexture(0), 0, RenderContext.Buffer.Height, RenderContext.Buffer.Width, -RenderContext.Buffer.Height); } private void RenderContext_Resize(object sender, EventArgs e) { buffer = new Leadwerks.Buffer(RenderContext.Width, RenderContext.Height, (int)(BufferType.Color | BufferType.Depth | BufferType.Normal)); } private void RenderContext_KeyDown(object sender, KeyEventArgs e) { if (e.KeyCode == Keys.Q) Framework.Layers.Main.Camera.Move(new Vector3(0, 1 * Leadwerks.Core.AppSpeed(), 0)); if (e.KeyCode == Keys.Y) Framework.Layers.Main.Camera.Move(new Vector3(0, -1 * Leadwerks.Core.AppSpeed(), 0)); } } } I hope this will help you. I will now try to integrate this a bit more into the control so that you won't need to handle this by your own.

Hi, I'm still working on this issue. The polled Input is working, but in another way then the usual way in leadwerks. you have handle the correct events. In the Formssample you need this: private void RenderContext_KeyDown(object sender, KeyEventArgs e) { if (e.KeyCode == Keys.W) cam.Move(new Vector3(0.0f, 0.0f, 1.0f * Core.AppSpeed())); if (e.KeyCode == Keys.S) cam.Move(new Vector3(0.0f, 0.0f, -1.0f * Core.AppSpeed())); } And this: this.RenderContext.KeyDown += new System.Windows.Forms.KeyEventHandler(this.RenderContext_KeyDown);

I'm using LE. but not for the 2D Part. The 2D part is my own 2D framework usin OpenGL.

Hi guys, I have made some small progress on my gui system the last few days. Nothing fancy, but believe me there where a lot of changes under the hood and now I can show you a first skinned screenshot: As you see the base skinning part is done. Well it will develope further with later gadgets, but the base part is done. You can have multiple skins running in one application, so you can have your main gui in your own game style and another like an ingame pc with a WinXP skin. One other thing which is special about this picture: The 2D part isn't using a single part (except Texture loading, which may also change later) from the Leadwerks Engine. OK Buffers are still used as well as Textures, but the whole Drawingpart of images uses my own 2D Framework. A small code can show you how the logo is drawn on the right of the above image: Local img:TLEImage = TLEImage.Load("abstract::lelogo.dds") ... TLeGui.RenderGui(camera) BeginLE2D() TLe2DHelper.SetBlend(ALPHABLEND) TLEImage.DrawImageRect(img, GraphicsWidth() - 320, GraphicsHeight() - 100, 320, 100) TLEImage.DrawSubImageRect(img, 200, 300, 32, 20, 5, 5, 120, 120) EndLE2D() Flip() The commands are a bit inspired by Max2D as you may have noticed. Also you see the second DrawImage command, this command draws a subimage of the source image. Currently my 2D system supports: Completely new TLEImage Some Primitives Transformations (rotation,scaling,...) Blendmodes, Colors, and some small other things. I hope you enjoyed the read. See ya at my next entry.

Maybe we should switch the forum language to Esperanto

Ok, as said in my last post i will make an advanced 2d system and a gui. I have now decided to start with the gui and add 2d Functions on demand. Here is a first screen, nothing special, but it shows some progress: Note the correct rendering of the window at the cube. I'm using one of my first 2D additions, SetScale , to mirror the rendering correctly for the texture. What does the renderer currently do: Every control is itself contained in a buffer which is only updated if it is marked as dirty. the rendering goes up the parents tree and each control buffer is renderend into its parents buffer at the desired location. With this technique i only need to draw one Image most of the time to represent a root gui element. I will keep you informed.

I'm also from Germany and I'm also against undersections for different languages. If someone will have a german or other language forum he may build up a fan forum in the specific language like it is done over at Blitzbasic. But with this together i don't believe it is currently a good idea to "split" the users by their language because of different points: 1. The userbase for each language is not that big that an own forum will need 2. This is quite young engine and the whole power and support should be bundled exactly where it is. 3. You can contact people in your language via PM if you have a question or need help translating a question to English. My English is of course far from perfect, but i never had a problem to post a question and i doubt this will be a problem for anyone. Well, it may take a bit longer to formulate the questions but it is a good training for school and later jobs where english is needed nearly everywhere. At least english is essential for a programer you will find most technical papers in english, programming languages have mostly an english command set and most bigger support/help forums are english. Also it is no standard for technical communities. PS: Standart gibt es nicht, oder sprichst du von Stehkunst?

After a forced break from programming with Leadwerks Engine, due to Work and other not 3D related Projects, I have started yesterday to come back to my Leadwerks project. As I'm continuing my project, I'm developing some extension for my own needs and if they are needed and good enough i will publish standalone addons here. The first project will be somekind of Leadwerks2D. It will offer a richer 2D function set than the current one. eg: Rotation, scaling, origin handling and new primitives with advanced options. The first project with LE2d will be a small skinnable gui system with the goal to provide an easy and flexible ingame gui system. One feature will be that you can attach a "rendertarget" to the gui and eg have the gui on 3D Objects. I will keep you informed on any News and post screens etc as soon as something showable is produced.

Unfortunatly the LETKControl doesn't work with Framework. I'm working on this issue but haven't found a working solution by now.

this looks promising, but take a look at this: http://www-evasion.imag.fr/Membres/Eric.Bruneton/ the source is available and it is using OpenGL and GLSL so it may be possible to use. I'm currently trying to implement some of the features myself.