that bugfix sounds overdue. Good job whatever pace keeps going is welcome

I was hoping that it would somehow fix my ATI shader problems too, but of course it doesn't. The new autopilot, however, made the download well worth it. 😀

Well, can't fix what we don't know of 😉 so make bug reports with hardware specs.

Of course it's possible your gpu is just *that* old.

Yeah, it's exactly *that* old. 😉 I posted about this a year or so ago. Radeon 9550, Asus a7n8x, Athlon 2500+. It's supposed to do shader 2.0. Oh well, I'll get a newer one eventually. It's probably not worth worrying about.

15 December - a3cdb9f

Two nice additions in the latest nightly:

Multisampled antialiasing

If your card can cope, multisampled antialising is now enabled. Removes the jaggies from most things drawn in the game. Before:

After:

By default its set to 2x. You can change this by setting the "AntiAliasingMode" option in config.ini to 0 (off), 2, 4, 8 or 16, or by using you graphics driver config to override.

Dock targeting

If you have docking clearance, the target square will now appear attached to the port you're cleared for. This makes manual landings much easier:

I like the target square manual landings can be fun

Hello,

It seems the bulletin boards are not working (empty) in the latest nightly builds.

Please fix this issue. Thank you in advance.

Press high time acceleration while docked and it should populate the board in-time.

Top tip robn, thanks for that. Now running in 16 AA mode and very nice I must say! 😎

A fairly major refactor landed in the last nightly, and its almost certainly the cause of the problems. I'll start doing some testing on a couple of other machines I have here and see what I can come up with.

If you can, could you please test with various options - with and without shaders and/or HDR, with antialiasing at 0, 2, 4, 8 and 16, and so on. I'll be doing the same set of tests here. Hopefully we can pin it down.

I've tested the following combinations:

[*:2nq317as]AntiAliasingMode=0, HDR disabled

[*:2nq317as]AntiAliasingMode=0, HDR enabled

[*:2nq317as]AntiAliasingMode=2, HDR disabled

[*:2nq317as]AntiAliasingMode=2, HDR enabled

Linux/Nvidia and Windows/VMware worked correctly for me.

I got my brother to test on a low-end Windows/Intel box. It failed on 2xAA+HDR, showing a blank 3D region (ie no intro ship or starfield, just the menu). No AA + HDR was not even an option - Pioneer wouldn't switch to HDR. This particular machine had very little graphics memory so that might be right, but it might point to an unrelated quirk in our feature detection.

I did try on a Linux/Radeon machine, but its an old R300 and the official AMD drivers no longer have support for them. With the free drivers HDR refused to work regardless of AA mode. That could be a driver deficiency, and isn't something I can address right now.

When you post the results of your test, please also post your opengl.txt (in your Pioneer dir) and link to it. Once I have your results I'll write this up into an issue.

I've logged issue #901 to track this. If you have hardware/software combos that aren't covered in that issue, it'd be great if you could do the tests and report the results. Please also post your opengl.txt.

Ok, we believe we have a fix. A build will appear in a few hours with the fix. I'll post when its up so people can try. Thanks for the feedback!

Build d664a5f has just been uploaded. Crash on OS X and glitches on Linux/Radeon confirmed fixed. I'm yet to test Windows/Intel but I expect it to be fine. Let us know if you see any further problems, and thanks for the report!

still updating the nightly builds ? ive got the twitter feed as well

If you do get the twitter feed then you know there's an update every few days.

The latest build has something fun:

Or you could wait for alpha 21, which will be released on 13 April 😉

Confirmed. I'll be working on a fix this morning.

Ok, problem has been found. It also affects OS X and probably MSVC Windows builds as well. Its a simple problem with a few hairy knock-on effects, so its taken longer than I hoped to fix it. I'm at work now so I'll finish it off on my commute home. Once its pushed and a new build is available I'll post here.

All fixed: https://twitter.com/#!/pioneerspacesim/ ... 9568074752

Also includes your Spanish translation updates. Cheers 🙂

Can I ask what the filenames mean for the nightly release ? Every release there are different codes of numbers and letters. Please forgive me if this was answered I could not find posts that answered it.

Cheers.

Simply, it's the short hash of the git-commit that the binary was built at.

So when you say 'my version of pioneer is broken, and the filename is d7832e5' then we know exactly at what point of the repository that binary was built with.

And if you lose the filename, its also shown in the bottom-right corner of the menu screen.

Cheers Robn thanks for that.

Please open your user dir (My Docs/Pioneer) and delete the model_cache folder. We're in the middle of some changes that have made the old cache incompatible. Deleting it will cause it to be rebuilt, which has solved most of the problems people have come up with in the last week or two.

Alpha 21 won't have to do this, fyi.