Work on this project is still undergoing, been working on the hairpins a lot more to smooth them out.Irohazaka Ver 3 will be released soon. Ver 3 will be both Uphill and early downhill together.
Thank you, yea it takes a lot of patience to get it as close as possible, and I still know I can actually make it better.
I got a problem downloading it... I can't type the captcha in, an error occurs everytime (I reloaded it multiple times... doesn't work at all). Is there another way downloading it?
I watched/skimmed the video; this project looks pretty cool! Normally I don't think that zones & portals could be used on an outdoor track to improve performance without causing terrible problems. In this case since visibility is often limited, maybe they could be used? I'll give the map a try ASAP. Zones is probably not practical, but I think it could be interesting to try.
Dammit! Why doesn't it work when I download it That's what it looks like when I'm trying it (reloaded 5 times before):
One important thing I noticed is that all (?) the guardrails in this map lack end treatments. When driving in this map, as things are now, a gentle tap against the end of a guardrail can put the guardrail inextricably into the car sometimes. I think that this may be related to how thin the guardrail is and I'm confident that end treatments would help. (The few guardrails that are in official maps include end treatments.) EDIT: Here's a picture a turn in real life with end treatment visible if you download the full-sized picture and zoom in all the way: http://s1089.photobucket.com/user/Chigo4/media/Japan tour/DSC02021_zps97262faa.jpg.html EDIT 2: The guardrails on Iora1 seem to be at a good/typical height. The guardrails on Ihrohazaka2 are very high in the air, my car slips under them and hits the posts. Is this realistic or a mistake? EDIT 3: This article shows a good selection of end treatments - http://www.crashforensics.com/papers.cfm?PaperID=53
OK, I've made some changes to the *.mis file: Implemented some zones to get things started. Based on some (very) quick comparisons I think they should help with the worst areas, at least on Iora1. There are 5 zones: 2 separate zones are on Iora1 (eg the downhill section). There is a large portal connecting them which should be large enough to prevent any blinking/blanking/bad-stuff. 3 other zones are in a zone group and together they cover Irohazaka2 (eg the uphill section). The second zone in Iora1 connects to the first zone in the Irohazaka2 zone group using a very large portal. I make no guarantees that any of this is done correctly. I'm especially unsure about using a giant portal like that. Deleted the *.ter from the *.mis - it wasn't doing anything useful. Rotated the Spawn Sphere to face downhill. It could use some more careful tweaking before a final release, but for now there is plenty of more important work to do with those huge dae objects.
Iroa 2 was a old project I had for rFactor and lost all origi al BTB files so the guardrails there would ether stay the way they are, (and I do know there to high, something I wasent proud off) or I can completely remove them and add some from beamng, but that would take insane time.the guardrails on iroa 1 are getting a redo with ends and everything. at the moment I am at work, but I am reading everything you are saying about zones and all that, what is it exactly that you mean by zones? Is this my fps issue, or something that I should change that you think will benefit from fps? EDIT: by the way thank you for helping me
Ok, tried it in tears with Internet Explorer cause I was too lazy to download Chrome... I worked Thanks for the help
You are welcome. Zones are a performance optimization system for T3D (the engine that BeamNG.drive uses for most things besides the physics). They help the engine cull things which are outside of your current zone (other than what you can see through any relevant portals). Using giant (monolithic) DAE files seems to prevent everything from being culled, so if possible it might be best to slice up the DAE(s) a little bit. Most outdoor environments in BeamNG make using zones impractical, but yours is unique because visibility is so limited. Partitioning off 3 separate areas using zones and portals wasn't too bad. With a realignment of Iroa 2 you could probably optimize a little more. Take a look at the *.mis file I provided in your level. Look at your Scene Tree and examine the zones and portals. It might be easiest to highlight all of the zones and portals at once so that you can see how they touch each other or do not touch each other. For more information on zones take a look at: Marcus L's reply here - https://www.garagegames.com/community/forums/viewthread/124138 Portal Class Reference (scroll down to Detailed Description) - http://docs.garagegames.com/torque-3d/reference/classPortal.html Zone Class Reference (scroll down to Detailed Description) - http://docs.garagegames.com/torque-3d/reference/classZone.html I'm just asking about it, but for Iroa 2 couldn't you remove the guardrails and then create a second object in your 3D modeling environment which only contained guardrails? (eg similar to the work you'll be doing in Iora 1)
