1768 replies to this topic

[smurfynet]

EyEpOkEr, on 11 February 2013 - 04:53 PM, said:

I could make that happen.... Smurfy would need to provide the web services....

working on it, adding some gui parts/docu, but REST interface to mechs and Oauth2 authentication works fine in local tests on dev system

phil

[smurfynet]

it seams, that currently the server on which the site is running on has some sort of problem. i'm currently in the process in figuring out whats wrong.

[Syllogy]

The process of adding armor feels like a pain to me.

Any chance you can either add a +/- 5/10 button, or change the armor value to a text field that we can just enter a value into?

[Snib]

Syllogy, on 12 February 2013 - 07:44 AM, said:

The process of adding armor feels like a pain to me.

Any chance you can either add a +/- 5/10 button, or change the armor value to a text field that we can just enter a value into?

You mean like this:



So many people seem to miss it because there are also the +/- buttons. Smurfy should probably add a notice or something.

[EyEpOkEr]

smurfynet, on 11 February 2013 - 11:11 PM, said:

working on it, adding some gui parts/docu, but REST interface to mechs and Oauth2 authentication works fine in local tests on dev system

phil

I have access to various devices, ipads 1 thru 3, mini, iPhones, various android tablets and phones if you need a tester when the time comes. Just fyi. Otherwise thanks for your hard work, as you can tell, the community appreciates it

[Jacmac]

Smurfy: Can you add in a function to export the build data to a CSV file?

[mekabuser]

OP. your work rocks ~S~ What a pleasure to do all the tinkering at work

[smurfynet]

Jacmac, on 12 February 2013 - 12:39 PM, said:

Smurfy: Can you add in a function to export the build data to a CSV file?

i'm thinking about it, can you send me an example how this should look like?

