[WMCoolmon]

I assume you mean this page in the wiki? Done, and I tried to update the rest of the examples to reflect the new scripting system capabilities as well.

[Nuke]

thanks
but wheres the render trargets example?
all i really got to go on is this old example which didnt work last i checked. i never really understood the whole thing in the first place and the fact that i was never able to generate any working code doesnt help much either. i need to see a current working example that i can mess with and understand how its working. not neccisarily a panel, but at least painting foul words on the side of an orion will do

[WMCoolmon]

Well, I haven't been able to get a working RTT example going; apparently there's a bug with the RTT code which taylor is looking into. (I don't know when the fix will be committed)

[Cobra]

What is RTT?

[Wanderer]

Render-To-Texture

[Nuke]

will taylors fix include rtt under open gl?

[WMCoolmon]

It sounds like the fix will only affect OpenGL.

[Admiral Nelson]

How practical would it be to use scripting with the HUD available now to produce a disturbed reticle gunsight?  This is a form of early gunsight in which the reticle itself moves to account for the bullet path under G at a given range.  In effect, unlike the targeting reticle in FS2, which is a director sight (it knows the target course, velocity and range) it is a targeting reticle set to a fixed range.  The reticle 'floats' across the screen as the craft maneuvers to display where the projectiles will actually be traveling.

[Nuke]

how good are you at math?

that means it can be done, ive done my own lead indicators (based off some of wanderer's script). be nice if you could make a lead that indicates hit probibility and takes the target's evade potential into consideration.

[WMCoolmon]

That actually would be pretty cool.

That thrill of almost-satisfaction you'd get as the reticule pulsed red when you catch a Dragon flat-footed...

[blackhole]

flat-footed

That term is reserved for D&D, not FS2

[Nuke]

ideally id use a reticle like the one i already completed, a simple circle with a radius and color indicating hit potential. evade potential can be figured out by determining the travel time for your shots to get to the target, how fast the ship can go/manuver, and in some cases max deflection angles (for weapons that use them). using that data you could determine  it would require doing complicated math every frame though.

[Admiral Nelson]

Heh, that stuff sounds cool, director sights do have a "SHOOT" indicator that would be interesting.

I am interested actually in a primitive F-86 style gyro sight.  Basically a reticle that precesses opposite to whatever turn you are making. 

The disturbed reticle sight takes the ballistic data, combines it with aircraft pitch and roll inputs, and then computes a picture of what the bullet path looks like.  Essentially, the disturbed reticle sight says to the pilot, "Here’s what the bullets are doing…now it is up to you to get the target to fly into this area."

Of course it wouldn't precess down as there is no gravity in space.  I presume I would need to get the vector describing the flight path of the player craft and then in effect reverse it to get the projectiles' vector.  That in turn would need to be converted into an on screen coordinate.  Does that make sense?

[Nuke]

try this

Code: [Select]

#Global Hooks
$GameInit:
[

--all this stuff is for multires support, for getting true width and height, and for generating factors to scale coords by

w = gr.getScreenWidth()
h = gr.getScreenHeight()
cx = w/2
cy = h/2

if w >= 1024 then
wf = w / 1024
hf = h / 768
awh = (wf + hf) / 2
hires = true
else
wf = w / 640
hf = h / 480
awh = ((wf + hf) / 2) * 0.625
hires = false
end

--now that were done with that ****, we can define some more important vars

xtarg = cx --this is where our crosshair will want to be
ytarg = cy --same thing but a bit more vertical
wepvel = 450 --set for thrasher for testing, wel do what wanderer did later
chr = 50
chg = 50
chb = 50
cha = 50

--now a crosshair, il make this much more detailed later, with target direction and orientation, target iff and maybe ammo gauge and locked/locking indicators

drawgunsight = function(x,y,r,g,b,a)
gr.setColor(r,g,b,a)
gr.drawCircle(25,x,y)
gr.setColor(r,g,b,255)
gr.drawGradientLine(x+18,y+18,x+5,y+5)
gr.drawGradientLine(x-18,y+18,x-5,y+5)
gr.drawGradientLine(x+18,y-18,x+5,y-5)
gr.drawGradientLine(x-18,y-18,x-5,y-5)
end

--and finally lets jack wanderers code, because i really dont feel like plotting vectors in 3d space

leadreticle = function(weaponvel)
local targetpos = target.Position --tweak theese
local targetvel = target.Physics.Velocity --looks like nothing else needs to be tweaked here
local lenghttargetvel = targetvel:getMagnitude()
local playerpos = player.Position
local plrtotrg = playerpos - targetpos
local lenghtplrtotrg = plrtotrg:getMagnitude()
local trgangle = plrtotrg:getDotProduct(targetvel)
local a = (( weaponvel * weaponvel ) - ( lenghttargetvel * lenghttargetvel ))
local b = ( 2 * trgangle )
local c = -( lenghtplrtotrg * lenghtplrtotrg )
local discrim = ((b * b) - 4 * a * c)
local leadx = 0
local leady = 0

if discrim >= 0 and a ~= 0 then
multipl1 = (( -b + math.sqrt(discrim)) / ( 2 * a))
multipl2 = (( -b - math.sqrt(discrim)) / ( 2 * a))

if multipl1 >=0 and multipl1 <= multipl2 and multipl2 >= 0 then
targetmult = multipl1
elseif multipl1 >=0 and multipl2 < 0 then
targetmult = multipl1
elseif multipl2 >=0 then
targetmult = multipl2
else
targetmult = nil
end

if targetmult ~= nil then
local leadvel = targetvel/(1/targetmult)
local leadpos = targetpos + leadvel

      if leadpos:getScreenCoords() ~= false then
leadx, leady = leadpos:getScreenCoords() --rather than just simply draw the coords, il scale and return them so my code can **** with them
leadx = leadx * wf --drawleadreticle(leadx,leady) pft, my way is better :D
leady = leady * hf --theese factors make things so much easyer
return leadx, leady --yep, thats what i need there
else
return -1, -1 --return -1-1 if this all fails, so it doesnt tweak my math
end
end
      end
end

]
$HUD:
[

player = mn.Ships["Alpha 1"]

if player:isValid() then
target = player.Target

banks = player.PrimaryBanks --work on this
wep1 = banks['1']
wepvel = wep1.WeaponClass.Speed
end

if target:isValid() and player:isValid() then
if target.Position:getScreenCoords() ~= false then
xship, yship = target.Position:getScreenCoords()
xship = xship * wf
yship = yship * hf
xtarg, ytarg = leadreticle(wepvel)
if xtarg >= 0 or ytarg >= 0 then
xtarg = cx + (xship - xtarg)
ytarg = cy + (yship - ytarg)
else
xtarg = cx
ytarg = cy
end
else
xtarg = cx
ytarg = cy
end
else
xtarg = cx
ytarg = cy
end

if target:isValid() == false then
if chr > 50 then
chr = chr - 1
elseif chr < 50 then
chr = chr + 1
end

if chg > 50 then
chg = chg - 1
elseif chg < 50 then
chg = chg + 1
end

if chb > 50 then
chb = chb - 1
elseif chb < 50 then
chb = chb + 1
end
elseif target.Team.Name == "Hostile" or target.Team.Name == "Traitor" then
if chr < 255 then
chr = chr + 1
end

if chg > 0 then
chg = chg - 1
end

if chb > 0 then
chb = chb - 1
end
elseif target.Team.Name == "Friendly" then
if chr > 0 then
chr = chr - 1
end

if chg < 255 then
chg = chg + 1
end

if chb > 0 then
chb = chb - 1
end
elseif target.Team.Name == "Unknown" then
if chr < 255 then
chr = chr + 1
end

if chg > 0 then
chg = chg - 1
end

if chb < 255 then
chb = chb + 1
end
elseif target.Team.Name == "Neutral" then
if chr > 0 then
chr = chr - 1
end

if chg > 0 then
chg = chg - 1
end

if chb < 255 then
chb = chb + 1
end
else
if chr > 128 then
chr = chr - 1
elseif chr < 128 then
chr = chr + 1
end

if chg > 128 then
chg = chg - 1
elseif chg < 128 then
chg = chg + 1
end

if chb > 128 then
chb = chb - 1
elseif chb < 128 then
chb = chb + 1
end
end

drawgunsight(xtarg, ytarg, chr, chg, chb, cha)

]
#End

this should work in recent head builds

[Unknown Target]

Could something a little more modern be made? As in, a gunsight pipper with a line trailing to a circle - you place the circle on the target and squeeze? Basically like the one in an F-15? (Kinda like a different looking F-86 sight ).

[Nuke]

well you could swap the procedurally rendered pipper i mad ewith a graphic pipper instead, then just get the screen coords of the ship and draw a line from those coords to the sight's. ive done this before its rather easy.

[Admiral Nelson]

Is the magnitude of a vector in FS2 a value expressed in meters (yes, I was an English major)?  For instance, the F-86 gunsight doesn't know anything about the location of the target.  It is calibrated to assume that the target is at a certain distance -- say 500m.  Thus instead of this code snippet:

Code: [Select]

local targetpos = target.Position --tweak theese
local targetvel = target.Physics.Velocity --looks like nothing else needs to be tweaked here
local lenghttargetvel = targetvel:getMagnitude()
local playerpos = player.Position
local plrtotrg = playerpos - targetpos
local lenghtplrtotrg = plrtotrg:getMagnitude()
local trgangle = plrtotrg:getDotProduct(targetvel)
[\code]


Could I not simply use

[code]

local targetvel = player.Physics.Velocity --use the player's own craft's velocity
local lenghtplrtotrg = 500 --fixed distance
local trgangle = plrtotrg:getDotProduct(targetvel)


and continue with the rest of the code?  I will need to flip the x/y coordinates of the gunsight, as this is a trailing and not leading indicator.[/code]

[Nuke]

before the radar gunsight was used they used a gyro gunsight, which compensated for g-forces, gravity and attitude (as this data was already available to the instruments). that would require entire code entirely.

the whole function for generating the lead was designed by wanderer (though i added some tweeks too it) and i barely understand how it works. what i did know was that if i knew where the leadpoint was (generated by function), i knew where the reticle was (w&h / 2), and i knew where the ship was, then i could draw a pipper on the screen by subtracting the lead's screen coords from the ship's screen coords, then add the result to the screen center. all i did really was change how the data was represented.

btw, what sim is that?

[Wanderer]

My lead function is basically just 101 trigonometry.. namely usage of the extended Pythagoran law.. the cosine rule. It constantly calculates interception point for the given primary weapon and the target in 3d space. Most of function is just a verification process that it uses the correct root (from 2nd degree function) and that the root may not be imaginary. Most of the stuff i added just in case Lua would be unable to automagically handle 'double' results and imaginary values and also to make sure that i get the result i wanted from the function.

But to get a low tech 'lead reticle' for fixed distance firing you need to use something totally different as Nuke said.