Jump to content

Behind Enemy Line

burgelkat

512 views

Hi ,

Currently I'm planning the next level for Behind Enemy Lines. Since the player has to do part of the level with a sniper rifle, a little preliminary work had to be done. So, Here's my way to tackle this topic with the Addon "FPS Weapon Pack":

The tutorial from tipforeveryone was very helpful to me. You can find it here

https://www.leadwerks.com/community/blogs/entry/1775-realistic-sniper-rifle-scope-in-lua/

i downloaded a Scope frome here :http://www.cadnav.com/3d-models/model-36647.html

and put it as a child to the "vwep m4" and saved it as a prefab "vwep m4_sniper"

it should be look like this

5a48be56f2b74_Screenshot2017-12-3111_37_48.thumb.jpg.ca8c1070dd891545338755158df07db1.jpg

Now you have to ajust the scope

ScopeSetting.jpg.df542a5d197b33939faefc5f0074607b.jpg

But for the scope script to work, an empty script must be inserted in the following places. Thanks to Macklebee for this hint!

image.png.25f937c71b335505b9870df393d1d07b.png

Now you have to change 2 scripts

1. fpsgun.lua

2. fpsplayer.lua

 

1. fpsgun.lua

this script i saved under "FPSGun_Sniper.lua"

then this video helps a lot :https://www.youtube.com/watch?time_continue=628&v=3OqwQSP-2FU

thanks to BluHornet

place this in your fpsgun_sniper.lua

Script.offsetNor=Vec3(0,0,0)
Script.offsetADS=Vec3(0,0,0)--Vec3 "Offset ADS"

the next line put after the function Script:Start()

self.offsetNor = self.offset
self.hasZoom=true

self.hasZoom=true (or false) has been inserted because the ironsight will be active in every weapon, but at Grenade or something else i did not want this.

Since I have difficulty with the sway of the weapon and I have no solution for it currently, I commented under function Script: Draw () the following lines out:

	--self.swayspeed = Math:Curve(speed,self.swayspeed,20)
	--self.swayspeed = math.max(0.5,self.swayspeed)
	--self.amplitude = math.max(2,Math:Curve(speed,self.amplitude,20))

now its time to change the fpsplayer.lua

2. fpsplayer.lua

this line put in at the beginning

Script.ADSmode=false

next place the following lines under the function Script:UpdateWorld()

	if self.weapons[self.currentweaponindex]~=nil and self.weapons[self.currentweaponindex].hasZoom then
		if self.ADSmode == false then
			self.camera:SetFOV(70)
			self.weapons[self.currentweaponindex ].offset = self.weapons[self.currentweaponindex ].offsetNor
		end
		if self.ADSmode == true then
			self.camera:SetFOV(20)
			self.weapons[self.currentweaponindex ].offset = self.weapons[self.currentweaponindex ].offsetADS
			end
	end

