Rigged 3D Cyclist Characters & Bike Creation

3D Cyclist Characters + Road Bike ####################################################################### #######My budget is $100 USD; if you do not consider this sufficient, do not place a bid.####### ####################################################################### ###############Attached photos are for reference only.############################ **Deliverables:** 2 rigged cyclist characters + 1 road bike ## 1. Characters required Four separate characters: | 1 | Male cyclist A | base male | | 2 | Female cyclist A | base female | ## 2. File format **Primary deliverable: `.glb` (glTF 2.0 binary), one file per model.** This is what the application loads directly. Please do not substitute another format. - Textures **embedded inside the .glb**, and also supplied separately as `.png`. - Also include the editable source (`.blend`, `.max`, `.ma` or `.c4d`) and an `.fbx`, for future edits. These are archive copies; the `.glb` is the one that ships. - Please verify each `.glb` opens correctly in a neutral viewer ([login to view URL]) **before delivery**, with the skeleton visible. ## 3. Scale, orientation, origin - **Units: metres, real-world scale.** Male ≈ 1.78 m standing, female ≈ 1.68 m. Road bike wheel: 700c, **0.67 m outside diameter**. - **Y up. Character and bike both face +Z.** - **Origin at (0, 0, 0) on the ground plane**, under the bike's centre — not at the hips, not at the mesh centre. Lowest vertex of the tyre sits at exactly y = 0. - No transforms baked into parent nodes: the mesh must be correct with an identity transform on the root. ## 4. Polygon budget **Every model must be delivered at three levels of detail**, as three separate `.glb` files. This is the single most important requirement in this brief. ### Cyclist (body + clothing + helmet + shoes, **excluding** the bike) ## 5. Rigging — requirements, not preferences The application drives the legs **live, from the student's real pedalling cadence**. The model is never played back as a canned animation. So the rig must be usable by code. **Required:** - A standard humanoid skeleton, **exported inside the `.glb` with skinning data** (glTF `skin`, `JOINTS_0`, `WEIGHTS_0`, `inverseBindMatrices`). A `.glb` whose skeleton exists only in the source file is a failed delivery. - **Maximum 4 bone influences per vertex** (glTF standard limit). - **Maximum 64 bones** in the skeleton. Fingers may be a single bone per hand or omitted. - These bones must exist, with a clean parent chain, on **both legs**: `hips → thigh → shin → foot` and on both arms: `chest → shoulder → upperarm → forearm → hand`, plus `spine`, `chest`, `neck`, `head`. - **Delivered in the riding pose**, seated on the bike, hands on the hoods, foot on the pedal — not in a T-pose. The bind pose may be a T-pose; the default node transforms should place the character on the bike. - Weights around the **hip and knee** must be clean: the thigh will be rotated through a full pedal revolution (about 75° of travel) and must not tear or collapse the shorts. **Not required:** animation clips. If you include a pedalling cycle it is welcome as a reference, but the application will not play it. ## 6. The bike — wheels must be separate, named nodes **This is worth reading carefully; it is the item that has cost us the most time.** The bike must be a **separate `.glb`** from the cyclist (we mix riders and bikes and recolour them independently). Inside the bike file, the following must be **separate nodes with these exact names**: | node name | contents | pivot / origin must be | |---|---|---| | `roda_dianteira` | front wheel: rim, tyre, spokes, hub, disc | **exactly at the front axle** | | `roda_traseira` | rear wheel: rim, tyre, spokes, hub, cassette, disc | **exactly at the rear axle** | | `pedivela` | crank arms, chainring, pedals | **exactly at the bottom-bracket axis** | | `quadro` | everything else: frame, fork, bars, saddle, seatpost | origin at (0,0,0) | The wheels are rotated in code every frame. If a wheel's pivot is not at its axle it will wobble; if frame geometry is inside the wheel node it will be swept around with it and the bicycle will visibly tear apart. **Nothing that stays still may live inside a wheel node, and no part of the wheel may live outside it.** Please also state, in the delivery notes, the **exact wheel radius in metres** and the **bottom-bracket height and Z position**. ## 7. Materials and textures - **PBR metallic-roughness** (the glTF standard). No Vray / Arnold / Redshift-only setups — those do not survive the export. Power-of-two, no overlapping UVs. ### Separate materials required list The application recolours parts independently, so these must be **distinct materials with these names**, not merged into one atlas: `camisa` (jersey) · `bermuda` (shorts) · `capacete` (helmet) · `pele` (skin) · `sapato` (shoes) · `cabelo` (hair) · `oculos` (glasses) and for the bike: `quadro_pintura` (painted frame) · `roda` (rims/tyres) · `metal` (chain, cassette, cranks) · `selim` (saddle) · `guidao` (bars/tape). ### Colour: deliver the recolourable parts NEUTRAL **`camisa`, `bermuda`, `capacete` and `quadro_pintura` must be authored in neutral white or light grey**, with all the shading, seams, wrinkles, logos and panel lines present but **no strong hue**. The application multiplies a per-student colour over these materials at runtime. Starting from neutral, any colour comes out correctly. Starting from a saturated purple, we can only shift the hue — purple to blue works, purple to white or yellow does not. Neutral base textures are what make "any colour, any student" actually possible. Skin, hair, shoes and metal should be authored in their final colours as normal.

Project ID: 40682930