requests regarding aircraft LOS, attack
Moderator: Moderators
requests regarding aircraft LOS, attack
For the next release I was wondering if it would be possible to make it so that aircraft LOS has a max depth value. I have been experimenting with setting aircraft cruisealt values really high ie 1000 and seeing how this effects gameplay. aircombat in WD and FF is awesome, -huge smoking death spirals to the ground but air to ground assault does not work, mainly because in the aircraft attack run, the aircraft will not adjust its altitude to get closer to the target. This wouldn't be an issue if aircraft altitude settings could be controlled in game (in the same fashion as the 'repair at 50' button works except using 'low altitude' and 'high altitude' as options. This brings me back to LOS, aircraft at high altitude will attempt to attack ground targets if they can see them since LOS is currently implemented as a cylinder of infinite height around the aircraft. This also presents an unfair advantage in terms of recon abilities.
Having the ability to define a max LOS depth (so that LOS is still a cylinder but only goes down for say the radius of the horizontal LOS) presents intriging tactical possibilities. i.e. in WD, the U-2 and the M-55(spyplanes) could have very high LOS abilities and could do their surveilance from very high up. For the defender this means that having higher altitude air defence such as patriot missile launchers and enhanced radar to target these high aircraft is more important (esp against B-52s and like). Imagine having to run combat airpatrols up high and worry about securing airspace while waging a combined forces ground assault.
In FF this also presents the possibility of combined space and ground warfare with the option of using 'in orbit' (high alt) battleships as bombardment platforms in conjunction with low level recon.
What I would like is these modifications: max LOS depth, and ability to control altitude (two levels max, otherwise too complicated)
Having the ability to define a max LOS depth (so that LOS is still a cylinder but only goes down for say the radius of the horizontal LOS) presents intriging tactical possibilities. i.e. in WD, the U-2 and the M-55(spyplanes) could have very high LOS abilities and could do their surveilance from very high up. For the defender this means that having higher altitude air defence such as patriot missile launchers and enhanced radar to target these high aircraft is more important (esp against B-52s and like). Imagine having to run combat airpatrols up high and worry about securing airspace while waging a combined forces ground assault.
In FF this also presents the possibility of combined space and ground warfare with the option of using 'in orbit' (high alt) battleships as bombardment platforms in conjunction with low level recon.
What I would like is these modifications: max LOS depth, and ability to control altitude (two levels max, otherwise too complicated)
- GrOuNd_ZeRo
- Posts: 1370
- Joined: 30 Apr 2005, 01:10
with the smoke trails I was refering to the units that are killed and fall to the ground sorry.
I also noticed that in normal air combat, aircraft seem able to be able to pursue others across a wide variery of altitudes so perhaps attacks 'out of the blue' from high altitude to low altitude could be possible without changing combat scripts at all (provided they can 'see' something is down there)
perhaps the multi altitude ability could be a new FBI tag ie 'highAltInc=500' (high altitude increment) so that when highaltitude is selected, effective height is cruisealt+500 otherwise it is just the default cruisealt
Cheers
I also noticed that in normal air combat, aircraft seem able to be able to pursue others across a wide variery of altitudes so perhaps attacks 'out of the blue' from high altitude to low altitude could be possible without changing combat scripts at all (provided they can 'see' something is down there)
perhaps the multi altitude ability could be a new FBI tag ie 'highAltInc=500' (high altitude increment) so that when highaltitude is selected, effective height is cruisealt+500 otherwise it is just the default cruisealt
Cheers

would be nice ...
gives good change to get various airplanes groups defined by altitude
ultrahi (orbital)
hi (spy planes or hi alt bombers-fighters)
med (classic aiplanes)
low (helicopter, low alt support like A-10) ....
forgot mention ultra low (hovers :)
gives good change to get various airplanes groups defined by altitude
ultrahi (orbital)
hi (spy planes or hi alt bombers-fighters)
med (classic aiplanes)
low (helicopter, low alt support like A-10) ....
forgot mention ultra low (hovers :)
Last edited by Dwarden on 17 Oct 2005, 06:13, edited 2 times in total.
1) this sounds super cool. True 3d combat for the Final Frontier mod, and sweet dogfighting in WD.
2) has anyone tried playing with low CruiseAlts? I'm trying to make a hovertank that strafes, by making a gunship with a very very low cruisealt, but its resulted in a few crashes, or more often, just didn't do anything.
2) has anyone tried playing with low CruiseAlts? I'm trying to make a hovertank that strafes, by making a gunship with a very very low cruisealt, but its resulted in a few crashes, or more often, just didn't do anything.
-
- Posts: 111
- Joined: 23 Jan 2005, 00:09
Problem with cruisealt is that if you come to a steep slope: it'll just go up regardless of anything since the unit is 'flying'Nemo wrote:2) has anyone tried playing with low CruiseAlts? I'm trying to make a hovertank that strafes, by making a gunship with a very very low cruisealt, but its resulted in a few crashes, or more often, just didn't do anything.
3D position?
Imho, I've always thought the best approach would be to have an actual 3d mouse pointer for aircraft, similar to Homeworld. But that would be annoyingly complicated. Maybe the mousewheel could be used for altitude (although it's already used for zoom).
As for radar, I'd just change sight/radar/targetting cylingers to be a very tall ellipses instead of cylinders. Make that a rule for every unit, not just planes.
As for radar, I'd just change sight/radar/targetting cylingers to be a very tall ellipses instead of cylinders. Make that a rule for every unit, not just planes.
Re: 3D position?
I thought LOS already eats up too much cpu time as it is, using ellipses would just make it worse.Pxtl wrote:...As for radar, I'd just change sight/radar/targetting cylingers to be a very tall ellipses instead of cylinders. Make that a rule for every unit, not just planes.
Well, then make is spheres.
You need the one square-root anyway, and the additional 2 instructions can be latency masked. It wont be slower.
Although i noticed that flying aircraft are something that slows the game down in enormous amounts. disproportionally enourmous amounts.
i got full cpu load with a test of 1000 brawlers in flight (actually more, but the gamespeed slowed down...), and only 15-20% were LOS, the majority was "simtime" and "slowunitupdate"
You need the one square-root anyway, and the additional 2 instructions can be latency masked. It wont be slower.
Although i noticed that flying aircraft are something that slows the game down in enormous amounts. disproportionally enourmous amounts.
i got full cpu load with a test of 1000 brawlers in flight (actually more, but the gamespeed slowed down...), and only 15-20% were LOS, the majority was "simtime" and "slowunitupdate"
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
Re: 3D position?
I'm no expert, but afaik the reason LOS takes long is not because of the complexity of range calculations, but the complexity of dealing with obstructions (such as terrain). Altering range to be 3d based shouldn't be as bad as all that.FizWizz wrote:I thought LOS already eats up too much cpu time as it is, using ellipses would just make it worse.Pxtl wrote:...As for radar, I'd just change sight/radar/targetting cylingers to be a very tall ellipses instead of cylinders. Make that a rule for every unit, not just planes.
The math goes from range being defined as
Code: Select all
in range iff: range > √(x├é┬▓+y├é┬▓)
Code: Select all
in range iff: range > √(x├é┬▓+y├é┬▓+nz├é┬▓)