reepblue

My friend uses it for texturing. I recall him telling me that the newer version(s) allow AO baking and such so it's still handy.

Thank you so much!

It seems that the lighting performance update while is really great in game, has a major draw back in the editor. If you have lighting quality on medium or low and add a static prop, then delete or change it's shadow mode, you'll see the prop's shadow remains until you force a new lighting calculation by hiding/un-hiding the light, or changing the light setting in the editor's properties. Again, everything is working as expected, it's just odd to not have auto updating in the editor with static shadows. Maybe make it so that it uses the older update method if the engine is in the editor?

I agree. The Scene Tree is just a mess and I actually don't like using it when I have to parent 2 entities together when the list is really long. I might also suggest a Parent drop down in the General tab that'll auto adjust it's position in the scene tree.

I noticed that in newly created projects, C+11 isn't ticked for Code::Blocks.

Oh no, another problem with env probes.

if it's 0.05 seconds long, I don't think it'll will not kill you to leave it as a wav.

As long as the stock code after creating a new project is still set up to run the main script, I'm fine with the App Class going. Like Evar, I usually delete it anyway,

Yeah the editor hit's it's wall when/if the user decides they wants to use C++ for their entire game.

I only use it because I'm used to applying nodraw in Source which was also something you didn't need to do since 2006 or so.

it has been replaced with self.entity:PlayAnimation. http://www.leadwerks.com/werkspace/page/api-reference/_/entity/entityplayanimation-r918 you can find the Animation Manager Script here. https://github.com/reepblue/DarknessAwaits/blob/master/Darkness%20Awaits/Scripts/AnimationManager.lua

Here. Josh saw it, so I think it's fixed/will be fixed in 4.3. http://www.leadwerks.com/werkspace/topic/15487-issues-in-visual-studio-projects-and-the-fixes/

Ok, did some testing around. The issue is related to brushes. Materials that are Caulk, or in Editor Blend Mode or Selected brushes/faces will build in the probe reflection With models, this isn't the case and everything works as expected. So pretty much, it a brush issue.

Interested to see. I know a lot of the Steam Community is sick of Early Access Titles. Maybe GameJolt and Itch.io are where more early adopters are? Anyway, the Vectronic Demo has 1,682 current subscribers, and 1,819 overall on the workshop.

Hmm, seem to be having issues when you exit the launcher, Steam still says it's running, other than that great to see. Just tried VecDemo, never went below 100fps, averaging 130~ on my system and ultra wide screen res. Also don't forget the Editor Only Blend Mode being built in probe reflections. . :B

Sometimes in Vsync, my framerate caps to 30 randomly. It's not a Leadwerks thing, as I experienced it in older Source Engine games too. Been like that since I got my 750. I'll try this artificial syncing too... But overall, 4.3 is turning out to be one of my favorite updates so far. Ogg support and perf improvements is what I've been waiting for the longest.

This report makes me very happy. Glad to see improvements. might give this update a look. Also, the current Vectronic Demo on the game launcher has less point lights and smaller spotlight cones which may have contributed to the performance increase as well, but I saw very little improvement with 4.2.

I just played the Game Launcher through my Steam Link and Steam Controller and it was very cool! However, when I was done, I could not exit the app from my TV, so I had to go to my PC to force close it that way. Not sure if it's the same way on SteamOS or not. This was all through Big Picture Mode.

If you change it to 480, it will call the Spacewar app which is a test app that all accounts have access too.

I better stop using Leadwerks then! just kidding...

ogg support confirmed?

Fixing Filters 1) Filter's don't seem to be working for Visual Studio upon the release of 4.2. To fix, rename $PROJECT_NAME.filters to $PROJECT_NAME.vcxproj.filters. Fixing Debug working directory 2) Debugging from the IDE seems to not be working. To fix Go to Properties->Debugging and change the working directory from $(ProjectDir) to $(SolutionDir)..\..\ Very minor, but should be addressed. Thanks.

Use this script instead. http://www.leadwerks.com/werkspace/topic/15382-volumetrigger-script/

Ahh, recalling old forum posts, I thought the engine would just "magically" be able to read the contents.

You can just use 7Zip to zip up each asset folder with a password. Tedious, but it should only be done post release and each update.