flachdrache

@mumbles - i dont questioning skills ... how could i. By bumping the fine detail of linux however you have to live with remarks, every now and again me thinks.

erm ... dont use example code i am posting while figuring stuff out myself - in that matter do we talk about throwing a physics controller into the scene while still loading the map (the latest bit i posted) or using appspeed to equalise framerates. 1. load the gamedata / map, force pause screen and let the player enter/spawn into a stable environment. or. 2. use VsyncOn and live with the 60 fps or cap the frames yourself (timebased rendering vs. framebased). Dont take every bit as granted - we all work from different preconditions ... imho.

The releases so far do kind of puzzle me ... i could run all builds with your first release never going out of "fade_screen" however. I suggest to go two steps back and dont complicate things for starters. Build samples for features, get into app design and assemble it into smaller builds till you tackle your game code as such. if(Fullscreen) Graphics(Width,Height,32); else Graphics(Width,Height); Could be just "Graphics(Width,Height,fullscreen);" with a const int fullscreen = 32; or not. You have two "noise.dll" in your shader.pak - causing errors or white halos at least. For the AppSpeed() issues i suggest to simply spawn 200+ dynamic objects to let them tear down your fps - the old sample map for the gameLib had a pyramid of of bodys for that matter. In my case its the other way around and i simply can use a 640x480 resolution to get 120+ fps while i usually have my inGame scenes at ~60 fps. Now the evil part - as a developer, i usually do not download .exe files because its a sample/test build i do, however. 1. put a "build.txt" or something in the zip with a date and some keyboard settings at least ! 2. your "config your screenRes from console build" (see what i mean with build.txt) somewhat archives its settings ! 3. the build before (which all other couldnt run) was stable at 29 - 32 fps - the "consoleRes" version jumps back to initial spawn position now and then which i cant track down to issue ... the later two are most evil because its bad behaviour imho ... a crash could be tracked down, some strange behavior just looks like bad hacking. Even worse would it be to save random config files into the path of random user profiles (who ever is in charge by the time of execution) or to install additional software secretly in the background, however ... avoid that. Sys spec`s are in my sig, hth. [edit] : ... and dont listen to Mumbles, she`s experimenting a lot with all kinds of strange systems.

FYI : Because its not quickload but scene change i dont know if clearing the world will do ... or what happens with the data if its memory isnt free`d. that is from some lua engine.exe fps-sample if KeyHit(KEY_F1)==1 then FreeFramework(fw) fw=CreateFramework() SetGlobalObject("fw",fw) g_playerstart = nil scene=LoadScene("abstract::SceneParaTropique_GTownCamp.sbx") g_playerstart = scene:FindChild("playerstart") playercreation() dofile("sample_Player_Fps.lua") end if KeyHit(KEY_F2)==1 then FreeFramework(fw) fw=CreateFramework() SetGlobalObject("fw",fw) g_playerstart = nil scene=LoadScene("abstract::SceneParaTropique_GTownCamp.sbx") g_playerstart = scene:FindChild("playerstart") playercreation() dofile("sample_Player_Fps.lua") end ... which works because of the differance of who`s client<>host.

OK - "ResetFramework()" simply seams to do the trick in my case ... some hours wasted to code functionality which already is implemented.

Hi, i want to convert my sceneLoader C source to c++ and hit a wall with retrieving the lua state for using its transparency script settings ... this is/should all be frameWork. The entities in question are not handled within ProcessScene(), are the usual suspects firepit, waterplane and the atmosphere but loading fine first time around. from the engine.log Loading script "c:/devlab01/le23sample/vs2008_proto_arena_01/media/engine/models/props/firepit/firepit.lua"... Lua error: c:/devlab01/le23sample/vs2008_proto_arena_01/media/engine/models/props/firepit/firepit.lua:25: attempt to index field 'transparency' (a nil value) I init lua like this : // -- // Set Lua framework object SetGlobalObject( "fw", fw ); // Set Lua framework variable BP lua = GetLuaState(); lua_pushobject( lua, fw ); lua_setglobal( lua, "fw" ); lua_pop( lua, 1 ); // ... i brute force reLoading in the main loop like this : // -- // Prepare App for new sceneLoad if( KeyHit(KEY_F5) ) { FreeFramework(fw); fw = CreateFramework(); // Set Lua framework object SetGlobalObject( "fw", fw ); // GfxSetup // -- SetBloom( true ); SetHDR( true ); SetGodRays( false); SetSSAO( false ); SetAntialias( true ); SetReflectionElements(ENTITY_MESH | ENTITY_MODEL | ENTITY_TERRAIN); playerIndex01.~cController(); // -- // recreate layer_world for new framework TLayer _layer_main; TLayer _layer_background; TLayer _layer_transparency; _layer_main = GetFrameworkLayer(0); _layer_background = GetFrameworkLayer(-1); _layer_transparency = GetFrameworkLayer(1); // Set its global vars for lua ... SetGlobalObject ("main.world", _layer_main ); SetGlobalObject ("transparency.world", _layer_transparency ); SetGlobalObject ("background.world", _layer_background ); playerIndex01.SetCamera( GetLayerCamera(_layer_main) ); playerIndex01.CreatePlayer(); // -- scene.~cScene(); scene.Load( "abstract::SceneParaTropique_GTownCamp.sbx" ); // add camera from scene PositionEntity( playerIndex01.GetCamera(), scene.GetCameraPos() ); RotateEntity( playerIndex01.GetCamera(), scene.GetCameraRot() ); // add controller from scene camera PositionEntity( playerIndex01.GetPlayer(), scene.GetCameraPos() ); } As you can see i even tried to pass framework layers with "SetGlobalObject" - however, i just want to assign/get the previous lua state back to use fw.transparency etc ... hint&help appreciated

