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

macklebee

Members
  • Content Count

    3,944
  • Joined

  • Last visited

Everything posted by macklebee

  1. slimwaffle - is this resolved or are you still having issues getting a terrain to deform? If so, post your example so we can try to replicate the issue. It's called being friendly. - macklebee
  2. The advice that was given was that models can be converted to other formats and ways to do conversions when my only concern was that I didn't want to waste time doing conversions? Like I said, Josh answered my question from his very first reply - it was all good from there. And actually that "couple of years" is over 15 years closer to 20, but just as tinkerer/hobbyist, but thanks for being a arrogant, *******, ******, ***************.about your credentials. Glad to have you here. Artists of your experience and skill level are few and far between around these parts as most do not want to
  3. Sorry to hear that you had issues when you updated to the beta. It was my understanding that the first time that you installed Leadwerks that it should have installed all the files you needed, including the VC++ redistributable? So I am surprised this is the first that this has come up since you have been using LE for some time now. Did you perhaps delete and re-install LE recently? If so, maybe the redistributable did not install properly during that time? This does apparently happen from time to time according to the posts I see on the Steam forum. As for the screen issues, hopefully Jo
  4. Thanks - I didn't know what the word "batch" meant! jeebus... That's fine and dandy - and if it comes to it, it's definitely something that i will try even though I think I would look for some commandline batch converter instead of trying to load thousands of assets into a blender scene. And speaking of key words, you are missing the key point repeated in all my posts: The only concern was having to spend a lot of time converting assets that currently work in LE to another format to work in the newer version of LE - not that I didn't know how to do conversions. And Josh answered exactl
  5. Or you know, I don't have to do anything because Josh is for the time being supporting other formats... and honestly, that doesn't sound very feasible at all. Trying to navigate a scene with hundreds or thousands of models to determine what to export, not to mention it doesn't sound very practical from a memory / file size standpoint, but to each his own. Still it would be time consuming endeavor to setup which was why I asked Josh about supporting other formats and he said he was going to...
  6. Yeah, man I know that you can convert models from one format to the other. I get it. I've done it. I will do it again in the future. The angst is not wanting to spend the enormous amount of time trying to convert a decades worth of files over to this format, if Josh decided to only support this format. Since Josh has stated he will be supporting other formats at least for the time being, I am satisfied. As it stands right now, essentially 90% of my assets are automatically accepted by LE by just simply starting the editor - that alone is an enormous benefit to any user.
  7. jeez dude... i hope they are paying you for this... I get it - you are a fan of this new format. The conversation was directed at Josh and he answered exactly what I wanted to hear. It's all good. We are both getting what we want.
  8. ooph - you don't have the source! that blows donkeys. Great that you are looking into new and exciting things - no complaints here about that. I just wasn't looking forward to having a decades worth of a models and textures asset catalog basically become useless in LE unless I convert it over to this gtfo format.
  9. Just as long as you keep some other format import options available other than this random GTFO format that until posted here most of us have never heard of - including yourself.
  10. hmmm. This still seems to be saving the same way as the Editor does where it overwrites the existing mipmaps. I am not seeing a difference when viewing with the above program. The second mipmap should look like this:
  11. Just a quick and dirty script to view the mipmaps saved inside a TEX file: window = Window:Create("texture detail example",0,0,800,600,Window.Titlebar+Window.Center) context = Context:Create(window) world = World:Create() camera = Camera:Create() tex = Texture:Load("Materials/beach_dirt_b.tex") mips = tex:CountMipmaps() while window:KeyDown(Key.Escape)==false do if window:Closed() then break end Time:Update() world:Update() world:Render() context:SetBlendMode(Blend.Alpha) for i = 0, mips-1 do Texture:SetDetail(i+1) if i <= 4 then context:DrawImage(tex,155*i,150,150,15
  12. I wonder if its due to the default settings for the editor when converting an image to TEX that it automatically saves it as DXT1 and with the 'Generate Mipmaps' option selected? Is it overwriting your mipmaps because of this? These have always been settings i wish we had control over instead of them just being hard-written as the defaults.
  13. Did you try my example? Does it work for you? You are not giving us enough information to determine if its something you are doing wrong or its a problem with LE. What version are you using? Give us a simple example to try. And again, the height value is on scale of 0 to 1. This simple example works for me: window = Window:Create("terrain example",0,0,800,600,Window.Titlebar+Window.Center) context = Context:Create(window) world = World:Create() camera = Camera:Create() camera:SetPosition(0,30,-30) camera:SetRotation(45,0,0) camera:SetMultisampleMode(8) light = DirectionalLight:
  14. The height value in SetHeight() is normalized from 0 to 1 where 1 is equal to the max altitude of the terrain. Altitude of the terrain is set by SetScale() via code or via the Editor terrain settings, so you would need to normalize the height you want in regards to the max altitude being equal to 1. Another thing to keep in mind: a terrain position is not the same as the world position. For example: on a 64m x 64m terrain, the world origin (0,0,0) would be located at X=32 & Z =32 on a flat terrain when using SetHeight(). Example showing SetHeight() in action: window = Window:Creat
  15. Without seeing this in action and the rest of your code, its hard to tell what exactly the issue could be. Why are you aligning the entity by 90 degrees in the X-axis as well? Seems like what you are trying to achieve based on your description could be solved just by setting the 'self.otherEntity' rotation by using SetRotation()? But again, just a guess since no example to test.
  16. weird. yes no one is going to do a direct export to xbox with LE. This would require your code to be engine independent and that all your assets are of a common format and not just LE formats. Even then the licensing and the game developer kit itself has always been restrictive. Great that you have these dreams, but you should probably focus on just getting something first that works on a pc before worrying about publishing.
  17. At this point, I think its the code the OP isn't showing us that is the problem or at least maybe how the pick is working for camera collision. The code he posted doesn't do anything but set the camera at the 'chassis' position and allows the user to rotate the camera.That code does not point the camera at the car, it does not automatically move the camera if behind a wall, and it doesn't allow the user to move the camera closer or farther away from the 'chassis' like what is shown in his videos. The jitter, since he is making us guess, is probably due to the pick hitting the wheels briefly in
  18. Yes, the LE API is for LE commands. And yes, potentially (depending on the script and its function) you could adapt other lua scripts into a LE lua script.
  19. The only lua commands that will only work in LE are the LE API commands listed in the API Reference and obviously the Script class that is available for LE scripts. Actual inherent lua commands can be used wherever lua is used (with obvious considerations given to the different versions over the years). Refer to actual lua programming sites for reference: http://pgl.yoyo.org/luai/i/_ http://lua-users.org/wiki/TutorialDirectory http://www.lua.org/pil/contents.html
  20. Impossible. In your videos, the camera is changing positions if behind walls and is allowing you to move the camera close and away from the vehicle. The code you posted only allows the user to change the rotation of the camera and not the position. EDIT - you can make as many videos as you want, but without an example we cannot troubleshoot your issue.
  21. Thanks - but I think Marcousik has that file. I am looking for the script and now i cannot find it either. Oh well, I think the bigger issue above is that it appears the OP has two sets of code setting the camera position and possibly fighting each other. Or at least the collision code and however the pick properties are set is causing it to bounce position.
  22. There's been a lot of iterations apparently. I was going to use the 3rdPersonFollow script as an example that has similar code but that's no longer supplied with the software.
  23. You need to interpolate the camera's position to the next position over time or you will get quick jumps like that in movement. Use the Math:Curve() to smoothly transition between positions. Now if some of the jerkiness is due to the pivot bouncing with the stuttering vehicle joints, that might be another problem. EDIT--Also - it appears you have implemented some sort of camera collision/pick which is not a part of the code you posted above that is moving the camera as well. If this is the case, then you need to show that code as well or even better post an example that shows
  24. Yes, you can open the zip but can you actually access any of the files? Try it. If it works like everyone else's zip file, it will ask for a password. EDIT -- gamecreator beat me to it.
Facebook Twitter Youtube Github Steam
×
×
  • Create New...