29 replies to this topic

[Wecx]

Does the Clan TC Effect Gauss Rifles? I Cant really tell in the Testing Grounds! , Thanks.

[mogs01gt]

I do not think it affects the GR.

[Jackal Noble]

Yes it does, testing grounds is notorious for not being super dependable q.c. for testing builds. As the Gauss is a ballistic projectile weapon, the tc's projectile perecentage enhance it, i.e. a Gauss with a tcII will travel at 2200 m/s , a Gauss with a tcVII will travel at 2600 m/s. Now if it is actually granting those predicted speeds or just making them somewhat faster, is a separate pgi coding issue entirely

[Gas Guzzler]

JackalBeast, on 11 April 2016 - 11:35 AM, said:

Yes it does, testing grounds is notorious for not being super dependable q.c. for testing builds. As the Gauss is a ballistic projectile weapon, the tc's projectile perecentage enhance it, i.e. a Gauss with a tcII will travel at 2200 m/s , a Gauss with a tcVII will travel at 2600 m/s. Now if it is actually granting those predicted speeds or just making them somewhat faster, is a separate pgi coding issue entirely

Targeting computers DO NOT affect Gauss rifles. If you read the description in the Mechlab, I remember it only including autocannons and PPCs when referring to projectile velocity, not Gauss.

Also, smurfy also only refers to ACs and PPCs and lasers. Gauss rifle is not an AC.

Edited by Gas Guzzler, 11 April 2016 - 11:39 AM.

[Mcgral18]

Gas Guzzler, on 11 April 2016 - 11:37 AM, said:

Targeting computers DO NOT affect Gauss rifles. If you read the description in the Mechlab, I remember it only including autocannons and PPCs when referring to projectile velocity, not Gauss.

Also, smurfy also only refers to ACs and PPCs and lasers. Gauss rifle is not an AC.

You would be incorrect

-<TargetingComputerStats moduleDestroyedHudWarning="eHUD_TARGETING_COMPUTER_DESTROYED">

-<WeaponStatsFilter compatibleWeapons="SmallLaser,MediumLaser,LargeLaser,ClanERSmallLaser,ClanERMediumLaser,ERLargeLaser,ClanERLargeLaser,SmallPulseLaser,ClanSmallPulseLaser,MediumPulseLaser,ClanMediumPulseLaser,LargePulseLaser,ClanLargePulseLaser" tag="BeamWeapons">
<WeaponStats critChanceIncrease="0.08,0.045,0.01" operation="+"/>
<WeaponStats operation="*" maxRange="1.1" longRange="1.1"/>
</WeaponStatsFilter>

-<WeaponStatsFilter compatibleWeapons="AutoCannon2,ClanAutoCannon2,AutoCannon5,ClanAutoCannon5,AutoCannon10,ClanAutoCannon10,AutoCannon20,ClanAutoCannon20,GaussRifle,ClanGaussRifle,ClanUltraAutoCannon2,UltraAutoCannon5,ClanUltraAutoCannon5,ClanUltraAutoCannon10,ClanUltraAutoCannon20,PPC,ERPPC,ClanERPPC" tag="ProjectileWeapons">
<WeaponStats critChanceIncrease="0.08,0.045,0.01" operation="+"/>
<WeaponStats operation="*" speed="1.35"/>
</WeaponStatsFilter>
</TargetingComputerStats>

[LT. HARDCASE]

TC7 Goose Rifle is so hilarious.

[Chuck Jager]

Mcgral18, on 11 April 2016 - 01:08 PM, said:

You would be incorrect

-<TargetingComputerStats moduleDestroyedHudWarning="eHUD_TARGETING_COMPUTER_DESTROYED">
 
-<WeaponStatsFilter compatibleWeapons="SmallLaser,MediumLaser,LargeLaser,ClanERSmallLaser,ClanERMediumLaser,ERLargeLaser,ClanERLargeLaser,SmallPulseLaser,ClanSmallPulseLaser,MediumPulseLaser,ClanMediumPulseLaser,LargePulseLaser,ClanLargePulseLaser" tag="BeamWeapons">
<WeaponStats critChanceIncrease="0.08,0.045,0.01" operation="+"/>
<WeaponStats operation="*" maxRange="1.1" longRange="1.1"/>
</WeaponStatsFilter>
 
