Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cameni]

Can anything be done to remove the tear that occurs along the transitional area at the ends of a road since nothing beyond the ends gets aligned?  Aligning to terrain or manually aligning doesn't work in every situation.

Assign the lead-in marking to the first node, and lead-out to the node before the last one.

[cameni]

Just wondering if it was possible to add in a feature called, road quality ...

Yes, that's planned, but after other parts of the road system are reworked, allowing for a wider variety of road types. The wear could be also dynamic.

[lookastdu]

I would like to report a bug. 

So, after update 3053 I can't generate any road, the old roads aren't generating, but I can "click" them in road tool mode. However, I can't regenerate them, or generate any new road.
Except of that I can't flat the terrain under buildings.
It looks like that I can only view te original terrain and it can't be modified by anything.

Radeon 3870 + Catalyst 12.3, Phenom 9550, 6GB RAM

Should I try deleting cache maybe?

[cameni]

Did you try it in other parts of the world? I'm looking at the log but there's no error, and I'm not sure why it even crashed after multiple clicks.

[lookastdu]

Ok, so I tested on Oahu. The before parts were made on Usui, Japan.
But still the same.
However: I had made 4 part road (on Oahu) and I had camera at futher distance from terrain. The part 2 and 3 of road had generated, but 1 (beggining) and 4 (ending) not. And when I tried to close up camera, it disapperaed. When I moved back camera, the road has appeared again from farther distance.

I'm confused with this crash I had. I tried to crash again clicking even faster "Make" button, but this time nothing happened.

Edit: I recorded and converted it, I will upload video in few minutes.

Edit 2: video:

[cameni]

Hmm we don't have any 3xxx card here, but it's odd that it would stop working on these, when the change was actually a simplification ...

Please do the following: edit eng.cfg, set debug_mode = true, debug_async = false.
Then start, try to make some roads, and send me the eng.log

[lookastdu]

Here it is: http://www.gamefront.com/files/21505946/eng.log
Ofc Outerra ran in debug mode, as you wished.

Link to video in my previous post.

[cameni]

Nothing helpful in there
Can you install the previous version (Anteworld-0.7.11.2968.patch-3051.exe) and then run outerra.exe with -noupdate argument from the command line, to check again if it still works in that version? Just to see if it's not something else causing it.

[lookastdu]

Ok, I tested with 3051 and everything works absolutely correctly. I can see the roads I have made in build 3053 and before. I can add/edit etc. them. The terrain under buildings is also flattening.

To be sure I ran outerra without -noupdate argument and downloaded build 3053 again. The problem is still appearing, so it is rather problem with something that was changed after 3051.

I think I can try to completely uninstall Outerra, install 2982 (I still have installer on HDD ), update it, visit again Oahu and Usui and try to make some roads, place buildings etc.

[cameni]

I can see the issue on 4850 as well.

[lookastdu]

I reinstalled Outerra but nothing has changed (but you probably have read my crash report so far).

Do you know if build 3053 runs without problems on Radeon 5/6 series? Because I'm a little bit intrested if AMD screwed something up in drivers or what*...

Outerra runs on OpenGL, yes? So maybe after build 3051 you used in outerra source code some OpenGL extension that is not supported by 38xx/48xx graphics cards?
Of course I'm only guessing.

* - quite a long time ago when I was playing 18WoS Haulin after some drivers update I had to change graphics settings from high to medium, because game was crashing on new drivers. Game was running on OpenGL.

[cameni]

Yes, the problem appears only on 3/4 Radeons. I'm developing on 6850 where it works normally.

The problem is that I'm not aware of any change that would cause this

[Jagerbomber]

Can anything be done to remove the tear that occurs along the transitional area at the ends of a road since nothing beyond the ends gets aligned?  Aligning to terrain or manually aligning doesn't work in every situation.

Assign the lead-in marking to the first node, and lead-out to the node before the last one.

Oh... 

[Airhogg]

Has there been an update applied today?  I was flying earlier today and my framerate was liquid smooth, but I changed my location to a coastal region and my framerate became VERY choppy.  I re-booted and went back to my original location (no water nearby), but I'm still getting very choppy framerates.  Any ideas?
 

Update:  Nevermind.  I reverted my graphics settings back to default and all is well again.  I changed each setting, one by one, to see if any one in particular might have affected my peformance.  There was no change that I could tell.  All seems to be o.k. now.

[cameni]

Uploaded new version 0.7.11.3054 that (probably) fixes the issues with roads on ATI 4xxx and 3xxx cards. Please test if it resolves the issue for you.

I must say that this is one of the most absurd bugs I've ever encountered, that took me a couple of days to locate. Simply said, roads sometimes weren't rendered at all, or were rendered randomly only in some terrain tiles.
After a painful search I've narrowed it down to a single shader variable, and the fix consisted of giving it a name that works. The variable name can be (almost) arbitrary, but for some reason the GPU didn't render the roads if that particular variable was j6 or mare_1 or many other names, but it worked if the name was frcm_1. If it doesn't make any sense to you, you are not alone.

Understandably, it cannot be taken as a proper fix, just a workaround until the drivers are fixed.