Here is 70126-main results, but unfortunately at least cracks have different location so it's no longer 100% the same planet. I suppose using older version will increase difference between planets even more so there no reason to benchmark it. So memory usage is 250MB higher than in current stable version (600MB higher than PTE), but lower than few versions ago. Thought it's might be useless testing because planets aren't completely the same. Guys who have 4GB do not play on planets that using 4GB. They likely stick to something that use less than 2.5GB or even less so basically improvement for them would be 50-100MB at best. Fact that improvements are here is great, but as long as UI using 1.5GB RAM it's doesn't make sense for such low-level PCs.
Can I request for someone to try to change their Display Name in-game with the PTE build? I just want to make sure it's working outside of the office
I give it a try. one second. Edit: The change button could use a "thse are not alloed characters" hint. Tried to set a name with space, the button kept being enabeled and nothing happened
It is still a bit buggy: If I start via the uber launcher display name seems to be reset to Account name. Every time. If I start the steam version a previously set Display Name is kept, wheter it was set in the steam version or the Uber launcher version.
Got a minor pathfinding issues in a game: Units produced by teh advanced factory where unable to move into the teleporter. I could manually set them to enter the teleporter, but they would just stop outside the factory if I gave it the "send build to teleporter" order. It might be that the order did not "stick" with the factory, but have forgotten to look. So in parts I just manually controlled the units/set them to a rally point at the teleporter enterance. Lobby ID: 11137772352121087766
I noticed the ocassional LOD texture bug (LOD being used when I could clearly see it being LOD texture because I was way too close to overlook it). Nothing to write on this thread about. But with this planet I seem to have hit the "mother load" of all LoD bugs. They were everywhere. So just the right planet for debuging. Lobby ID: 687994340653082742 Settings: Some example pictures: Dxdiag attached.
Basically this color is not LOD textures, but likely completely missing texture. Can you please clarify are you running game on Nvidia GPU or Intel one? If it's Intel then one related task that might cause this for you: PA#3802 Code: Display Memory: 1792 MB Dedicated Memory: 0 MB Shared Memory: 1792 MB It's looks like when someone try to set non-standard settings for Intel graphics in BIOS it's usually end-up with glitches like you have.
Depends. Is the feature going by Programm name only or complete path? The UI implies programm name only, but I am not 100% certain. The programm pa.exe was automatically set to be run on the better Nvidia Graphics card.
You can check what GPU was in use by opening few recent log files in this directory: C:\Users\%USERNAME%\AppData\Local\Uber Entertainment\Planetary Annihilation\log\ You'll see something like that: Code: [01:13:31.918] INFO OpenGL Vendor: Intel Open Source Technology Center [01:13:31.918] INFO OpenGL Renderer: Mesa DRI Intel(R) Haswell Desktop [01:13:31.918] INFO OpenGL Version: 3.3 (Core Profile) Mesa 10.4.0-devel (git-504f5f9 2014-09-04 trusty-oibaf-ppa) [01:13:31.918] INFO OpenGL Shader Language Version: 3.30 [01:13:31.918] INFO Vendor flag set to Intel.
Got this: "[23:18:37.218] INFO OpenGL Vendor: NVIDIA Corporation [23:18:37.218] INFO OpenGL Renderer: GeForce GTX 765M/PCIe/SSE2" So I guess it was the Nvidia one. FYI, %userprofile%\AppData\Local\Uber Entertainment\Planetary Annihilation\log\ is a slightly shorter and more adaptable path to the profile folder
Let's say fair I post this path in instruction without even thinking about using any macro there because most of players I ask to provide logs likely would manually open this path directory by directory and I doubt anyone of them know there is way to use such paths like you posted.
