Jump to content

Alienhead

Developers
  • Posts

    620
  • Joined

Everything posted by Alienhead

  1. The invasion has begun! Over the course of the next few months I'm going to slowly but surely convert this game over to UltraEngine while still completing the full game in LE. I figured this would be a good testing grounds to help bring me to grips with the new engine. I can't wait to see this running in Ultra where I can up the invaders count from 60 to about 200. :)> More later!
  2. Some info on the latest Radeon drivers, seems to community is upset with them Still very much broken: Run a 3d load (moderately demanding game) Tab out Open a browser (maximized) Open task manager - sort by power usage Start shuffling the mouse through your taskbar icons Watch as Radeon Host Service skyrockets to Very High, and brace for a driver crash I made a topic on this sub, that got swept under the rug (tech megathread) I knew I should had went back to Geforce, but at that time geforce chips were SKY HIGH and I got a fast radeon for under $300. Oh well.. lesson learned.
  3. I find it way cool that you can create a terrain, move it around like a normal object, then create another one next to it! all with their own nav meshes.. oh man the game ideas are flooding my head as we speak. Excuse my random babbling, I'm still in the ewww--ahhh stages of discovering features.. and I can't get over the clean, crispness of the rendering for a real-time time engine. Any instructions on setting up Vcode with the debugger and instructions on getting the code editor to run Ultra scripts? doh - https://marketplace.visualstudio.com/items?itemName=devCAT.lua-debug
  4. Hey good news, the dev version works for me, was able to create a terrain ( any size ) and save and load without problems on both AMD systems. Still cant go single viewport though, it expands the window and everything looks fine but it locks up and eventually closes without warning.. but at least i can work on a map now and reload it.
  5. Lua 5.4 introduced CONSTANTS at least. phew.. they getting closer to STRICT :>)
  6. I have another system, a little lower specs built on AMD tech. I'm going to see what happens on it.
  7. Desktop ryzen 5 5600x, 32gb ram, 770watt PS, 2gb ssdrive, radeon 6600rx
  8. I made a 64x64 terrain, it seems it got hung up for about 30 secs, amd crash report came up.. anyways went to restart the editor, and it crashes before the editor ever loads. I'm not sure if you are wanting all these error reports at this time but thought I'd mention it, I'm really stuck right now. Most everything I try results in this crash, I have to uninstall the entire package and reinstall to get back in the editor.
  9. After saving a map file, regardless if an entity is parenting or not - results in editor crashing as soon I try to start the editor up again. I created just a brush box and saved it as Map1.ultra, silent crash on next load up.
  10. On Radeon 6600Rx the editor crashes when switching to a single viewport.. Geforce is ok.
  11. Soft Shadows in Leadwerks? No way. . A lot cheaper than directional lighting... still got some ends to clear up but it appears to be a go!.
  12. This has been a challenge but with lots of shader rewrite and help from philliphaven, I am now able to say I got ssao, bloom, irsadjust, outliner, godrays, volumetric clouds, rim liner, and toonSat all behaving with each other. Now to squeeze in some Fov/dof
  13. Another look, another color palette, after messing with these colors for a few hours straight it all starts looing the same hehe.. this is probably the setup im going to run with. break time.
  14. A new look at toon shading. Any ideas, or suggestions on this look? tyvm.
  15. Of course it is, one of the best engines I've ever used to be honest.. It runs excellent on older hardware so if your planning on distributing a game made with it you have pretty much have the full spectrum of pc-gamers at your fingertips. Newer engines are to much worried about rendering, and super-exposed realism effects and PBR's when in fact only ' Only 8.2 percent' of the PC-gaming community have rigs capable of handling such engines ( quoted from google AI ) and actually even lesser than that if you break it down to pc, ios, linux, webgl and WebGPU support. I have a fairly decent modern gaming PC and I can hardly run the slower-than hell Unreal Engine editor. So if your targeting that 8.2% then your audience is very slim, while Leadwerks gives you the full spectrum pretty much. The only sad thing with LE is it's abandonment, it needs some repair in quite a few areas to put it on the map as a top 10 engine for older to mid range pc gamers. The next engine I pick will have to offer LTS, at least bugs that are apparent could be fixed since the product is still publicly sold.. With all that said however, I'll continue to use it until greener pastures are found. If Ultra offered rendering-pipeline options it could be that engine but that's a lot to ask for from an engine made by a single person.
  16. I'm pretty sure we don't have engine source code with the install.
  17. It would be really cool and helpful to have say like 3 to 4 different 'very short' game simulations to demonstrate the flexibility of the engine, this thread is not the first time, or the first place for that matter, I've heard people discuss Ultra as a first person shooter engine ala gameguru. Even Leadwerks was deemed as a 1st person shooter engine but as we all know that is far from the truth. 1) 3rd person template 2) 1st person shooter 3) tow-down click and go template. 4) perhaps a driving sim. etc..etc.. I understand this is not part of the engine's duties but when you unveil the release it sure would help the masses on deciding which engine to go with since there are literally dozens of AAA game engines available at this time and for free. In most cases you only get one shot at showing off the power of Ultra engine before the potential customer drifts elsewhere. Times are quite a bit different than when Leadwerks was released. All this wasn't really required back then - however the market was just starting and options were limited. You've put a TON of work into ULTRA, and that's just in the past 2 years I've been hanging around here. Ultra deserves to have the same validity as other 'team-based' developed engines have/had.
  18. I haven't posted anything in quite sometime, I thought I'd take this time to display my latest work, this is a spin off of AvBot ( a small gamejam I did last year a featuring Bullethell theme), but built around real game elements, it was to be a Towerdefense gamejam entry but due to a loss in my family I had no time to finish it and meet the deadlines. So I'm taking my time on it and creating what I feel is one of the more fun Tower Defense games you could ever hope to play. I'll do a video sometime this weekend. Introducing what I call a Toonville shader - all in one shader that handles ssao, edge enhancements, fov, outliner, rim and outline distortion all in one package. Many many thanks to HavenPhillip| whom laid the foundation for most of what went into the shader, it would not had happened without his Blogs and continuous support on ssao as I slowly but surely grasped shader coding.. The game is already playable to an extent, I'm starting the optimize and polish stages, then I want to add some cool UI to it and create a handful of maps. Should be done before the new year! I'm also considering placing it on Steam's EA or perhaps itchio's Refinery, haven't decided yet.
  19. Yes, your media within the zip cannot be touched. No way, no how. I had deleted on accident, a project GameJam awhile back, the only access I had to the models from that project were in that zip file. Even with the best compression hack software I failed miserably until I eventually gave up. lol.
  20. 9 times out of 10 you are missing some media, only things in code that use the load function get moved to the zip. if your loading filename with a varaible like: fish = {} for t=1, 10 do ent = Model:Load("models/fish"..t..".mdl") end then those files are not present in the media .ZIP file and you'll crash on a compiled run. I ran into this when I first started out with LE too. you can work around it by rem'ing some load commands. -- ent = Model:Load("models/fish1.mdl") -- ent = Model:Load("models/fish2.mdl") -- ent = Model:Load("models/fish3.mdl") and so forth. The zipper will pick up those files from the rem'ed code and you can still use variable naming to load mass media.
  21. Gotcha, point a Vec3() position with math instead of an entity.. cool.
  22. Handy function there, .. but don't forget LE has an optimized Point built in. https://www.leadwerks.com/learn?page=API-Reference_Object_Entity_Point
×
×
  • Create New...