-<WeaponStatsFilter compatibleWeapons="AutoCannon2,ClanAutoCannon2,AutoCannon5,ClanAutoCannon5,AutoCannon10,ClanAutoCannon10,AutoCannon20,ClanAutoCannon20,GaussRifle,ClanGaussRifle,ClanUltraAutoCannon2,UltraAutoCannon5,ClanUltraAutoCannon5,ClanUltraAutoCannon10,ClanUltraAutoCannon20,PPC,ERPPC,ClanERPPC" tag="ProjectileWeapons">
<WeaponStats critChanceIncrease="0.08,0.045,0.01" operation="+"/>
<WeaponStats operation="*" speed="1.35"/>
</WeaponStatsFilter>
</TargetingComputerStats>

Pretty sure many of these XL lists are for mech lab associations or client side games [test ground?]

Why would pgi put a simple list in a file we could find and edit that would change how weapons functioned during the game. Probably mirrors another similar list that is compiled at the time of the drop or there could be a check system.

I just know that not all visible code is used as written when and where someone expects it too. Of course the poster could be 100% correct too.

Edited by Chuck Jager, 11 April 2016 - 01:22 PM.

[Revis Volek]

Chuck Jager, on 11 April 2016 - 01:21 PM, said:

Pretty sure many of these XL lists are for mech lab associations or client side games [test ground?]

Why would pgi put a simple list in a file we could find and edit that would change how weapons functioned during the game. Probably mirrors another similar list that is compiled at the time of the drop or there could be a check system.

I just know that not all visible code is used as written when and where someone expects it too. Of course the poster could be 100% correct too.

Good luck altering those files, its the XML, it can be mined from most games.


Its not editable, and if you do PGI will find you and bad you. Its also server side not client side as far as most of that stuff goes. Only recently has things like ZOOM been moved to client side. I am not sure that was a good idea, im waiting for the hackusations from the change.

[Jman5]

I played around with the Gauss with and without a TC 7 firing at a target 1500 meters away. Even though it's supposed to be going 35% faster I couldn't tell the difference. Either there is some sort of 2000 m/s max speed cap, or it's already so fast that it's too hard to discern. Especially when you consider that 90% of your shots are going to be much much closer in, and you're more likely to be using the TC 1, this part of the TC doesn't seem to be worth it. That leaves the +8.5% crit bonus the 22.5% target info gather, and the 14% zoom boost as the only appreciable changes.

[Gas Guzzler]

Mcgral18, on 11 April 2016 - 01:08 PM, said:

You would be incorrect

-<TargetingComputerStats moduleDestroyedHudWarning="eHUD_TARGETING_COMPUTER_DESTROYED">
 
-<WeaponStatsFilter compatibleWeapons="SmallLaser,MediumLaser,LargeLaser,ClanERSmallLaser,ClanERMediumLaser,ERLargeLaser,ClanERLargeLaser,SmallPulseLaser,ClanSmallPulseLaser,MediumPulseLaser,ClanMediumPulseLaser,LargePulseLaser,ClanLargePulseLaser" tag="BeamWeapons">
<WeaponStats critChanceIncrease="0.08,0.045,0.01" operation="+"/>
<WeaponStats operation="*" maxRange="1.1" longRange="1.1"/>
</WeaponStatsFilter>
 
-<WeaponStatsFilter compatibleWeapons="AutoCannon2,ClanAutoCannon2,AutoCannon5,ClanAutoCannon5,AutoCannon10,ClanAutoCannon10,AutoCannon20,ClanAutoCannon20,GaussRifle,ClanGaussRifle,ClanUltraAutoCannon2,UltraAutoCannon5,ClanUltraAutoCannon5,ClanUltraAutoCannon10,ClanUltraAutoCannon20,PPC,ERPPC,ClanERPPC" tag="ProjectileWeapons">
<WeaponStats critChanceIncrease="0.08,0.045,0.01" operation="+"/>
<WeaponStats operation="*" speed="1.35"/>
</WeaponStatsFilter>
</TargetingComputerStats>

The why the **** doesn't the description say that?

Unbelievable, we shouldn't have to open up game files to see how this sort of thing works.

[Ghogiel]

Chuck Jager, on 11 April 2016 - 01:21 PM, said:

