AnsweredAssumed Answered

Automatic Mirroring

Question asked by Scott McFadden on Jul 23, 2010
Latest reply on Aug 21, 2010 by Scott McFadden

Like • Show 0 Likes0
Comment • 12

If I hadn't seen this with my own two eyes I wouldn't have believed it.

Here is the scenario,

Was working on a fairly complex assembly andf had the housing of that

assermbly opened as well, with cascaded windows, made an update to the housing and went back to my

assembly and the boss features of that housing were mirrored. Opposite side from where they are supposed to be.

Keep in mind going back to the part every feature is where it is supposed to be. Back to the assembly and it is mirrored.

If you close that housing out and reopen it through the assembly the housing calls up fine, but still showing mirrored

in the assembly. If you close out of everything and and do a hard reboot of the machine, sqame thing occurs.

Now, on top of the irraneous mirroring, the assembly is showing transparent. With no transparency settings active.

Has anyone experienced this? If so any solutions? Or do we chaulk this up to the corkyness of Solidworks 2010.

Thanks

No one else has this question

Outcomes

Alin Vargatu Jul 23, 2010 7:36 AM

Any chance the part has a configuration with a mirrored body?

Can you post a pack'n'go zip file of the assembly. Delete all the other parts, leave only the part in question and save under a new name first.

Actions

Scott McFadden @ Alin Vargatu on Jul 23, 2010 8:30 AM

Alin,

No configurations involved.

Not a good idea for me to post any part of the assembly on this portal.

I work for a company with high proprietary rules.

Ended up starting a new assembly and inserting the bad assembly into it and

dissolving the bad assembly.

It worked. I was just hoping someone else had experienced it

and found a solution.

Actions

Alin Vargatu @ Scott McFadden on Jul 23, 2010 12:47 PM

Glad to hear you solved it.

I am still intrigued about what went on there... Too bad you cannot dumb down the parts/assembly and post them here.

Actions

Scott McFadden @ Alin Vargatu on Jul 23, 2010 12:40 PM

Thanks Alin,

This is just another in the list of quarky things that have been

occuring in Solidworks 2010.

I don't know about you, but this is the most unstable version I have seen. But with that

said this is also the first time I have run the software with a 64 bit machine.

Actions

Alin Vargatu @ Scott McFadden on Jul 23, 2010 12:49 PM

Still, any issue can and should be troubleshooting. That is the only way they can be fixed or at least a workaround can be found.

Have you created at least an Rx report and send it to your VAR?

Actions

Scott McFadden @ Alin Vargatu on Jul 23, 2010 1:01 PM

I agree with whole heartedly. Some though are enough to make your head spin strying to figure them out.

Rx? I have used it, but only when I can consistenly duplicate the problem.

With an exisiting issue that happens out of nowhere I am not sure Rxing it after the

fact would be benificial. Unless I am missing something.

Actions

Alin Vargatu @ Scott McFadden on Jul 23, 2010 1:03 PM

After the fact, most likely not. Unless you have back-up-ed files.

Actions

Kelvin Lamport @ Scott McFadden on Jul 23, 2010 12:49 PM

For every version there has always been a group (different each time) which claims that the latest version is the worst/least stable so far, and others claiming it is the best/most stable. As the saying goes, "your mileage may vary".

Actions

Scott McFadden @ Kelvin Lamport on Jul 23, 2010 1:12 PM

Fair enough.

I personally am speaking based on having used 9 versions.

Actions

Alin Vargatu @ Scott McFadden on Jul 23, 2010 1:28 PM

... and the last version is supposed to work on 6 different operating systems...

Actions

Scott McFadden @ Alin Vargatu on Aug 21, 2010 8:00 AM

Key word is supposed to...

Actions

Scott McFadden Aug 21, 2010 8:01 AM

Worked itself out on it's own

Actions

12 Replies

Alin Vargatu Jul 23, 2010 7:36 AM
Mark Correct
Correct Answer
Any chance the part has a configuration with a mirrored body?

Can you post a pack'n'go zip file of the assembly. Delete all the other parts, leave only the part in question and save under a new name first.
Like • Show 0 Likes0
Actions
- Scott McFadden @ Alin Vargatu on Jul 23, 2010 8:30 AM
  Mark Correct
  Correct Answer
  Alin,
  No configurations involved.
  
  Not a good idea for me to post any part of the assembly on this portal.
  I work for a company with high proprietary rules.
  
  Ended up starting a new assembly and inserting the bad assembly into it and
  dissolving the bad assembly.
  
  It worked. I was just hoping someone else had experienced it
  and found a solution.
  Like • Show 0 Likes0
  Actions
  - Alin Vargatu @ Scott McFadden on Jul 23, 2010 12:47 PM
    Mark Correct
    Correct Answer
    Glad to hear you solved it.
    I am still intrigued about what went on there... Too bad you cannot dumb down the parts/assembly and post them here.
    Like • Show 0 Likes0
    Actions
    - Scott McFadden @ Alin Vargatu on Jul 23, 2010 12:40 PM
      Mark Correct
      Correct Answer
      Thanks Alin,
      
      This is just another in the list of quarky things that have been
      occuring in Solidworks 2010.
      I don't know about you, but this is the most unstable version I have seen. But with that
      said this is also the first time I have run the software with a 64 bit machine.
      Like • Show 0 Likes0
      Actions
      - Alin Vargatu @ Scott McFadden on Jul 23, 2010 12:49 PM
        Mark Correct
        Correct Answer
        Still, any issue can and should be troubleshooting. That is the only way they can be fixed or at least a workaround can be found.
        
        Have you created at least an Rx report and send it to your VAR?
        Like • Show 0 Likes0
        Actions
        Scott McFadden @ Alin Vargatu on Jul 23, 2010 1:01 PM
        Mark Correct
        Correct Answer
        I agree with whole heartedly. Some though are enough to make your head spin strying to figure them out.
        
        Rx? I have used it, but only when I can consistenly duplicate the problem.
        With an exisiting issue that happens out of nowhere I am not sure Rxing it after the
        fact would be benificial. Unless I am missing something.
        Like • Show 0 Likes0
        Actions
        Alin Vargatu @ Scott McFadden on Jul 23, 2010 1:03 PM
        Mark Correct
        Correct Answer
        After the fact, most likely not. Unless you have back-up-ed files.
        Like • Show 0 Likes0
        Actions
      - Kelvin Lamport @ Scott McFadden on Jul 23, 2010 12:49 PM
        Mark Correct
        Correct Answer
        For every version there has always been a group (different each time) which claims that the latest version is the worst/least stable so far, and others claiming it is the best/most stable. As the saying goes, "your mileage may vary".
        Like • Show 0 Likes0
        Actions
        Scott McFadden @ Kelvin Lamport on Jul 23, 2010 1:12 PM
        Mark Correct
        Correct Answer
        Fair enough.
        
        I personally am speaking based on having used 9 versions.
        Like • Show 0 Likes0
        Actions
        Alin Vargatu @ Scott McFadden on Jul 23, 2010 1:28 PM
        Mark Correct
        Correct Answer
        ... and the last version is supposed to work on 6 different operating systems...
        Like • Show 0 Likes0
        Actions
        Scott McFadden @ Alin Vargatu on Aug 21, 2010 8:00 AM
        Mark Correct
        Correct Answer
        Key word is supposed to...
        Like • Show 0 Likes0
        Actions
Scott McFadden Aug 21, 2010 8:01 AM
Mark Correct
Correct Answer
Worked itself out on it's own
Like • Show 0 Likes0
Actions

Automatic Mirroring

Outcomes

Related Content

Recommended Content