thehankinator

Ranged based for loops clean up that iterator business even more! Also lambdas clean up the algorithms in STL(stuff like std::sort). My favorite is probably std::bind, been using it for years from Boost but it's nice to see it in the standard.

I've had inconsistent results with prefabs containing CSG. Also as described here, putting a script on CSG means putting a blank script on all it's children if it's suppose to move. It's become clear that I am trying to use CSG in unintended ways. What is the intended use for CSG?

I've had problems with phantom breakpoints also. Another funny thing was I had breakpoints in a file that no longer existed so I kept getting errors until I recreated that file to remove the breakpoints. That was a while ago though. I think the biggest issue with the debugger imo is that it doesn't always correctly display numbers(and other things?), Rick made a post about it a month or two ago. This issue has sent me down a rabbit hole more than once. Because of these issues and how slow it is to start the debug build, I rarely use the debugger and use prints to debug issues.

I'm glad you had time to work on the Launcher, I think it's one of my favorite parts of Leadwerks. Looking forward to more updates.

Sounds cool, is there a specific school looking at using Leadwerks in the classroom?

Glad to help! Imo this is bug report worthy. The debugger should never manipulate the data before presenting it to the user, could send the user on a wild goose chase.

I know the debugger says c=5 and r=12 but have you tried adding a print before the loop for r and c? The reason I ask is because I ran equivalent code and the results look fine. It would be good to know exactly what lua sees, not the degger. Ran on a standard lua interpreter but that shouldn't matter. c = 5 r = 12 map = {} for row=1, r do map[row] = {} for col=1, c do map[row][col] = "r"..row.."c"..col end end for row=1, r do str = "" for col=1, c do str = str..map[row][col].." " end print(str) end Results: C:\Users\Blah\Desktop>lua.exe test.lua r1c1 r1c2 r1c3 r1c4 r1c5 r2c1 r2c2 r2c3 r2c4 r2c5 r3c1 r3c2 r3c3 r3c4 r3c5 r4c1 r4c2 r4c3 r4c4 r4c5 r5c1 r5c2 r5c3 r5c4 r5c5 r6c1 r6c2 r6c3 r6c4 r6c5 r7c1 r7c2 r7c3 r7c4 r7c5 r8c1 r8c2 r8c3 r8c4 r8c5 r9c1 r9c2 r9c3 r9c4 r9c5 r10c1 r10c2 r10c3 r10c4 r10c5 r11c1 r11c2 r11c3 r11c4 r11c5 r12c1 r12c2 r12c3 r12c4 r12c5 Another thing I thought of, I'm not sure what happens if you have a global variable c in addition to the function argument c. All the more reason to print it out and see what it grabs for a value for c.

Have you looked at this? https://social.msdn.microsoft.com/Forums/vstudio/en-US/dee0ac69-4236-49aa-a2a2-0ac672147769/win32-c-how-do-i-change-the-window-icon-during-runtime?forum=vcgeneral

That's for Object:Release(), the documentation I am looking for defines the the behavior of Script:Release() if it exists in a script that is attached to an entity. Similar to Script:Start(), Script:UpdateWorld(), etc. The links in OP have Script:Detach() or Script:Delete() but nothing about Script:Release() which Reep says superseded Script:Detach() and/or Script:Delete() but the tutorial and reference do not match (one has Script:Detach() the other Script:Delete()) and neither have Script:Release() defined.

So neither the tutorial or the reference pages are correct? Do you know where Script:Release() is documented? I don't see it on either page.

Is this a typo? If not, Delete() appears not to be called when the script is removed from the object, under what conditions does an object have a script removed but not deleted? http://www.leadwerks.com/werkspace/page/api-reference/_/script-reference/ Script:Delete() This function is called when the entity it is attached to is deleted from memory. Use this to release any resources you allocated in the Script:Start() function. http://www.leadwerks.com/werkspace/page/tutorials/_/lua-scripting-r12 Script:Detach() This function will be called when the script is removed from the object, or if the object is deleted.

I've added models for keycards, clues, extension cord, medkits and ammo(no more solid colored boxes!). I think I want to focus on the story next(which will likely require additional levels) but I may also rework the clues before hand. Yeah, I am the best modeler ever I know you wish I made models for your game

No reason why you would need Josh to create the project file. You could start from the Linux codeblocks project file and add an additional build target. Don't forget to configure the compiler settings for MSVC first.

A lot of entries this time! Is it a record?

I'm glad you enjoyed it! Thank you for the feedback, I was worried the puzzles would be too difficult!

Thanks! I'm glad you liked it. I have a story and some other mechanics that I had originally planned on doing but ran out of time. Maybe in the future

Making things pretty has never been my strong point!

Thanks!

This is very much a work in progress, lots of undecorated rooms and story to be added but the basics of the game are there. You are locked in a mysterious underground bunker where something has gone terribly wrong. The only way out is through the horrors lurking in the dark corridors of South Central Biotechnics' forgotten facility. Left click - Move/Shoot R - Reload (can be held down) Shift - Run F - Flashlight http://steamcommunity.com/sharedfiles/filedetails/?id=749141006

Have you looked at the tutorials for Leadwerks? Covers learning Lua and Leadwerks API. There is a bunch here http://www.leadwerks.com/werkspace/page/tutorials/

Can you tell us what size spotlight (and other light types if applicable) is reasonable or what size is in danger of significantly impacting performance?

Beer helps but to to reset the timer just reinitialize StartTime with Time:GetCurrent()

God yes, I've been struggling to get my (simple)game to run well on my laptop's 7670m.

Time:GetCurrent() is in MS. I'd do it something like below. StartTime would need to be initialized to whatever time the timer starts with Time:GetCurrent() local MS = Time:GetCurrent() - StartTime local Minutes = math.floor(MS / 60000) MS = MS - Minutes * 60000 local Seconds = math.floor(MS / 1000) MS = MS - Seconds * 1000 local TimeStamp = Minutes..":"..Seconds..":"..MS

For MosterAI.lua to work you need to build the nav mesh. Here is a tutorial on how to build the navmesh, it's about 2/3 down the page. http://www.leadwerks.com/werkspace/page/tutorials/_/ai-pathfinding-and-events-r28