Pretty sure many of these XL lists are for mech lab associations or client side games [test ground?]

Why would pgi put a simple list in a file we could find and edit that would change how weapons functioned during the game. Probably mirrors another similar list that is compiled at the time of the drop or there could be a check system.

I just know that not all visible code is used as written when and where someone expects it too. Of course the poster could be 100% correct too.

The xmls client side are overridden by the ones on the server always. Modifying them does nothing in game. But you are correct in your way of thinking of them. ie don't put much stock into them as in theory they may not be the same as on the server and a lot of game mechanics that modify or override can be compiled and not in the xmls

but as for the topic. I was always under the assumption that TCs work on gauss.

Edited by Ghogiel, 11 April 2016 - 01:29 PM.

[Revis Volek]

Ghogiel, on 11 April 2016 - 01:28 PM, said:

The xmls client side are overridden by the ones on the server always. Modifying them does nothing in game. But you are correct in your way of thinking of them. ie don't put much stock into them as in theory they may not be the same as on the server and a lot of game mechanics that modify or override can be compiled and not in the xmls

but as for the topic. I was always under the assumption that TCs work on gauss.

I have yet to find a lie in the .XML, maybe Mcgral can shed more light.

As far as i know its 100% accurate.

[Mcgral18]

Revis Volek, on 11 April 2016 - 01:30 PM, said:

I have yet to find a lie in the .XML, maybe Mcgral can shed more light.

As far as i know its 100% accurate.

All I know is Steam doesn't let you launch if you change them (I wanted to test a 200M Flamer in the Training Grounds)


Years ago, that would have worked in a live match (not that I've ever tested that)

[Dimento Graven]

Mcgral18, on 11 April 2016 - 01:35 PM, said:

...

Years ago, that would have worked in a live match (not that I've ever tested that)

BAN THE HAXXOR!!!!

[Mcgral18]

Dimento Graven, on 11 April 2016 - 01:41 PM, said:

BAN THE HAXXOR!!!!

Stories of the Closed Beta testers.

Some funny stuff. They made a ticket, and abused until it was fixed.

[Dimento Graven]

Mcgral18, on 11 April 2016 - 01:59 PM, said:

Stories of the Closed Beta testers.

Some funny stuff. They made a ticket, and abused until it was fixed.

Oh...

GO BACK IN TIME AND BAN THE HAXXORS!!!

[Jackal Noble]

Thanks for being the sentinel McGral, appreciate it

[Ghogiel]

Mcgral18, on 11 April 2016 - 01:35 PM, said:

Years ago, that would have worked in a live match (not that I've ever tested that)

Pretty sure it wouldn't have. For a long while modifying the game client wasn't an issue with ToS. It was still heavy server authoritive even before HSR.

AFAIK you could basically only mess with rendering and sound. Almost everything else was on the server.

like if you mess with the maps, The collision is loaded on the servers sim, even if you remove the buildings on your end, it's like playing blind to the terrain and buildings> they were still there and you'd collide with but you couln't see anything.
You could make mechs glow in the dark by messing with the mtls
You could mess with textures,give a bullseye on mech cockpits, remove filmgrain etc
I am pretty sure xml edits did zip.

[Tristan Winter]

I love these threads when people are discussing theories from testing grounds, video footage, ancient scrolls and legends passed down from generation to generation, and McGral just reads the code and is like:

[Mcgral18]

Jman5, on 11 April 2016 - 01:28 PM, said:

I played around with the Gauss with and without a TC 7 firing at a target 1500 meters away. Even though it's supposed to be going 35% faster I couldn't tell the difference. Either there is some sort of 2000 m/s max speed cap, or it's already so fast that it's too hard to discern. Especially when you consider that 90% of your shots are going to be much much closer in, and you're more likely to be using the TC 1, this part of the TC doesn't seem to be worth it. That leaves the +8.5% crit bonus the 22.5% target info gather, and the 14% zoom boost as the only appreciable changes.

I went to Alpine (on something past 2500M, directly right of spawn) which I assume is 3-4Km away.
TC7 was just below 2 seconds, while no TC was noticeably longer than 2 seconds (2.5? 2.25?)

I guess I could Math it out, or get a longer distance (like edge of Alpine to the other), but when you get more distance, eyeballing it seems possible.