A tiltrotor combat drone with large proprotors on the wingtips, built to take off like a helicopter and cruise like a plane. The design uses 60,686 polygons and 65,312 vertices, light enough for real-time flight but detailed around the nacelles. Its slim fuselage and compact tail suggest storage on crowded ship decks.
StemCell certification keeps the gray finish and sensor glass consistent between engines. Non-overlapping UVs let you add squadron numbers, warning stripes and exhaust stains on the wings. With no cockpit glazing, the smooth nose reads as unmanned, while the huge rotor discs dominate the silhouette from the front.
Simulation teams can choose from eight versions, split between the Bell name and a generic Combat Propeller Drone UAV. Rigged copies cost $139 across Maya and Cinema 4D, while static ones stay at $119. Available since 2024, the drone fits naval aviation renders, defense technology talks and future warfare games.
Questions About This Model
How heavy is the Bell V 247 Vigilant Combat Drone mesh?
60,686 polygons and 65,312 vertices, built as polygonal quads/tris. Against a median of about 200,000 polygons across our Aircraft models, 60,686 puts this one below the middle of the category.
Where can I buy the Bell V 247 Vigilant Combat Drone 3D model?
It is sold through TurboSquid, where this listing has been available since 2024. Purchase, download and licensing are handled by TurboSquid; delivery is immediate after checkout.
Can the Bell V 247 Vigilant Combat Drone model be modified after purchase?
Yes. The license allows editing the geometry, retopologising, changing materials and adapting the asset to a project. What it does not allow is reselling or redistributing the model file itself, or using the result commercially: this listing is Editorial Uses Only.
What does StemCell mean for the Bell V 247 Vigilant Combat Drone model?
StemCell is TurboSquid's multi-format standard. The model was authored once and delivered in several formats with matching PBR materials, so shading survives the move between a game engine and an offline renderer.