Reporting Companies using Hacked Solidworks

I recently reported a company I had dealings with for using hacked
versions of Solidworks to both Solidworks and FAST - The Federation
Against Software Theft (UK only?). The result being that they contacted
the company and asked them if they were using illegal copies. Of course
they said no and painted me as a malicious disaffected former employee.
The company then had their lawyer send me a letter threatening me with
legal action if I repeated the allegation. Apparently what they lack in
integrity they make up for in boldness. For the record the company
P.A.C.T. Engineering (Scotland) Ltd. possesses no Solidworks licenses
but uses it as there only design package and had at least 3 seats
installed. They also routinely download and install any package they
think they want. To my direct knowledge they have Cosmosworks,
Camworks, PADS PCB and various MS OS's.
I expected a more vigorous intervention would result from my report. It
seems companies can easily download Solidworks and install it without
any fear of legal repercussions. It makes me wonder why people bother
paying for it.

 

What proof do you have that the SolidWorks they use is illegal? I'm not
a fan of software theft, but if you are the only one saying this you
might be on shaky ground, allegations true or not. I am rather
surprised that SW or FAST told them your name.

 

It was common knowledge. I watched them download and install it. They
took pleasure in how easy it was. I don't think SW or FAST gave them my
name, they just assumed it was me.

 

Naw they were getting hacked versions that are commonly available on
the web. They had no licenses, no dongles. They made no effort to
conceal the fact that they were stealing. They acted like they were
proud of it.

 

Well...if P.A.C.T. doesn't have licenses, your note here on the WWW
means the VAR near P.A.C.T. Engineering certainly knows about it now!

In the U.S., the ultimate defense against libel is the truth.
Unfortunately, the opposite is also true. If I state something as a
fact that specifies an individual is a criminal, and he can prove he is
not & show intent to harm, I will likely suffer the fate of the jury's
monetary verdict against me.

 

You witness, report.
SolidWorks looks into it.
They find no Wrong. Bye.

 

I am writing this letter to persuade you that P.A.C.T. Engineering
LTD's insanity has reached record levels. I will persuade you of this
by providing a few examples and illustrations of the way in which
P.A.C.T. Engineering LTD seeks to cheat on taxes. What follows is a
call to action for those of us who care -- a large enough number to
comment on its modes of thought. Is there a way to counter P.A.C.T.
Engineering LTD's fastidious, sinister slurs? Oh yes, there is a way.
It's really quite simple and can be done by any individual. It doesn't
cost a thing, monetarily. It requires only time, diligence, and a
desire to complain about abusive suborners of perjury. That's all I
have time now to write. If you want to get more insight into P.A.C.T.
Engineering LTD's mentality, though, then study the details of its
commentaries. Try to see the big picture: It will amaze you. It will
take your breath away. And it will convince you that it has been, and
is, my great undertaking to increase awareness and understanding of our
similarities and differences.

 

SaladWorks is not worth paying for.

VX *is* worth paying for !!!

I believe VX is half the price of SaladWorks in the UK.

http://www.infdatasys.co.uk/

jon

 

I feel compelled to preface my remarks with the following: VX
corporation's exegeses make about as much sense as jumping off a
building and hoping you'll sprout wings on the way down. Permit me this
forum to rant. VX corporation can't help it; it just loves to intensify
or perpetuate obscurantism. And that's what writing this sort of letter
is all about. It's a way to champion the poor and oppressed against the
evil of VX corporation.

 

How's the free demo & the ad?

 

Lets see what obscure name can we make up for VX, maybe VD.

And there is a reason that VX is half the price of SolidWorks, it is
half the program.

 

There is a reason but that's not it. Your conclusion that it's half
the price is about as accurate as VX being like IronCAD. I'd be happy
to tell you the reason VX is half the price if you just ask. My answer
will be measurable in every way unlike the wild guesses you so
desperately post.

Perhaps it's time for you to get specific rather than throwing shit at
the fan to see if anything might stick.

Please give me the specifics on why you think VX is like IronCAD.

Based on what you posted if you looked at VX it was for about 30
seconds and what your saw was way over your head.

Looking forward to seeing you post the specifics rather then the
bullshit. I'm also happy to give you the specifics if you get your head
out of your ass and ask politely why VX is half price. There is a damn
good reason why VX is half the cost of SaladWorks and it has nothing to
do with the quality of the software.

Balls in your court.