and this also in this function (i put this after a lince called "--fire weapon"

	if window:MouseHit(2) then
		if self.weapons[self.currentweaponindex]~= nil then
			if self.ADSmode == false then
				self.ADSmode=true
			else
				self.ADSmode=false
			end
		if self.sound.pickupweapon~=nil then self.sound.pickupweapon:Play() end
	end
	end

if you do not want the ironsight by jump, reload, or carry an item, then paste those lines at the right places

self.ADSmode=false

Since the original crosshair disturbs me in the ironsight, I have inserted "and self.ADSmode==false then" in the function Script:PostRender(context) it should looks like this

	if self.health>0 then
		if self.canUse==true and self.carryingEntity == nil then
			local pickUpX = math.floor((context:GetWidth() - self.image.hand:GetWidth()))/2
			local pickUpY = math.floor((context:GetHeight() - self.image.hand:GetHeight()))/2
			context:SetBlendMode(Blend.Alpha)
			context:DrawImage(self.image.hand, pickUpX, pickUpY)	
		else
			if self.carryingEntity==nil then
				if self.weapons[self.currentweaponindex]~=nil then
					if self.image.crosshair and self.ADSmode==false then
						local crossHairX = math.floor((context:GetWidth() - self.image.crosshair:GetWidth()))/2
						local crossHairY = math.floor((context:GetHeight() - self.image.crosshair:GetHeight()))/2
						context:SetBlendMode(Blend.Alpha)
						context:DrawImage(self.image.crosshair, crossHairX, crossHairY)
					end
				end
			end
		end

 

What follows now are the individual settings for each weapon to get an Ironsight.

M4 Sniper:

image.png.024f746069709184ca6c52f95fdf2c1b.png

in the script:

image.png.737d01c3b32651e9103e1a724c019aa5.png

image.png.b95d99ba31e7c8856c70df17257c6e0e.png

the sniper M4 looks now like this

5a48cda3491d2_Screenshot2017-12-3112_42_26.thumb.jpg.23c6c8f4b859224522d7d9f5110a480c.jpg

5a48cd8f0574f_Screenshot2017-12-3112_42_36.thumb.png.37373fbea24037c2cad8fa9bb38a86fd.png

the m4 without scope

image.png.73598b3a8bb9321794e9a9318cc1de38.png

in the script:

image.png.ddb9e6a1a9db94227d15853d1ac09498.png

image.png.9508944d70f2de50158494df1121b68c.png

it should look like this

image.thumb.png.d6be17990eb861406c2b2a3b048772c3.pngimageproxy.php?img=&key=93667c899a2c8479

the shotgun

image.png.2e15a8ee74abae390602bfc9c9cd6a06.png

in the script

image.png.2147c2be3f1df5350efddf96d8d7390f.png

image.png.9d3e018bbeb54f4f7c07057946555b6d.png

the shotgun look like this

image.thumb.png.ae43110af1dabc4f17e8551297f36f55.png

 

the pistol

image.png.262e606c5446b6eda4d6a8c716c0a0e2.png

in the script

image.png.c6153f475f7fec5588b55a593e4bb267.png

image.png.932c5705a3d9ef13fb076aab0869e17d.png

the pistol look now like this

image.thumb.png.a4c80e1d76f7d8e468a5a400f9e29813.png

 

So, that was my solution. But if you have even better settings, feel free to write in this blog. I hope that this blog helped a bit. Especially to save time to find the settings for the Ironsight.

Have fun.

Greetings burgelkat

 

 

 

  • Like 5


0 Comments


Recommended Comments

There are no comments to display.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Blog Entries

    • By reepblue in reepblue's Blog 0
      As you may have known, I've been dabbling with input methods for a while now using SDL2. Since then, I've learned how to do similar functions using the Leadwerks API. The goal was to make a inout system that's easily re-bindable, and allows for controllers to "just work". My first research of a goof system comes from a talk at Steam DevDays 2016 as they discuss how to allow integration with the Steam Controller. 
       
      My thought was: "If I can create my own Action System, I can bind any controller with any API I want". The SDL experiments was a result of this, but they ended up being sloppy when you tried to merge the window polling from SDL into Leadwerks.
      The next goal was to remove SDL2 out of the picture. I've created functions to allow reading and simulations of button presses with the Leadwerks Window class.
      //----------------------------------------------------------------------------- // Purpose: //----------------------------------------------------------------------------- bool InputSystem::KeyHit(const int keycode) { auto window = GetActiveEngineWindow(); if (keycode < 7) return window->MouseHit(keycode); return window->KeyHit(keycode); } //----------------------------------------------------------------------------- // Purpose: //----------------------------------------------------------------------------- bool InputSystem::KeyDown(const int keycode) { auto window = GetActiveEngineWindow(); if (window != NULL) { if (keycode < 7) return window->MouseDown(keycode); return window->KeyDown(keycode); } return false; } //----------------------------------------------------------------------------- // Purpose: //----------------------------------------------------------------------------- void InputSystem::SimulateKeyHit(const char keycode) { auto window = GetActiveEngineWindow(); if (window != NULL) { if (keycode < 7) window->mousehitstate[keycode] = true; window->keyhitstate[keycode] = true; } } //----------------------------------------------------------------------------- // Purpose: //----------------------------------------------------------------------------- void InputSystem::SimulateKeyDown(const char keycode) { auto window = GetActiveEngineWindow(); if (window != NULL) { if (keycode < 7) window->mousedownstate[keycode] = true; window->keydownstate[keycode] = true; } } The simulate keys are very important for controllers. for this case, we would trick the window class thinking a key was pressed on the keyboard. The only direct input we would need from the controller is the value analog sticks which I haven't touch as of yet.
       Using JSON, we can load and save our bindings in multiple Action Sets!
      { "keyBindings": { "actionStates": { "Menu": { "selectActive": 1, "selectDown": 40, "selectLeft": 37, "selectRight": 39, "selectUp": 38 }, "Walking": { "crouch": 17, "firePrimary": 1, "fireSecondary": 2, "flashLight": 70, "interact": 69, "jump": 32, "moveBackward": 83, "moveForward": 87, "moveLeft": 65, "moveRight": 68, "reloadWeapon": 82 } } } } You may want a key to do something different when your game is in a certain state. For this example, when the Active Action Set is set to "Menu", Only KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, and KEY_LBUTTON will work. You can still hover over your buttons with the mouse, but when it comes time to implement the controller for example, you'd just call GetActionHit(L"selectActive") to select the highlighted/active button. If the state is set to walking, then all those keys for Menu gets ignored in-favor of the walking commands. All keys/buttons are flushed between switching states!
      Here's example code of this working. "Interact" gets ignored when "Menu" is set as the default action and vise-versa.
      while (window->KeyDown(KEY_END) == false and window->Closed() == false) { if (window->KeyHit(KEY_TILDE)) { if (InputSystem::GetActiveActionSet() == L"Menu") { SetActionSet(L"Walking"); } else { SetActionSet(L"Menu"); } } // Under "Menu" if (GetActionHit(L"selectUp")) { DMsg("selectUp!"); } // Under "Walking" if (GetActionHit(L"interact")) { DMsg("interact!"); } } Only things I didn't implement as of yet is actual controller support and saving changes to the json file which might need to be game specific. I also want to wait until the UI is done before I decide how to do this.
      As for controllers, we can use SteamInput, but what if your game isn't on Steam? You can try to implement XInput yourself if you want. I tried to add Controller support with SDL2, but people reported issues. And then, what about VR controllers? What matters right now is that we have room to add these features later on. All I need to do is use the GetActionHit/Down Commands and the rest doesn't matter.
    • By reepblue in reepblue's Blog 5
      There has been some discussion regarding on how to set collision shapes for your models. For 95% of models, you should be building shapes with the Model Viewer as described here. In some cases, the model artist might want a custom shape to be made. In this post, I'll be going over how I import models into Leadwerks, and building custom shapes.
      A few notes first. I use Blender; Blender 2.79b to be exact. I haven't get got the hang of 2.80 and until the new engine's art pipeline is fully online, I don't see a use for it. Leadwerks 4 uses Blinn-Phong rendering so the PBR stuff makes no sense for Leadwerks 4. So for this, I'll be posting screenshots from 2.79b. I should also mentioned that a feature I use in my process isn't present in the Linux build of the editor, which is the collapse tool. (Tools->Collapse). Doing the collapsing via a terminal will cause the models to crash the editor. This seems to be a known bug, as you don't see that feature in the Linux editor.
      Lets say you created a tube model such as this one and you want the player and objects to go into the tube:

      If you tried to make a shape doing the Concave settings, not only it'll be really slow to generate, but the results will not be good. We could make a shape based on the wire frame, but this is a high poly model. What we need to do is make a new mesh, import both models  to the editor, collapse them both, build the shapes for both, and delete the low poly model while making the high poly read the low poly's generated shape.
       
      First to get it out of the way, apply the scale and rotation of the model. This will make Y forward and the scale will be (1,1,1) when you import it into Leadwerks.

       
      Next we need a low poly model.

      This is the same proportions as our high poly. Apply the scale and rotation as the same as the high poly. I also set the max draw time to solid, but this is optional.

      Next, name your High poly and the low poly you're going to be using for the shape appropriately.

      Now lets, export each object as a FBX. For this my high poly is going out as tube.fbx, and my low poly shape is going out as tubeshape.fbx. Here are my export settings:

      If you saved the files in a Leadwerks project while the editor was opened, the editor would have auto convert the files to the .mdl file format. Open the high poly model (tube.fbx) and first collapse it and give it any shape. (Give it a box shape to save time.) you need to assign a shape to the high poly so the mdl file is linked to a phys file. Do the same with the low poly, but you're gonna set the shape as poly mesh.


      Close the model viewer, and then go into the directory where the models are placed. We are now going to delete the box shape of our high poly, and trick it into loading the low poly shape by renaming the shape file of the low poly to be what the previous shape of the high poly was. In other words, we are making tubeshape.phy into tube.phy.
      Before:

      After:

      Notice the time stamp and the size of tubeshape.phy from before being the same as tube.phy in the after screen cap. This should be your end result.

      Notice that the shape isn't sold but now a tube. Objects can go into the tube with no issues. Now, there is another way that uses limb names to generate physics automatically. However, there are a lot of issues I came across using this method such as the shape not being parented to the model when the model moved via physics or a joint. With this way, you have a custom shape, the model is optimized because it doesn't have any children nodes, and everything is clean and tidy!

       
    • By 💎Yue💎 in Dev Log 5
      The prototype is finished, and the mechanics of the game can be given way.  It has established a desert terrain in the form of dunes, this implies that there are no cannons or anything similar, because Leadwerks does not allow a terrain to cast shadows on that same terrain and this looks visually rare.
      So the terrain is like low-slope dunes. On the other hand, I think the texture of the terrain is already the definitive one, with the possibility of changes and suggestions on the part of those involved in this project.
      On the other hand we have taken the model of a habitat of the nasa, which certainly looks very nice. 
      The next steps, are to establish the starting point of the player, this must start near the capsule return to Mars somewhere on the map of 2024 x 2.
      And think about the first thing you should do, repair your suit? Seek a shelter? things like that.  


×
×
  • Create New...