But if my choice is between discussing the Vinnie and Hermie show and
their insane jihad against COMMAND and the developers of that excellent
game ... well, Shawn, where do you stand on lease / purchase? I leased
the Fusion Energi. First time I've gone down the lease road.
The only thing that upsets me is that it doesn't have a spare tire, but
the parts manager at the dealer is getting me a donut I can sling in the (virtually non-existent) trunk to keep out-of-town trips from turning
into a travel nightmare because ... flat tire.
In article <14of4zgxvh7lu.1c4jwofyt93ew.dlg@40tude.net>,
me@shawnritchie.com says...
Go back to the discussion for catastrophic converters, or whatever.
Nice try, ya weaselly little fuck.
I gave you a precise argument. You argued: Giftzy only posts about car parts. I argued back: actually, an even cursory search of this newsgroup's spool will reveal thousands of non-car-related posts by ol' Giftzy.
Not all of them well-considered, I do admit. But I stand by them.
That's a FACT, jack.
Now you're trying to spin out of it like you weren't blatantly wrong.
Y'know. Just like a fuckin' cunt would do.
But if my choice is between discussing the Vinnie and Hermie show and
their insane jihad against COMMAND and the developers of that excellent
game ... well, Shawn, where do you stand on lease / purchase? I leased
the Fusion Energi. First time I've gone down the lease road.
The only thing that upsets me is that it doesn't have a spare tire, but
the parts manager at the dealer is getting me a donut I can sling in the (virtually non-existent) trunk to keep out-of-town trips from turning
into a travel nightmare because ... flat tire.
--
Giftzwerg
***
"As Barack 'Eldrick' Obama approaches his 200th round of golf since his election as president, here?s a fact to put that into perspective: Since January 2009, Tiger Woods has played 269 rounds of golf."
- Washington Times
The only thing that upsets me is that it doesn't have a spare tire, but
the parts manager at the dealer is getting me a donut I can sling in the (virtually non-existent) trunk to keep out-of-town trips from turning
into a travel nightmare because ... flat tire.
To top it off, 'shuffling the blame onto others' is probably the only consistent behaviour for Matrix' developers. OTS was adamant that it was _absolutely and totally_ in control of its own source code. With absolute control comes absoluteresponsibility. OTS and no one else is responsible for its current problems.
On Friday, November 27, 2015 at 5:27:50 PM UTC-6, herm...@hotmail.com wrote:
responsibility. OTS and no one else is responsible for its current problems.To top it off, 'shuffling the blame onto others' is probably the only consistent behaviour for Matrix' developers. OTS was adamant that it was _absolutely and totally_ in control of its own source code. With absolute control comes absolute
You do understand that Steam has it's own situation right?
And that we have to not only make the code work with Matrix installers but Steams as well. When we aren't given the entire set of parameters to make our code work with those things can get a bit out of hand.
While we are in control of our code, we aren't in control of the demands made on that code.
Steam has their own situation as does Matrix. The fact that OTS needs to work with them both is also apparent. That means OTS must demand all the necessary parameters and then test the final code vigorously.
Blaming other companies for supposedly not giving you the entire set of parameters is just lame. Either OTS did not ask enough questions, did not demand sufficient information on the parameters, or else it failed to test their code adequately.Regardless, the only party at fault is OTS.
Given the dismal state under which v2.0.10 was released, we are not talking about isolated cases. Virtually *NO One* in the entire player community was able to play a PBEM++ game. Most Steam users could not even get the game to launch!
Once again, OTS fails to learn its lesson. OTS and no one else is responsible for the botched v2.0.10 release. Continuing to ignore the situation only means that it will happen again.
Black Hole v210bscannot fire into the hex. The units in 1814 are, essentially, invulnerable.
Rhino scenario PBEM++ has a NATO tank unit and a USSR tank unit in hex 1814 (circled in Red) at the same time.
A check of the firing range shows the hexes can be hit from 1814 (circled in Red). However, hex 1814 is, itself, a Black Hole. The tanks cannot engage one another inside it, but they can freely engage units outside the hex. Also, units outside the hex
http://www.armchairgeneral.com/forums/showpost.php?p=3144043&postcount=133
On Friday, December 4, 2015 at 6:45:36 PM UTC-6, herm...@hotmail.com wrote:
Steam has their own situation as does Matrix. The fact that OTS needs to work with them both is also apparent. That means OTS must demand all the necessary parameters and then test the final code vigorously.
ROFL!!!!! You can demand away. You get what they give you. If they forget to mention something that's an after the fact issue we get to deal with.
Regardless, the only party at fault is OTS.Blaming other companies for supposedly not giving you the entire set of parameters is just lame. Either OTS did not ask enough questions, did not demand sufficient information on the parameters, or else it failed to test their code adequately.
I didn't blame anyone I was explaining why we are working to fix the issues that came up after the last release.
When we aren't given the entire set of parameters to make our code work
Even if 'they' forget to mention something
Given the dismal state under which v2.0.10 was released, we are not talking about isolated cases. Virtually *NO One* in the entire player community was able to play a PBEM++ game. Most Steam users could not even get the game to launch!
We get the reports before you do. So, we are well aware of what happened and when. Much more so than anyone outside the development group.
Once again, OTS fails to learn its lesson. OTS and no one else is responsible for the botched v2.0.10 release. Continuing to ignore the situation only means that it will happen again.
You're right. Once again we fail to learn our lesson.
In keeping with I've failed to learn that it's the holidays and that means more free content.
I'm currently working on a scenario that will use the full 14 hour time limit for scenarios on the new BIG MAP in the Reforged DLC! If all goes well that will be available for FREE before Christmas.
I know, I know... I really should learn my lessons and stop giving away new content. Let's just mark it up to me being hard headed and that I can't help myself.
On Saturday, December 5, 2015 at 8:05:20 PM UTC-6, herm...@hotmail.com wrote:hex cannot fire into the hex. The units in 1814 are, essentially, invulnerable.
Black Hole v210bs
Rhino scenario PBEM++ has a NATO tank unit and a USSR tank unit in hex 1814 (circled in Red) at the same time.
A check of the firing range shows the hexes can be hit from 1814 (circled in Red). However, hex 1814 is, itself, a Black Hole. The tanks cannot engage one another inside it, but they can freely engage units outside the hex. Also, units outside the
http://www.armchairgeneral.com/forums/showpost.php?p=3144043&postcount=133
Which side were you playing in that scenario?
I'm currently working on a scenario that will use the full 14 hour time limit for scenarios on the new BIG MAP in the Reforged DLC! If all goes well that will be available for FREE before Christmas.
The game continues to explode with Access Violation Errors.
https://youtu.be/S1qQF7tzXWE?t=53m42s
On Monday, December 21, 2015 at 3:23:38 PM UTC-6, herm...@hotmail.com wrote:
The game continues to explode with Access Violation Errors.
https://youtu.be/S1qQF7tzXWE?t=53m42s
When was the last time you did a clean install?
Good Hunting.
MR
Premature CAS re-supply v310b
http://www.armchairgeneral.com/forums/showpost.php?p=3175690&postcount=158
In reply to "hermanhum@hotmail.com" who wrote the following:
Premature CAS re-supply v310b
http://www.armchairgeneral.com/forums/showpost.php?p=3175690&postcount=158
For Heaven's sake - I go away for a year...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 225:30:13 |
Calls: | 6,623 |
Calls today: | 5 |
Files: | 12,171 |
Messages: | 5,318,600 |