jon

 

I'm also happy to give you the specifics if you get your head

Hi Jon -

I wanted to ask you (politely and specifically) about your experiences
with VX.

Specifically, are you using this program as a single piece design and
program solution?

Are you creating the data with VX or are you importing a customer
supplied model?

Is the need for "direct manipulation" driven by the reality of customer
supplied geometry?

(And) Are you using this for large assemblies and if so what type of
performance have you had with very large data sets?

What types of machines (how many axes) are you programming with this?
VMC, etc . . .

I have asked some of this of you once before and am still interested in
hearing what you have to say on the topic. You position on soiledwonks
is clear so no comparison to solidworks will be necessary - I would
like to ask your honest opinion of VX (relative only to itself and the
work that you specifically perform) first as a CAD tool and then as a
CAM tool.

I am presently evaluating "cost sensitive" CAM systems (visual mill,
oneCNC, etc) and would like to hear your opinion on what VX really has
to offer, based on your experience with this product.

Could you relate the extent of your experience with this product
(designed and programmed 50 parts, 500 parts, 5000 parts, etc)?

Thanks,

Sean

(sorry folks this is OT but I need to scratch this itch)

 

"Specifically, are you using this program as a single piece design and
program solution? "

Not yet. Just the CAD end of VX at the moment. The reason I don't use
the CAM end will be addressed below.

"Are you creating the data with VX or are you importing a customer
supplied model?"

Both. VX IGES is the best I have ever used in any CAD/CAM system.

"Is the need for "direct manipulation" driven by the reality of
customer supplied geometry?"

Yes.

"(And) Are you using this for large assemblies and if so what type of
performance have you had with very large data sets?"

Don't work with any large assemblies at all. I have asked several times
for other SaladWorks users to do a comparison. Although I know many
SaladWorks users downloaded and checked out VX this newsgroup never got
any kind of report of how well VX does on large assemblies. I maybe
wrong but I believe I asked two regulars of comp.cad.solidworks who I
respect in some areas to evaluate this aspect of VX vs SaladWorks....
nothing of any substance was reported. So typical. : (

"What types of machines (how many axes) are you programming with this?
VMC, etc . . "

I'm not using the CAM end of VX at the moment. VX CAM does not fit my
needs at present. VX CAM is very, very powerful but it's not fast
enough IMO for the stuff we do everyday.

"I am presently evaluating "cost sensitive" CAM systems (visual mill,
oneCNC, etc) and would like to hear your opinion on what VX really has
to offer, based on your experience with this product."

VX CAM blows both of the systems you named out of the fucking water
power and feature wise. However, VX CAM does not have the speed that a
well though out UI gives you. For VX CAM to work in the kind of
environment I work in the CAM UI will have to be totally redone like
the CAD UI was redone. If you read alt.machines.cnc I have clearly
described some of the kinds of work I do at my job. I have not said a
lot about the work I do for my own clients. The VX CAM UI is not as
good CAM wise as the two systems you named.... it's not even close,
IMO. This is because what was started in VX 11 (The all new VX UI) has
not been fully implemented throughout all of VX. This also applies to
VX spline tools. Improvement is needed but I don't think one will have
to wait to long to see the next phase of the all new UI that was rolled
out with VX 11.

"Could you relate the extent of your experience with this product
designed and programmed 50 parts, 500 parts, 5000 parts, etc"

Over 50 parts designed / modified with VX starting with VX 10.

If one has been around awhile, isn't a product loyalist, doesn't need
to keep up with the Jones, has used other CADCAM systems they quickly
realize how powerful VX's kernel is. It is beyond clear to me that all
the power is there in VX's proprietary kernel, even on the CAM end
where VX has had 5 axis simultaneous for years.

What VX needs is continued UI work. The amount of progress VX made
between VX 10 and VX 11 was mind blowing to me. The rest will follow. I
have never felt the need to tell VX what direction I feel they need to
go in with product development. They already know.

I suggest frustrated SaladWorks users read the following links very
carefully and think about what is different about how VX is developed
and who develops VX compared to SaladWorks.

http://www.vx.com/background.cfm

http://www.vx.com/vorwaller.cfm

Mark Vorwaller has been there from day one.

You want to ask some questions about VX AE and VX VARs in my area and
in Southern California ?

How about VX documentation ?

Hope you were not expecting some line of fucking bullshit now that you
*finally* got the balls to ask questions that you and other SaladWorks
users should have been asking about VX for years.

