Jump to content

Roland

Members
  • Content Count

    2,932
  • Joined

  • Last visited

Everything posted by Roland

  1. Roland

    fog mode

    auto cam = Camera::Create(); cam->SetFOV(60.0f); cam->SetZoom(1); cam->SetRange(0.1f, 500.0f); cam->SetFogColor(0.7f, 0.7f, 0.7f, 1.0f); cam->SetFogAngle(5.0f, 20.0f); cam->SetFogMode(true); cam->SetFogRange(2.0f, 30.0f);
  2. Check your Debugger path
  3. Then there is something wrong with you VS installation or your paths. Check your Include Directories
  4. Its your problem the same one or something else ?
  5. Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. Se my post here https://www.leadwerks.com/community/topic/16838-upgrading-44-c-projects-to-45/?tab=comments#comment-110509
  6. entity is the one you collided with position is the position of the entity when collision happened normal is the direction of the collision speed is the speed of the collission entity
  7. The Actor class is included as any other Leadwerks class. C:\Program Files (x86)\Steam\steamapps\common\Leadwerks\Include\Classes\Actor.h There is already a C++ setup for you when you create a project. Just open \Projects\Windows\"projectname".sln in Visual Studio and there you go
  8. Maybe this could help A C++/LUA bridge Class
  9. Roland

    A C++/LUA bridge Class

    I have made a small class for helping with reading and writing parameters between C++ and LUA and also calling LUA functions from C++. I'm sharing this little thing here. Using the class is quite simple as shown below LUA - part C++ - part I have included is a test project which looks like this in the editor And like this when executed Here is the LuaBridge class source LuaBrigde.h LuaBrigde.cpp And the complete test project LuaBridge.zip Note: Its says 'Click for next test', should be 'Hit Spacebar for next test'
  10. Just a little note. if self.health >= self.maxHealth then self.health = self.maxHealth end if self.health <= 0 then self.health = 0 end could be replaced with self.health = Math:Clamp(self.health, 0, self.MaxHealth)
  11. Updating to VS 2017 goes fine according to your instructions. Josh, now when you are at it, could you make the changes suggested below to get rid of warnings. A good project should compile without warning! Release cl : Command line warning D9030: '/Gm' is incompatible with multiprocessing; ignoring /MP switch Remove <MinimalRebuild>true</MinimalRebuild> from <CLCompile> section ------------------------------------- LINK : /LTCG specified but no code generation required; remove /LTCG from the link command line to improve linker performance Add <LinkTimeCodeGeneration>Default</LinkTimeCodeGeneration> to <LINK> section ------------------------------------- Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. ------------------------------------- Debug 1>libcryptoMT.lib(aes_cbc.obj) : warning LNK4099: PDB 'ossl_static.pdb' was not found with 'libcryptoMT.lib(aes_cbc.obj)' .... 1>libcryptoMT.lib(aes_core.obj) : warning LNK4099: PDB 'ossl_static.pdb' was not found with 'libcryptoMT.lib(aes_core.obj)'.... ... ... etc ... etc ... Add /ignore:4099 to <LINK> section, line <AdditionalOptions> ------------------------------------- Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. ------------------------------------- Thanks
  12. Solved: In Blender I scaled it up 100 times and the Applied Scale. Exported again and scaled down inside the LE-Editor Now it works
  13. Yes. I understand the problem. Will make some workaround. No problem now when I understand the reason. Thanks Josh
  14. Thanks for checking macklebee. Then it must be something local here. I created a blank project and added just that model and material. Placing the 'key' model in the scene works. As soon as I click on in the editor crashes. Oh well... I will reinstall Leadwerks then.
  15. This model causes an editor crash Version 4.4 Pro release key.zip
  16. Aha Great. My wallet became really scared and jumped under my table. Now I can tell it that everything is OK
  17. Aaah. I see. Thank's (y)
  18. Why not just use wstring, wchar_t, wfstream etc .. and that's it. A search and replace and maybe some modification here and there and its done
  19. Cool.. didn't 'not' know that
  20. while (not window->Closed() 'not'
×
×
  • Create New...