The making of the revolution.

Giant’s first 29er trail bike will be built with butted and hydroformed Aluxx aluminum tubing produced in-house for a claimed frame weight of 2,670g (5.89lb, medium size with rear shock and hardware). Rear wheel travel is set at five inches via the company’s familiar and well proven Maestro dual-link suspension design.

A few key geometry tweaks suggest the Trance X 29er won’t just be a longer-legged version of the current Anthem X 29er, though. In fact, the five-inch bike might end up being the more capable of the two overall. Most importantly, chain stay length has decreased by 10.1mm (0.4″) to 452mm (17.8″), courtesy of the single upright on the enclosed rear triangle, which should make the Trance X 29er more maneuverable despite the increased travel.

The head tube angle is 69 degrees, which should strike a nearly ideal balance between quickness and high-speed stability, based on our experience with other 29ers with similar front-end figures.

Giant will outfit the Trance X 29er with the company’s usual laundry list of frame features: an OverDrive 2 front end with a 1.125-to-1.5in tapered steerer; a 92mm Powercore bottom bracket shell with press-fit cups; and a correspondingly wide MegaDrive down tube. What does come as a bit of a surprise, however, is the fully internal cable routing – at least through the front triangle – including the rear brake and dropper seatpost.

The top-end GiantTrance X 29er 0

Front triangles will have room for at least one small bottle, too, and direct-mount front derailleurs are used across the board.

While 15mm thru-axle forks are featured throughout the line, one notable omission is a matching thru-axle rear end – something that’s quickly becoming an industry standard. As with the Anthem X 29er, Giant contends that the Maestro design’s enclosed rear end is inherently more rigid than four-bar or faux-bar configurations, so including one would only add weight without adding benefit. Perhaps that’s true, but with an increasing number of companies moving in that direction – even holdout Santa Cruz has conceded – it seems a thru-axle rear would aid in future wheel compatibility down the road.

Giant will offer three Trance X 29er models in five sizes (XS-XL) for 2013:

  • the Trance X 29er 0 with a FOX 32 Float 29 FIT CTD fork, Float CTD BoostValve rear shock, and Shimano Deore XT 2×10 group
  • the Trance X 29er 1 with a non-BoostValve FOX rear shock and a SRAM X7/X9 2×10 blend
  • the Trance X 29er 2 with a RockShox Recon Silver fork and Monarch rear shock with a mix of SRAM X5 and X7 2×10 drivetrain parts

No carbon ‘Advanced’ models have been announced, but given Giant’s standard product development cycle, we expect one to appear in the lineup no more than a year after the aluminum introduction.

You must log in to post a comment.

ATTENTION! (by Comprehensive Google Map Plugin)

Google found the following address(es) as NON-geographic and could not find them:

[REPLACE]
Consider revising the address(es). Did you make a mistake when creating marker locations or did not provide a full geo-address? Alternatively use Google web to validate the address(es)", "kml" : "ATTENTION! (by Comprehensive Google Map Plugin)

Dear blog/website owner,
Google returned the following error when trying to load KML file:

[MSG] ([STATUS])", "kmlDocInvalid" : "The KML file is not a valid KML, KMZ or GeoRSS document.", "kmlFetchError" : "The KML file could not be fetched.", "kmlLimits" : "The KML file exceeds the feature limits of KmlLayer.", "kmlNotFound" : "The KML file could not be found. Most likely it is an invalid URL, or the document is not publicly available.", "kmlRequestInvalid" : "The KmlLayer is invalid.", "kmlTimedOut" : "The KML file could not be loaded within a reasonable amount of time.", "kmlTooLarge" : "The KML file exceeds the file size limits of KmlLayer.", "kmlUnknown" : "The KML file failed to load for an unknown reason.", "msgApiV2" : "ATTENTION! (by Comprehensive Google Map Plugin)

Dear blog/website owner,
It looks like your webpage has reference to the older Google API v2, in addition to the API v3 used by Comprehensive Google Map! An example of plugin using the older API v2, can be jquery.gmap plugin.

Please disable conflicting plugin(s). In the meanwhile, map generation is aborted!", "msgMissingMarkers" : "ATTENTION! (by Comprehensive Google Map Plugin)

Dear blog/website owner,
You did not specify any marker locations for the Google map! Please check the following when adding marker locations:
[a] In the shortcode builder, did you add location(s) and clicked the Add button before generating shortcode?
[b] In the widget, did you add location(s) and clicked Add button before clicking Save?

Please revisit and reconfigure your widget or shortcode configuration. The map requires at least one marker location to be added..", "msgNoGoogle" : "ATTENTION!(by Comprehensive Google Map Plugin)

Dear blog/website owner,
It looks like Google map API could not be reached. Map generation was aborted!

Please check that Google API script was loaded in the HTML source of your web page"} ">