How about changes VX has made for post processing ?

How about VX Seminars on the West Coast ?

How about ???


jon (SaladWorks.... Toss It !)

"I may have many faults, but being wrong ain't one of them." ... Jimmy
Hoffa

 

Thanks Jon -

I appreciate your response. I think that an underdeveloped UI is very
common with many CAM programs and its not a shock. I've seen a few and
just have to giggle - straight out of the late 80's. Things are
progressing though. Sometimes a very ample CAM program can have a
really bad look but do its Job really well.

Ok now for the follow up - what specific experience do you have with
solidworks? I'm really curious here and trying to frame your state of
mind and dislike for the product - are you a former user and have found
something better? Like the same question along the 50, 500, 5000 idea.

I must say that a "direct manipulation" model would be a very big
advantage for taking in many types of data, but not so necessary if one
has a native file & system available (i.e. not locked out of the car,
so to speak).

The large data set thing would be really hard for a non-hardcore "real"
user (i.e. a solidworks person "playing around" with a demo). I just
wondered if they hit the wall has hard as we do when we get into the
500+ model threshold (i.e. they all die, just curious as to where)

Later,

Sean

"I may have many faults, but being ALIVE ain't one of them." ...
Possibly Jimmy Hoffa (SMILE - perfection exists just not often in
this life . . . ? )

 

Sean-Michael Adams,
I have used SolidWorks in the past for about 7 years. I still use it at
client sites for consulting. We own:
- VX "mold and die" - history based surface modeling, large scan
importing from Geomagic
- Visual Mill - budget CAM to run my Bridgeport mill - I bought VM
before I ever knew about VX
- Rhino - non-history based surface modeling, I bought this before I
found out about VX
- Geomagic - Reverse Engineering - point cloud to mesh to nurbs

When chosing a modeler it was between VX, Alias Studio Tools,
SolidWorks, ProE with surfacing extension, ImpactXoft, and ThinkDesign.
We evaluated all the above packages with importing large scan files
from Geomagic. I had 7 years of SolidWorks experience and my coworker
had about the same in Alias. In the end, we chose VX and are very happy
with our decision. We use VX in order of our importance: 1. surfacing
modeling 2. interfacing with large file imported meshes 3. small
assemblies. 4. export models as IGES for outsourced manufacturing 5.
techincal drawings.

We do not do large assemblies. However, if you are sincere in you quest
for large assembly performance, I suggest you call the friendly guys at
VX and ask them about it. They can tell you about their internal
benchmarks against Catia and UGS (and perhaps SolidWorks) Ask for Chris
W at VX, he has Catia experience.

As for my experience with VisualMill, all I can say is that I wanted to
get SprutCam but at the time it was only from Russia and I am a CAM
novice so I wanted to buy from a company with good English support. VM
has great support. Anytime I had a problem or question, they took care
of it usually that same day. I also looked briefly into Onecnc, it
looks like a real winner to me.

Geomagic just plain kicks butt. Their technology is amazing, EXPENSIVE,
but amazing. I think we paid about $20k for one seat. There are only 3
major players that make this type of software. ProE sells an extension
that uses stripped down Geomagic code.

Best of luck and if you want to know more about VX, the guys at VX are
truly cool, give them a call. They are not salesmen types like I came
across with inquiring about ThinkDesign and ProE. They won't bash
SolidWorks, but they do know SolidWork's strengths and weaknesses. I
never asked VX about their CAM because I already owned VM. VX started
out as a CAD/CAM package for Samsung I believe.

Happy New Year!!

Haulin79

 

Thanks a million. It's nice to have strong testimony like that and
good "pros & cons" with the "been there - know the ropes" sensitivity.

Thanks as well for the input on VM - I got the demo and was able to do
some reasonable 2.5 axis programing and get a handle on the methodology
- the entry point is unreasonably attainable and I need something that
can do almost exclusively prismatic parts (we are talking small scale
here).

Have a nice one - I truly appreciate your reply.

Sean

 

It's Korean dollars as they stave off possible bankruptcy?

 

You were whining on a BBS system that it did not work IIRC.

You don't and could not do anything more than simple
prismatic parts with a few holes in them, if even that.

 

So the UI you were bragging about last is trash?
And what has the UI to do with system speed in computing
tool paths? Missed that, eh?
OTOH It's not like you ever do such things.