Home Creators Posts Import Register Favorites Logout

Content

Thank you for supporting EvoForge! 1.1.51 brings two big things. The track builder had a full pass on what it generates from the map: roads without sudden bumps or steps, streets that read as streets, pavements up to the façades, buildings closer to the real place, and free roam without the wrong-way warning. And the drone of the in-game apps now flies like a real one. The in-game apps, drone included, are free for everyone.

Track builder: free roam is really free roam

  • No more "Driving in the wrong direction". On a free-roam map the game used to show the warning as soon as you left the hidden loop or drove it backwards. Free-roam maps now tell the game not to check the direction, anywhere on the map. Seen in game: banner on 6 of 12 pictures before, 0 of 12 after, against the loop and in the side streets.

  • Your free-roam maps already installed are updated by EvoForge itself, with the game closed: nothing to rebuild.

  • Hosting a free-roam map: driving against the loop is no longer checked by the server.

Track builder: roads without bumps or steps

  • City streets. The height of every street is now solved together with its junctions, with a gentle minimum curve where the slope changes. On our Annecy test area: bumps over 15 cm from 14 to 2, steps of 10 to 30 cm between two carriageways from 731 m to 5 m. On central Lyon: bumps from 127 to 30.

  • Dual carriageways and lanes side by side now share the same level: the step between the two halves is gone (up to 26 cm on a player's project).

  • Mountain hairpins. The map draws them far tighter than they are. They are now opened to a radius a car can take, with the extra width of a real hairpin, a smooth entry, and banking that never leans the wrong way.

  • Retaining walls between two legs of a stacked hairpin, instead of a spike of ground. Guard rails, walls and fences drawn on the map are placed where the map has them. Unpaved roads look unpaved.

Track builder: streets that look like streets

  • The carriageway has its own asphalt, centre line where the street is wide enough, edge lines on main roads. Yards and car parks keep a worn surface: from above you can read the street plan.

  • Pavements. They now reach the façade when the building is close, the kerb has a lighter edge, and it drops at pedestrian crossings.

  • Car parks from the map get painted bays, and the parked cars stand in them.

  • Railways and trams (ballast and rails, level crossings flush with the road), mini-roundabouts, and speed bumps from the map — off by default, with a switch in Scenery when the map has some.

Track builder: buildings closer to the real place

  • Façades in bays. Windows are never cut or stretched any more; each building picks its tint and window style; the ground floor is its own level with a front door, a garage door on houses, shop fronts in town centres and where the map has a shop.

  • Roofs read from the aerial photo: tiles, grey roofs or light flat roofs, as on the real building. Balconies and a cornice on blocks of flats.

  • Recognisable buildings: churches with a bell tower, warehouses with sectional doors, offices, barns. A village now looks like a village.

Track builder: fixes from your reports

  • Painting the ground in a city area did nothing: generated yards and car parks were covering your paint. Your paint now wins.

  • Fill stops at the streets instead of flooding the whole area.

  • The terrain brush starts at 40 m in an area (streets only follow a wide stroke), and the Road tool says how to remove a street (Alt+click).

  • A build that runs out of memory now says so, in your language.

  • Editing a large area is much faster: on a 2 km area, a ground brush stroke or a building edit is shown in about 8 s instead of more than a minute, with the same result. Terrain strokes and street edits still take a full rebuild.

  • TV cameras are available when an area carries a circuit.

  • First build of a project is faster (its aerial textures are prepared on all cores).

FPV: a real quad on your gamepad

  • Real FPV flight. The FPV mode is now a full quadcopter model, the kind FPV simulators use: thrust along the drone's axis, gravity, drag, motors that take a moment to spin up. Pitch forward and it accelerates, cut the throttle and it falls.

  • Betaflight rates. The sticks follow the rate curve of Betaflight, the firmware of most FPV drones (Actual rates: centre sensitivity, max rate, expo). Default: 670°/s at full stick, as in Betaflight.

  • Acro for real. Rolls, loops and inverted flight are possible: release the sticks and the drone keeps its attitude. Prefer an easy start? Turn on Angle mode in the Drone app: the sticks then set a lean angle (55° at most) and the drone levels itself.

  • Throttle on a gamepad. A gamepad stick springs back to the centre: centre is hover, down cuts the motors, up is full power.

Camera drone: real-world values

  • DJI mode behaves like a real camera drone in its normal mode: 15 m/s top speed, 6 m/s up and down, 120°/s of yaw, and the acceleration and braking of a drone that leans 30 to 35°. It was tuned much slower before.

  • Your own settings are kept. Values that were still the old defaults move to the new ones.

Automatic follow: changing car

  • A smooth travel to the next car. When you change the followed car, the drone now takes the time the distance needs (one more second per 30 m, 9 s at most), leaves and arrives gently, and the camera pans from one car to the other instead of snapping onto the new one.

  • In FPV follow, the picture banks less during that travel and when the camera looks down.

Known issues

  • Track builder: re-import your project to get the new city ground sorting, tunnels in areas, shops, railways and speed bumps from the map. A project you have edited is never re-processed on its own: your changes stay as they are.

  • Track builder: the retaining walls of stacked hairpins are tall plain concrete for now.

  • Acro FPV is as demanding as the real thing on a gamepad: start with Angle mode.

  • A drone flown by hand into a building's canopy can stay held against it when the automatic follow starts: fly it out first, or land and take off again.

Thanks again for your support. Feedback is welcome on the Discord: https://discord.gg/x3w7eCDFkK

Files

Comments

Vins Cenzo

Merci pour ton travail, grâce à toi je peux m'amuser sur mon parcourt domicile/travail, 9km de bonheur dans les montagnes de Martinique!!!

Vins Cenzo

Petit retour d'info : je n'ai pas réussit à utiliser une conversion de Karting, aucun n'a fonctionné, soit le jeu plante au chargement du circuit avec volant qui part d'un côté et reste bloqué, soit le Kart reste bloqué sur le circuit (un circuit de Kart créé qui fonctionne avec les voitures ACE) comme s'il touchait le bitume).

Marcin Czepiela

Great work on the latest update! 😃 It's awesome that we can now generate such large areas, and the road generation in hilly and mountainous terrain is so much better than before! I have a few questions about the future development of EvoForge: 1. Why is the map size limited by radius rather than total area? When creating long, narrow routes, an area-based limit would offer much more flexibility. 2. Are you planning to introduce a way to gradually expand existing maps by adding new areas? It would be amazing to keep expanding a single map instead of having to create a new one every time we want to cover more terrain. 3. How much RAM would you recommend for generating the largest possible map with a 10 km diameter (5 km radius)? Would 32 GB be enough, or would 64 GB be a better choice? Thanks for all your hard work and for continuously improving EvoForge! 😊

EvoForge - Jésus Triste

Thanks! Glad the mountain roads feel better. 1. Radius vs area. The radius isn't really what limits the map. The real limit is the content: about 16 million triangles. That's what a 2.5 km area in the centre of Lyon weighs, and it runs at around 77 fps in game. A light area like countryside or mountains can go up to 5 km. A dense town stops earlier: Annecy asked at 4 km came out at 3.35 km. The wizard shows the estimate before you build. For long, narrow routes, the import wizard already has Shape of the area → Drawn outline. Only what's inside your outline gets built: streets, buildings, trees and street furniture. There are two limits for now. The outline has to fit inside a 5 km radius circle, and the ground (relief and satellite imagery) still covers that whole circle. So a route longer than about 10 km end to end doesn't fit in one area yet. A footprint that follows the route instead of a circle is a good idea, and I'm noting it. 2. Expanding an existing map. Not yet: an area is built in one go. Adding a neighbouring area means joining the terrain and the roads, and keeping the edits you already made. It's on my list, but I can't give you a date. 3. RAM. The biggest areas I measured used about 4 to 5 GB while building. A 5 km area in the Vercors took 4.1 GB, and Annecy at 3.35 km took 5 GB. The finished track is 2 to 3 GB. 32 GB is plenty. 64 GB won't get you a bigger map, because the limit is the triangle budget, not memory.