Qwen3.6 27B MTP vs GPT-5.5 | Local AI Head-to-Head
In this video, I put Qwen3.6 27B Q8 head-to-head against GPT-5.5 to see how a local model running on consumer hardware compares against one of the strongest frontier coding models. Both models were given the same prompts at the same time so we could compare speed, coding ability, creativity, interactivity, UI polish, game logic, physics, and how well each one handled single-file HTML projects. In this test, the models build: • Sled Sketch — a Line Rider-style physics sandbox • Cubicle Chaos • Smart City Emergency Command Dashboard This is not meant to be a perfect scientific benchmark. It is more of a real-world coding head-to-head to see how these models actually behave when given the same tasks side by side. Let me know which model you think won and what matchup I should test next. #Qwen #Qwen36 #GPT55 #LocalAI #LLM #AICoding #OpenSourceAI #RTX3090 #TokenChaser
Video
Models Tested
Prompts Used
You are in a coding head-to-head competition against another AI model. Your goal is to create the best possible result from this prompt. Create a single HTML file for a Line Rider-style physics sandbox game called Sled Sketch. The player should be able to draw tracks with the mouse, press play, and watch a small sled rider slide along the drawn lines using gravity and physics. The game should include: - A start/help screen or instructions panel - A drawing canvas where the player can draw track lines - Different tool modes such as Draw Track, Erase, Move Camera, and Place Rider - A Play/Pause button - A Reset Rider button - A Clear Track button - Gravity-based sled movement - Collision detection between the sled and drawn track lines - Momentum, sliding, bouncing, and falling - A small rider or sled character that visually rotates based on movement - Camera follow mode so the rider can move across a larger track - Zoom controls or a simple minimap if possible - Speed display, distance traveled, airtime, and crash counter - Fun effects like sparks, snow dust, crash particles, and speed trails - Best distance stored locally Make it feel playful, smooth, and satisfying. The player should be able to draw ramps, hills, drops, and loops or loop-like shapes, then watch the sled react to the track. Use a clean winter/arcade style with a dark blue snowy background, glowing track lines, smooth animations, and responsive controls. The game should be genuinely playable and interactive, not just a drawing demo. Keep everything in one HTML file with the CSS and JavaScript included. Name the file sled-sketch.html. Once you are finished, go back over all of your code, test the logic mentally, make sure everything works correctly, and fix anything that may be broken or incomplete before giving the final answer.
You are in a coding head-to-head competition against another AI model. Your goal is to create the best possible result from this prompt. Create a single HTML file for a funny first-person office chaos game called Cubicle Chaos. The player is stuck in a boring office and has to survive waves of angry office supplies, malfunctioning printers, rolling chairs, coffee spills, and paper airplanes. The player should move around an office in first-person view, aim with the mouse, and throw rubber bands, coffee cups, or sticky notes at enemies. The game should include: - A start screen with controls - First-person movement using WASD - Mouse aiming or pointer-lock style aiming if possible - Shooting or throwing with mouse click or spacebar - A simple office map with cubicles, desks, printers, meeting rooms, vending machines, and break room areas - Funny enemies such as angry printers, stapler bots, rolling chairs, flying paper airplanes, and coffee slime - Health, ammo, reload, score, wave number, and timer - Pickups like coffee boost, extra rubber bands, medkits, and snack packs - Different weapon types such as rubber bands, coffee splash, and sticky note traps - Wave-based difficulty that gets more chaotic over time - Collision detection with walls, enemies, projectiles, pickups, and desks - Throw effects, hit effects, explosions of paper, screen shake, and damage feedback - A minimap or radar showing enemy positions - Game-over screen with final score and restart button - Best score stored locally Make the game funny, chaotic, and playable. Use bright office lighting, silly animations, floating damage numbers, paper confetti, printer smoke, coffee splashes, and arcade-style feedback. It should feel like a ridiculous browser FPS mini-game, not just a static visual demo. Keep everything in one HTML file with the CSS and JavaScript included. Name the file cubicle-chaos.html. Once you are finished, go back over all of your code, test the logic mentally, make sure everything works correctly, and fix anything that may be broken or incomplete before giving the final answer.
You are in a coding head-to-head competition against another AI model. Your goal is to create the best possible result from this prompt. Create a single HTML file for a polished Smart City Emergency Command Dashboard. This should feel like a real production web app used by a city operations team during major events and emergencies. It should not look like a basic analytics mockup. The dashboard should monitor live city conditions, emergency calls, traffic incidents, weather alerts, power outages, hospital capacity, public safety units, and active response zones. Include realistic sample data for a mid-sized city with police, fire, EMS, hospitals, power grid areas, traffic cameras, shelters, and weather stations. The dashboard should include: - A hero summary section showing active incidents, emergency response units available, average response time, power outage count, hospital capacity, and city risk level - A live city map-style panel showing different zones, incident markers, traffic congestion, outage areas, and response units - Emergency call queue with priority levels, location, type, status, and assigned unit - Incident cards for fires, crashes, flooding, medical calls, road closures, severe weather, and power outages - Traffic and road condition panel with congestion level, blocked roads, and camera status - Weather alert panel showing storm intensity, wind speed, rainfall, temperature, and flood risk - Hospital capacity cards showing ER load, available beds, ambulance wait time, and trauma status - Power grid panel showing outages, affected customers, repair crews, and estimated restoration time - Response unit tracker for police, fire, EMS, utility crews, and rescue teams - Charts for incident volume, response time, outage trend, hospital load, and weather risk - Event log showing live updates like “Fire unit dispatched,” “Flood warning issued,” or “Power restored in Zone 3” Add interactive controls so the user can switch between Overview, Incidents, Traffic, Weather, Power, Hospitals, and Units. The user should be able to filter incidents by severity, assign a response unit to an incident, mark incidents as resolved, toggle simulated storm mode, search by zone, and sort emergency calls by priority or time. Make the UI premium, modern, and visually exciting with a dark command-center style, glassmorphism panels, neon emergency accents, smooth animations, glowing map markers, responsive layout, hover effects, and strong visual hierarchy. Keep everything in one HTML file with the CSS and JavaScript included. Name the file smart-city-command-dashboard.html. Once you are finished, go back over all of your code, test the logic mentally, make sure everything works correctly, and fix anything that may be broken or incomplete before giving the final answer.