Skip to main content
M
mtepermeister1-Visitor
1-Visitor
November 30, 2014
Solved

PTC Kit of Parts Compatibility

  • November 30, 2014
  • 2 replies
  • 1344 views

Hi.

Is the KOP for the 2015 FRC game going to be released in a format compatible with both Creo 3.0 and Creo 2.0?

The reason I ask is that it seems that parts created in 2.0 are openable in 3.0, but when that part is saved in 3.0, 2.0 can no longer open it.

Our team has 2.0 installed on all of our school computers, and if the KOP is going to be released in 3.0 format, that would be awesome to know since then we can switch our computers to 3.0 before the season starts and everything gets crazy (In a good way).

Thanks so much,

~ Max Tepermeister FIRST FRC Team 2877 (The LigerBots)

    Best answer by sm_01

    Great question. PTC will be providing all KOP models in Creo 2.0 format. It would be too disruptive to release them as Creo 3.0 models since many teams have not updated to Creo 3.0 yet.

    If you're still undecided, you can pick up Creo 3.0 @ http://www.ptc.com/communities/academic-program/k12/students/first/software

    Creo+3.png

    2 replies

    S
    sm_011-VisitorAnswer
    1-Visitor
    December 1, 2014

    Great question. PTC will be providing all KOP models in Creo 2.0 format. It would be too disruptive to release them as Creo 3.0 models since many teams have not updated to Creo 3.0 yet.

    If you're still undecided, you can pick up Creo 3.0 @ http://www.ptc.com/communities/academic-program/k12/students/first/software

    Creo+3.png

      R
      rjohnson-41-Visitor
      1-Visitor
      January 4, 2015

      We were using Creo v2 up until December but have fully switched to Creo v3 and it's pretty seamless. The new import feature alone is handy for pulling parts in from AutoDesk and SolidWorks. We were able to easily use it to import the new 2015 KOP items from the SolidWorks files on usfirst.org.

      We have Creo v2 and v3 installed on a couple of our machines just in case. But v3 has been rock-solid and we're planning to dump all our v2 work ASAP. One area we found that did not like switching was Windchill integration. We did all of our Windchill setup in v3. When I went back and loaded v2, it complained about the Windchill connection, but I was able to re-establish it. However, once I went back to v3, I could not get it to re-connect to Windchill at all until I deleted the v3 cache directory and restarted v3.

      So really, v3 is the way to go. Seamless, stable, and a lot of nice new features.

      Rande J.

      Mentor FRC 4931 & FTC8620

        Terms & ConditionsAccessibility statement