on another note, i temporarly added https support (https://mwo.smurfy-net.de) i tested it with an android device, my nokia n9 and desktop browsers. all browsers worked without ssl cert warning except my n9, but thats ok i guess nobody has one of those

but i like feedback from you guys if https works on your devices or not.

thanks
phil

[Jacmac]

smurfynet, on 13 February 2013 - 11:51 AM, said:

i'm thinking about it, can you send me an example how this should look like?

Example build:

http://mwo.smurfy-ne...f3db33e297af857

Export out a csv file like this:

Component,Head,Center Torso,Right Torso,Left Torso,Right Arm,Left Arm,Right Leg,Left Leg,Value
Front Armor,16,93,56,56,68,68,50,50,
Rear Armor,,31,28,28,,,,,
Slot0,Life Support,GYRO,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,SHOULDER,SHOULDER,HIP,HIP,
Slot1,Life Support,GYRO,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,UPPER ARM ACTUATOR,UPPER ARM ACTUATOR,UPPER LEG ACTUATOR,UPPER LEG ACTUATOR,
Slot2,Sensors,GYRO,AC/20,DYNAMIC STRUCTURE,LOWER ARM ACTUATOR,LOWER ARM ACTUATOR,LOWER LEG ACTUATOR,LOWER LEG ACTUATOR,
Slot3,Sensors,GYRO,AC/20,SRM 6 + ARTEMIS,HAND ACTUATOR,HAND ACTUATOR,FOOT ACTUATOR,FOOT ACTUATOR,
Slot4,SRM AMMO + ARTEMIS IV,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,AC/20 AMMO,AC/20 AMMO,
Slot5,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,AC/20 AMMO,AC/20 AMMO,
Slot6,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,,,
Slot7,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,SRM AMMO + ARTEMIS IV,,,
Slot8,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,SRM AMMO + ARTEMIS IV,,,
Slot9,,Heatsinks: 3 / 3,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,ER LARGE LASER,,,
Slot10,,GUARDIAN ECM,AC/20,SRM 6 + ARTEMIS,ER LARGE LASER,ER LARGE LASER,,,
Slot11,,GUARDIAN ECM,AC/20,SRM 6 + ARTEMIS,ER LARGE LASER,,,,
Tonnage,,,,,,,,,100.0
Armor,,,,,,,,,544
Firepower,,,,,,,,,83.0
Max Sustained DPS,,,,,,,,,5.53
Cooling Efficiency,,,,,,,,,27%
Free Slots,,,,,,,,,1
Speed,,,,,,,,,52.7
Speed Tweaked,,,,,,,,,57.9
Heatsinks,,,,,,,,,13
Armor Type,,,,,,,,,Standard
Structure,,,,,,,,,Endo-Steel
Heatsink Type,,,,,,,,,Double
Artemis,,,,,,,,,Artemis IV

If you save this as a CSV file and load it up in Excel or another spreadsheet, it will make sense.

You could add additional information, I only put what was the minimum for someone to import into a spreadsheet and get a basic understanding of the build. The big benefit is that a group can build up a database of builds and a Drop Commander can use the information to calculate drop configurations much more quickly than by hand.

We have guys spending a ridiculous amount of time manipulating this information by hand. I'm trying to get everyone in our group to use your site, but there are two problems. One objection to using it has been "what if it disappears one day?". Well if the data is exportable, they can no longer make that objection. Another is that the group leaders need to be able to make a lot of group related drop calculations, which they do with spreadsheets. Being able to import the data wold give them much more to work with and it would also be less prone to manual translation errors (entering bad data).

Anyway, thanks for considering it, I love your site!

[MadHatter6]

Hi. i cant use the mechbay at the site it said i must be loged in and i am loged in but wont let me use it.

[smurfynet]

@jacmac: thanks will try that

@madhatter6: what browser do you use?

[MadHatter6]

not shure have to ask my wife lol.

[MadHatter6]

do u mean web browser like yahoo pr google?

[smurfynet]

no like, internet explorer, chrome, opera, firefox, safari....

[Rushin Roulette]

Jacmac, on 13 February 2013 - 01:54 PM, said:

Spoiler

<br></p><p>Example build:</p><p><br></p><p><a class="bbc_url" data-cke-saved-href="http://mwo.smurfy-net.de/mechlab#i=17&l=f5dd610aa80de53aa7ec9b312f3db33e297af857" href="http://mwo.smurfy-net.de/mechlab#i=17&l=f5dd610aa80de53aa7ec9b312f3db33e297af857" rel="nofollow external" title="External link">http://mwo.smurfy-ne...f3db33e297af857</a></p><p><br></p><p>Export out a csv file like this:</p><p><br></p><p>

</p><p>Component,Head,Center Torso,Right Torso,Left Torso,Right Arm,Left Arm,Right Leg,Left Leg,Value</p><p>Front Armor,16,93,56,56,68,68,50,50,</p><p>Rear Armor,,31,28,28,,,,,</p><p>Slot0,Life Support,GYRO,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,SHOULDER,SHOULDER,HIP,HIP,</p><p>Slot1,Life Support,GYRO,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,UPPER ARM ACTUATOR,UPPER ARM ACTUATOR,UPPER LEG ACTUATOR,UPPER LEG ACTUATOR,</p><p>Slot2,Sensors,GYRO,AC/20,DYNAMIC STRUCTURE,LOWER ARM ACTUATOR,LOWER ARM ACTUATOR,LOWER LEG ACTUATOR,LOWER LEG ACTUATOR,</p><p>Slot3,Sensors,GYRO,AC/20,SRM 6 + ARTEMIS,HAND ACTUATOR,HAND ACTUATOR,FOOT ACTUATOR,FOOT ACTUATOR,</p><p>Slot4,SRM AMMO + ARTEMIS IV,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,AC/20 AMMO,AC/20 AMMO,</p><p>Slot5,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,AC/20 AMMO,AC/20 AMMO,</p><p>Slot6,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,DYNAMIC STRUCTURE,,,</p><p>Slot7,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,SRM AMMO + ARTEMIS IV,,,</p><p>Slot8,,STD ENGINE 325,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,SRM AMMO + ARTEMIS IV,,,</p><p>Slot9,,Heatsinks: 3 / 3,AC/20,SRM 6 + ARTEMIS,DYNAMIC STRUCTURE,ER LARGE LASER,,,</p><p>Slot10,,GUARDIAN ECM,AC/20,SRM 6 + ARTEMIS,ER LARGE LASER,ER LARGE LASER,,,</p><p>Slot11,,GUARDIAN ECM,AC/20,SRM 6 + ARTEMIS,ER LARGE LASER,,,,</p><p>Tonnage,,,,,,,,,100.0</p><p>Armor,,,,,,,,,544</p><p>Firepower,,,,,,,,,83.0</p><p>Max Sustained DPS,,,,,,,,,5.53</p><p>Cooling Efficiency,,,,,,,,,27%</p><p>Free Slots,,,,,,,,,1</p><p>Speed,,,,,,,,,52.7</p><p>Speed Tweaked,,,,,,,,,57.9</p><p>Heatsinks,,,,,,,,,13</p><p>Armor Type,,,,,,,,,Standard</p><p>Structure,,,,,,,,,Endo-Steel</p><p>Heatsink Type,,,,,,,,,Double</p><p>Artemis,,,,,,,,,Artemis IV</p><p>

</p><p><br></p><p>If you save this as a CSV file and load it up in Excel or another spreadsheet, it will make sense.</p><p><br></p><p>You could add additional information, I only put what was the minimum for someone to import into a spreadsheet and get a basic understanding of the build. The big benefit is that a group can build up a database of builds and a Drop Commander can use the information to calculate drop configurations much more quickly than by hand.</p><p><br></p><p>We have guys spending a ridiculous amount of time manipulating this information by hand. I'm trying to get everyone in our group to use your site, but there are two problems. One objection to using it has been "what if it disappears one day?". Well if the data is exportable, they can no longer make that objection. Another is that the group leaders need to be able to make a lot of group related drop calculations, which they do with spreadsheets. Being able to import the data wold give them much more to work with and it would also be less prone to manual translation errors (entering bad data).</p><p><br></p><p>Anyway, thanks for considering it, I love your site!

Great idea. That would go a long way to finding a balance between Dropweight/ Maneuverability and firepower for a team once CW is implemented (depending on how it is implemented).

What would be really great is if you could import builds into MWO directly (taking into account which parts you own and are useable from your Mechbay)... But alas... that isnt up to you.

Imagine how much time could be saved if you could change the build of your mech by selecting which saved configuration you want to use and you just have to fill in any blanks by purchasing the weapons/components missing from your storage.

Edited by Rushin Roulette, 14 February 2013 - 04:47 AM.

[Jacmac]

Rushin Roulette, on 14 February 2013 - 04:45 AM, said:

What would be really great is if you could import builds into MWO directly (taking into account which parts you own and are useable from your Mechbay)... But alas... that isnt up to you.

Imagine how much time could be saved if you could change the build of your mech by selecting which saved configuration you want to use and you just have to fill in any blanks by purchasing the weapons/components missing from your storage.

Well I would never expect PGi to implement an interface like that but if the MWO client had such an export/import function, it would be valuable. Anyway, Smurfy has a great tool for building mechs, if the data becomes exportable, I'm pretty sure a lot of groups/teams will use it.

[Snib]

smurfynet, on 13 February 2013 - 11:51 AM, said:

i'm thinking about it, can you send me an example how this should look like?

Don't care about csv, but I can tell you how XML export/import should look like:

Spoiler

<?xml version="1.0"?>
<MechBuilderMWO>
	<Mech id="5" chassis="COMMANDO" variant="COM-2D" name="Trollmando" clientVersion="1.2.182">
		<Loadout>
			<Head>
				<item id="2029" name="STREAK SRM AMMO" />
				<armor pts="8" />
			</Head>
			<CenterTorso>
				<armor pts="17" />
				<item id="1032" name="STREAK SRM 2" />
				<item id="2029" name="STREAK SRM AMMO" />
				<item id="3337" name="XL ENGINE 195" />
			</CenterTorso>
			<CenterTorsoRear>
				<armor pts="10" />
			</CenterTorsoRear>
			<RightTorso>
				<armor pts="14" />
				<item id="3000" name="STD HEAT SINK" />
				<item id="9006" name="GUARDIAN ECM" />
			</RightTorso>
			<RightTorsoRear>
				<armor pts="6" />
			</RightTorsoRear>
			<LeftTorso>
				<armor pts="14" />
			</LeftTorso>
			<LeftTorsoRear>
				<armor pts="6" />
			</LeftTorsoRear>
			<RightArm>
				<armor pts="12" />
				<item id="1032" name="STREAK SRM 2" />
				<item id="1032" name="STREAK SRM 2" />
			</RightArm>
			<LeftArm>
				<armor pts="12" />
				<item id="1003" name="SMALL LASER" />
			</LeftArm>
			<RightLeg>
				<armor pts="22" />
				<item id="3000" name="STD HEAT SINK" />
				<item id="3000" name="STD HEAT SINK" />
			</RightLeg>
			<LeftLeg>
				<armor pts="22" />
				<item id="2029" name="STREAK SRM AMMO" />
				<item id="3000" name="STD HEAT SINK" />
			</LeftLeg>
		</Loadout>
		<Modules>
			<item id="4002" name="CAPTURE ACCELERATOR" />
			<item id="4017" name="ADV. SENSOR RANGE" />
		</Modules>
		<Upgrades>
			<item id="2811" name="Ferro-Fibrous Armor" />
			<item id="3003" name="Standard Heat Sink" />
			<item id="3050" name="Artemis" />
			<item id="3101" name="Endo-Steel Internal Structure" />
		</Upgrades>
	</Mech>
</MechBuilderMWO>

I'm not entirely selfish here, it's the format one of my own tools is using to export my mechs straight out of the game (no, I don't think PGI would like me to publish that, so don't ask - also it cannot import them back into the game anyway).

PS:

Rushin Roulette, on 14 February 2013 - 04:45 AM, said:

Imagine how much time could be saved if you could change the build of your mech by selecting which saved configuration you want to use and you just have to fill in any blanks by purchasing the weapons/components missing from your storage.

Would be awesome, but I suppose it's not exactly in their interest for us to change between saved loadouts. They'd rather have us buy more mech bays and fill them with mechs.

Edited by Snib, 14 February 2013 - 09:09 AM.

[smurfynet]

sorry snib, the xml and json export will look a bit different

[Snib]

haha, same structure as game files would be my guess? works for me.

[Dauphni]

Starting today, I seem to have a problem with the builds I have bookmarked. The armour values are set to 0 for many random sections. It worked fine before, but now it's just gone.