[Some Challanges]

I found someone who made a new type of interpolation for this system. It's really great looking.

[Easy game creation]

This thread clearly branched off because all you troll-feeders forgot MakeFPSGame is a current working API command.

It's interesting, though.

[GetBoundingBoxSize]

^title. Could help greatly for height/width calculations.

[Exception handling in class constructors]

Try/Catch over class initialization is a perfectly fine practice, at least, in C#/.NET (in which exceptions play a major role). I see no reason to create a separate method.

[New here and wondernig about C# specifics]

Enough, I'm just done with Werkspace. Hire a guy who will make sloppy code that has nothing to do with C#, just a PInvoke file of your lib, and pay him hundreds of dollars. Rick, enjoy your vision of C#, that is, destroying the OOP it was meant for and using procedural commands. Actually, I won't even argue with anything. I'll do my C# headers for LE 3 and use them for myself. The rumour is pretty much right: Werkspace is an elitist community, and I'm done fighting that, I'll rather slip into the "snobs" (sic) who keep their code to themselves.

 

And to all potential buyers who view this reply (you probably won't, Josh will move it to the obscure C# forum), know that while Leadwerks is the best engine, Werkspace is the worst community.

[New here and wondernig about C# specifics]

I have provided the existing LE3 header, and am somewhat interested in C# support. I can't same more than that yet, because I don't know enough about C# to make a judgement. One problem is the getters and setters in C#, which are a nice language feature, but also lead to everyone making their own versions of commands they think is best, and it can deviate quite a lot from the original API. I would be much more comfortable with a class wrapper that duplicates the C++ classes exactly, and then let the C# people add whatever enhancement they like in a community add-on.

Well, it's the difference between "Foo.GetBar()" and "Foo.Bar", and "Foo.SetBar(Xin)" and "Foo.Bar = Xin". Honestly, since the variation is always similar, it can only be seen as a language limitation. I wouldn't spend time implementing Get and Set methods in C#, everyone any familiar with C# would spit on them.

[New here and wondernig about C# specifics]

So if we were able to get a Mono version of C# working you would support it? Mono is not Windows only.

 

 

 

I would make Mono compatible headers for LE 3. It's not that hard either.

You are this week Seriously anything .NET related to LE has people coming and going all the time. No offense to you since we don't know you, but when you see it over and over again, it's hard to think otherwise. Without the proper support from Josh it's always going to be this community effort that just doesn't get much traction.

Rick, please stop turning down the C# .NET community spirit or Leadwerks .NET for that matter, especially considering that you don't even intend to use it and stick with LE.NET. The community effort loses its momentum with comments like these.

[Need c# Wrapper]

Well that helps me decide betwen LE.Net and Leadwerks.Net. One less thing out of 938 I have to figure out. ;-)

 

Seriously though, I had pretty much decided that I would be writing my own OO layer given the upcoming changes for LE3.

 

Lazlo, in your experience implementing and working with Leadwerks.Net, what kind of PInvoke perf hit were you seeing when using LE.Net? Were there certain api's that became problematic?

 

In my experience with C#, when PInvoking an API design that results in many frequent API calls to fast functions can result in huge perf problems due to the invocation overhead. For example, math library invocations, coordinate transforms, etc. Doing them in a deep, tight loop can really slow things down. Did you run into this kind of problem, which required you to reimplement some of LE on th managed side to avoid the bottlenecks? Or worse, run into any such scnearios that you weren't able to workaround?

 

Any pointers or best practices or pitfalls worth mentioning? Other than GC woes?

 

If there are already such posts, please just link them here, and once I purchase I'll be able to read them.

 

Thanks,

Rhino

I could give you the SVN address with the latest source and binaries (DLL) if you want. The performance was near perfect, I saw no problem at all. The syntax is much better than that of any other language, but that's in my very own biased (but not humble) opinion. I intended to try to write a OO layer and possibly even an official one if Josh ever settles in on the idea, but go ahead if you wish to do so yourself. Leadwerks .NET was a very long design process.

[Need c# Wrapper]

I think I pretty much made my mind that I won't pursue any other community effort for C# (Leadwerks .NET) in LE 2. We'll see if Josh is interested for it in LE 3. I'm tired of fighting communities and rollbacks without any support.

[New here and wondernig about C# specifics]

Josh, please contact me if ever we are to set up an official C# header for LE3; including OOP wrapping, which will mimic the exact same structure as the C++ one.

 

As to the askers' question, LE .NET is no longer supported by Roland; it was, however, pretty stable.

Leadwerks .NET is not based on LE .NET. However, it is a ver C# .NET approach to Leadwerks, much more intuitive than the procedural commands.

With the massive rollbacks of the forum, Leadwerks .NET got deleted. I could repost it, but I'm in my finals at the moment, and I have no motivation to invest time in this, especially considering even the C# community is not very hot on the idea.

 

Hopefully Josh will take the C# demands into consideration for LE3.

[The Kingdom Of Soul]

The first of my waterfalls:

 

http://www.youtube.com/watch?v=kH5Ufb0jv2g

The vegetation on this is very crispy and good looking. The waterfall could use some work though, but I understand it's really hard to make (I myself have tried failed many times).

[Some Challanges]

You'd have to use clientside vector prediction and CalcBodyOmega / CalcBodyVelocity to achieve the desired movement. Calling the other "AddXXX" commands directly just gives you addititve physics, which is the complete opposite of what you want.

 

Optionally, you could use a simple spring to dampen the movement after you use AddBodyTorque or something similar; insanely high friction works as well.

Tyler what the?! Hi. Man... Argh. Come back!

 

And about that topic, I'd suggest frequent matrix updates with cubic spline interpolation.

[Some Challanges]

The page is http://www.assembla.com/spaces/leadwerks/, but I don't have time right now for a topic. Mind creating one for me? You could add this URL and the credentials, it would be nice

[Some Challanges]

By the way,

I would recommend using Leadwerks.Net, a different library than the shortened LE.Net. Lazlo would be able to offer the link since the forums were rolled back a month or so. There have been a lot of valuable updates to the library that make it very easy to use with VB or C#.

 

Oh really what the fawk. My links have been rolled back?

The credentials: leadwerks.chsarp/collaboration

[How to get started with C#?]

Here. Don't ask for details/explanations/features or anything else, I'm not into Leadwerks at the moment, neither is Tyler.

 

 

[LoadScene]

C# docs at http://middlewerks.com/headers/ are awful?

[Some questions regarding the controller]

Stop using Core! I'm making it Internal in the LE3 release. Gosh. Use the following:

if (playerController.LeadwerksType == EntityType.Model)
{
   playerController.Mass = 2;
}

[Just sending out a Howdy to All]

Welcome aboard. What language do you plan on using?

[Best Practices]

Agreed on all, although I still think Lua for prefabs is an overkill.

[what do you want see in leadwerks 3.0]

River nodes of course, but that's already planned.

I agree with darren, only Physics are an essential part of a game engine in my opinion (which is what Leadwerks is, now isn't it?). Besides, you cannot do anti-aliasing by yourself, else I would've done it long ago.

[[REQ] CreateJointUniversal]

Josh tends to sometimes remove functions "no one uses".

[Yet another flaw]

TTF fonts work on any system, when you use FreeType library.

+1 on that.

 

Besides, in which case do you render fonts out of screen? I'd say this is an exception in which you could translate the buffer, but not the other way around.

[How to add texture to my mesh?]

myMesh.Material = Material.Load("myMaterial.mat");

[Mouse picking]

?? how long could that possibly take?

Considering the fact that I don't want to release an in-between unstable version, that Tyler is gone and that no one gives feedback (despite the fact that it was asked repeatedly in my posts and blog) on how they want the C# headers, a while.

[Mouse picking]

You'll need the new version for working picks, apparently. Sorry, don't have time to upload it today.

 

When you pick something, however, remember you get the mesh. So any key set to the model won't be accessible. Use Pick.Entity.Parent to get the model of the mesh picked, I assume.