


Targeting Computers And Command Console - Feedback
#161
Posted 08 June 2014 - 09:44 AM

#162
Posted 08 June 2014 - 09:46 AM
#163
Posted 08 June 2014 - 09:47 AM
Targeting Computer Mk I
Weight: 1 ton.
Slots: 1 slot.
Zoom distance: [+2.25]%
Sensor range: [+2.25]%
Time to gather target info: [-22.5]%
Projectile weapon projectile speed: [+4.5]%
Beam weapon long ranges: [+4.5]%
Beam weapon max ranges: [+4.5]%
Increased crit chance for projectile and beam weapons: [+5]% <<<<<
Start with 5% for the Crit chance instead of 14.5% and ramp it up from there.
With more than 5%, the effect is just too good to ignore (for 1 ton on Mark1) !
Edited by Reno Blade, 08 June 2014 - 09:48 AM.
#164
Posted 08 June 2014 - 09:51 AM
darkkterror, on 08 June 2014 - 09:44 AM, said:

42.
Silly clanners
#165
Posted 08 June 2014 - 09:52 AM
#166
Posted 08 June 2014 - 09:52 AM
#167
Posted 08 June 2014 - 09:53 AM
The Command console on the other hand is very disappointing. It is basically an overweight BAP without ECCM. There have been numerous suggestions in this thread that would have been more useful and more in keeping with the lore of the component.
1 share targeting information on all enemies in LOS of the mech with the CC. (might cause problems the command mechs own targeting)
2 Give the mech the CC is mounted in more module slots. (This is my personal favorite. You might get some abuse of this with people mounting extra coolant flushes, but most would use as intended to take more sensors and strikes.)
3 Give target info gathering bonus to whole team. (This would also fit with the idea of a commander giving information to company)
I sure there are other great ideas these are just three that jumped out at me. Hopefully the current implementation of the command console is just a placeholder and PGI comes back and gives it another look later.
#168
Posted 08 June 2014 - 10:00 AM
Koniving, on 07 June 2014 - 09:01 PM, said:
Impossible convergence. Really? This is taking pinpoint beyond too far.
Possible pinpoint solution. (Yes I still have to get around to the annotations; but take a watch of first person versus third person).
There is a demonstration during the Banshee, which shows that through the use of 'timing', even with the crosshair bounce caused by the mech running, it is perfectly possible to use player skill to produce consistent headshots. This 'solution' is 100% skill friendly, 100% user controlled [if aiming is difficult to time, you can slow down to make your shot. If you want a perfect shot with no chance to screw it up you can be stationary. Everything about your aim is affected by what you do and how you do it.
To further flavor it, the concept is unique to mechs, giving them each a different feel as unique as the animations they are given (and clearly affected by loadout choices such as engine as the engine and set throttle both cause changes animation play speeds).
Best of all, the solution is already in the game with minimal work required to implement it. Just take how the crosshair draws the reticule from the third person cockpit and follows the third person animations and have the first person version do exactly that.
This completely. Targeting computers should directly influence convergence speed to give clan 'mechs a serious edge over their Inner Sphere counterparts.
In fact, the current in-game convergence speed should be what the targeting computer provides...
#169
Posted 08 June 2014 - 10:04 AM
Dev's, please think outside of the numbers!
#170
Posted 08 June 2014 - 10:18 AM
#171
Posted 08 June 2014 - 10:35 AM
#172
Posted 08 June 2014 - 10:35 AM
I don't know where to go with the CC: WSO-in'a-Box would overload many CPUs even when derping badly …
#173
Posted 08 June 2014 - 10:40 AM
You also don't have to waste module slots on target info gathering etc.
Edited by MisterPlanetarian, 08 June 2014 - 10:42 AM.
#174
Posted 08 June 2014 - 10:43 AM
Your proposed implementation is equivalent to mounting an amulet of dexterity onto the mech and give it a boost to it's abilities.
We don't want buffs to existing systems. We want these components to *do something*.
A targeting computer is a computer. It should add more information to our HUD. This should improve an individual's performance. Quite powerful.
The command console is a command console! It should be used to take command of the company and improve communication within the group. This should improve the group's performance. Also quite powerful.
They can be completely different, and you can balance them. It would give different strengths to each side of the battle.
Please do away with the magical +2 to strength and dexterity, and move onto implementing some real technology.
Also we would like a little more variety in this game. Different equipment should do different things.
#175
Posted 08 June 2014 - 10:44 AM
Ballistic weapon speed increase. A computer cant make a bullet go faster out of the gun. It can increase the rate of fire slightly.
The critical hit chance is way to high already at 25% for computer based play. A targeting computer cant help you critical a mech its all random.
Otherwise it looks fine.
#176
Posted 08 June 2014 - 10:45 AM
However there is something missing in the CC, if it is just a weak version of the TC it is a bit bland.
I would like to see the same bonuses apply to allied mechs in a range around a CC carrying mech.
Something like ECM but grants bonuses instead.
I believe this will increase the focus of the IS as a collaborative tactics while the clans fight one on one.
#177
Posted 08 June 2014 - 10:50 AM
darkkterror, on 08 June 2014 - 09:44 AM, said:
It is capable of firing 42 weapons at ranges of 42 metres, doing 42 points of damage each.
#178
Posted 08 June 2014 - 10:56 AM
Slarticus, on 08 June 2014 - 10:45 AM, said:
However there is something missing in the CC, if it is just a weak version of the TC it is a bit bland.
I would like to see the same bonuses apply to allied mechs in a range around a CC carrying mech.
Something like ECM but grants bonuses instead.
I believe this will increase the focus of the IS as a collaborative tactics while the clans fight one on one.
This would be handled by the C3 Slave unit.....
Did anybody bring up that they need to introduce the C3 Slave unit for the Command Console? It should allow faster sharing of target data between all mechs equipped with C3 Slave units. This would allow some of the small mechs to benefit from the Command Console if one is on the battlefield.
Anyways wasn't sure if they had thought about adding the C3 Slave unit.
Edited by SolCrusher, 08 June 2014 - 10:58 AM.
#179
Posted 08 June 2014 - 11:00 AM
SolCrusher, on 08 June 2014 - 10:56 AM, said:
This would be handled by the C3 Slave unit.....
Did anybody bring up that they need to introduce the C3 Slave unit for the Command Console? It should allow faster sharing of target data between all mechs equipped with C3 Slave units. This would allow some of the small mechs to benefit from the Command Console if one is on the battlefield.
Anyways wasn't sure if they had thought about adding the C3 Slave unit.
No, in the past two years, we've never brought up C3. Not even once.
Oh, and you things confused. C3 master is what you're thinking of. Command console is a completely different item.
#180
Posted 08 June 2014 - 11:08 AM
Edited by Gyrok, 08 June 2014 - 11:08 AM.
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users