Print

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

[Midviki]

Only bug report I have thus far is that my trees look flat and cardboardy

Good one!   

[SpaceFlight]

Only bug report I have thus far is that my trees look flat and cardboardy

Wouldn't it be awesome if Cameni and Angrypig had like 50-100 developers at their disposal, all knowing how to work with the early Outerra technology?
The 3D trees would be here in no time I guess 

[Krutan]

Will the next update be 0.7.17? Because it's been really quiet now for a couple of weeks

[Jagerbomber]

Yeah, when switching roads with the road window still open, for the start/end points on the newly selected road, the elevation value in the window stays the same as the last point selected on the previous road.  Only seems to be the start/end points (and maybe the 1 point adjacent to those).  The elevation value doesn't become the correct value that was set for those points when they are selected.

[Jagerbomber]

Is there anything that can be done to keep Outerra from crashing while having multiple Google services running? (In-game and out at the same time.  Usually maps.)  Other than, you know... closing them?

[cameni]

As far as I can tell from the crash reports, it's a memory problem. The browser running maps tends to use too much memory, and since it's running within the OT process that already takes a fair share, it can run out of virtual memory space.

A x64 build would help, but there seems to be a problem with the browser as well - it should just close itself instead of throwing a fatal error.

[Jagerbomber]

My W8 (64 bit, though I know Outerra isn't) says 8GB of virtual memory allocated...

Is whatever the problem is actually connected to using maps in Firefox as well?... or is it just the memory issue or something?  Or... is that just completely separate from using the in-game maps at the same time?  Doesn't seem separate to me because that's when it happens (as well as Google locking up in general).  When I'm using both.

[cameni]

Virtual memory is allocated per-process. If you think it's connected to other processes, then it may be a problem of the non-paged memory usage. It's used by drivers to allocate memory for communication with the GPU and other devices. Non-paged memory is a limited resource, and more apps using it can cause problems.

You can try to turn off GPU acceleration in Firefox. Also, with recent versions of Firefox (22-23) and with a Nvidia card I have experienced the Windows freezing hard several times, requiring reset, so I think there's definitely a problem with the GPU acceleration in there.

[Jagerbomber]

"Non-paged"... as in regular RAM or what?

I know I can't actually confirm that it's only with Google yet, but could it possibly a conflict/problem with Google servers/services (or something (API?)) locking up in this situation and not successfully sending me what I need to my one destination (computer) and multiple programs? idk... whatever.