If generating a navgraph one usually removes non-valid edges between nodes in a post step e.g. if a node is inside a entity aabb remove the node or if node A cant see node B ( blocked by a wall ) dont link these nodes ( north-west-south-east ). MG had something implemented for dynamic obstacles - i dont know how he solved that, however.

I tidy up some of my stuff and realise that 2.5 is somewhat falling behind earlier releases in terms of included content or does contain slight outdated material ... since josh got his head running leadwerks3D - i like to suggest to make it a little easier for him maintaining future (final ?!) builds of leadwerks 2.x and have the community find those loose ends. e.g. -the light fixture "Hanginglight" seams to be no longer a physical object -the switch shader "switch.frag" is missing the normalmap slot ... thats how it appears to me at least - there is possible more. Ill start and add the missing shader line to the bug tracker. thx for reading [edit] - forget the "switch.frag" - seams to be fixed already.

Leadwerks has a "custombuffer" - i used to render le`s framework to a custom openGL context but the upload got lost during the forum database mismatch some time ago. PS: "fallthrough" was suggested by using librocket`s "spacegame" demo.

Dont post try out code if you got the source. I pointed out that the dll is picky about its file paths (material, dll, video path). It could be anything from your description ... even more so with the "try out" code. put the video in the root e.g. same level as the scripts folder and work from a sample which only is there to get that thing done - no other stuff in its way.

The ninja smiley already is way cooler as the wink one. However, some posts or look-at-me behavior of very special people often do demand something more ... since i cant autoplay an applause sound file, i like to request these smiley`s. thx for you coexistence

iirc the lib was added by request and niosop just provided the tools. You fix it by integrating your video surface with given sample. Take care about the "video.mat", the dll path and the cleanup when the surface isnt needed anymore. CreateMaterial aint in for an abstract path in that case afaik. Ps : You seam to be something else then just lazy if you choose an image above the good old code tags. If i would need to point out what you might do wrong - i would need to rewrite your code .... people these days.

So i can drag a highpoly car model into the scene and build a simple version with CSG from it to be used as physics collider or AI obstacle ? - i currently have to convert my Le SDK models to a 3D world studio format or use a bbox to do that.

right - no sign of an eula is strange ... on the other hand, i did put up a lot of art assets as a starter w/o any license myself and since it looks like a students work i wouldnt mind. Defending the law is easy - using the internet - would be hard with real world brands ( VW, BMW, Porsche etc. ) or obviously "extracted" game content though. Game content usualy is obvious because of its well thought-out uv maps etc. I write a mail though - once "we can have it" ... can we ?

Hey there - just found an offer which almost looks to good to be true. A whole lot of "lowpoly" cars ... max users ! - please take a look and consider converting the " lowpoly car-sets 1-6" from the given site. http://tinyurl.com/6t8opcq PS : you might ask why obj and not gmf ... the texture sheets might need to be merged down for inGame usage. tia

depends ... with my sheer knowledge of shader programming i would say that one "reflect" beats two instances of "normalize" in terms of speed + processing vertexshaders is basically allways faster as fragmentshader processing but since i dont know what the compiled shader expect to be better, i play it save and say - add the old "cubecoord" instance to your .vert/.frag ... just the "varying vec3 cubecoord;" in the mesh.frag though. PS: iam not aware of random changes to some 2.5 shader ( insert funny EvilSmiley here).

Very nice work ... perfectness screams "move your head" though - but in a cutscene one blending this into the skeleton setup i assume.

tbh - thats not my work and i never had the files of the "river-nodes" from the showcase video ... which means, no projected caustics so far.

FYI : Mirrors dont depicture reality ... its not there job - they instead show the shadow of a copy of reality. This might be no longer true if you rewire both of your brain halfes ... and as much as i know the manykinds - there properly exists a drug for that too ... good luck !

You close your topic with an "I`ll be back" ... isnt that just a little "over the top".

Hrm, thats happen if i try it with the slang ... "game of death" is a bruce lee movie. ... same kind of leveling-up - if i understand correct.

Historically you might be interested in the "way of the exploding fist 2" game, which diversificated (kind-of) into mortal-kombat : shaolin monks and Jade Empire ... or most likely not - because you are doing your own thing ... which looks/sounds good. PS: if you dont like to ancounter you tube for an walkthrough video - its basically like "game of death".

Great that we all struggle with the same ideas - i got an generator for this, which grows the ivy on the objModel[part] ... i then put it in zBrush, reTopologise the roots of evil and project that on the new(lowpoly)mesh which then should ouput the normalmaps too ... there was an topic @doom3world some years ago in which this was discussed too. Iam bound to something else, atm, again but the fun part might be how to light that this with deferred rendering (backside & halftransparency).

Its some windows interns ( winuser.h iirc ).. write this after your "pragma once" #pragma once // Windows headers, LEAN_AND_MEAN after engine.h (pointless?!) #ifdef WIN32 #define WIN32_LEAN_AND_MEAN #include <windows.h> #include <winuser.h> #endif

You most likely need the prePlaning done first - the whole technical side grows from the game bounds you have to define first. Found this one years ago - its somewhat indie standard imho e.g. most people road at least parts of it. http://www.ics.uci.edu/~frost/GameDesign/ClawDesignDoc.pdf The more you know about how your game will "work", the easier youll find to "write down" the technical solutions to the design proplems. Healthbars and digi fonts displaying your ammo etc. became somewhat "oldschool" - its more common to "remove" the standard h.u.d. and to use indicators instead or to show the h.u.d. only in a fight situation (only if its actually needed). funFact : i use a heart and a brain decal "onscreen" texture which goes from red to black / blue to black ... if it gets grey the player knows he/she needs to do some healing.