I don't understand what these error messages mean, but reading that first line it says "WindowsBase, Version=3.0.0.0". It is entirely possible that this is referring to the .Net platform. There have been a couple of other people who have recently posted error messages that were caused by .Net- - or should I say by them not having the correct version.

The latest version of Supremacy has updated installation requirements - you MUST have .Net 3.5 Service Pack 1 Beta installed before Supremacy will play. Did you update .Net before you tried playing the game? These updated requirements were explained in the download post, so please try to read them if we ever post an update in the future.

If you haven't installed the update, you can find the download that you need

If you did update .Net though or installing the above update didn't work, you'll need to wait and see what Mike says about the error report, sorry.

Hi

I loved the original BOTF, and I got really excited to discover you are working on a BOTF2 - Great job!

I downloaded and installed .NET framework 3.5 SP1 - NOT the beta! I kinda hoped this would not cause any issues.... however....

Could not load type 'System.Windows.NameScope' from assembly 'WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

at Supremacy.UI.Star2D..ctor(StarType starType)
at Supremacy.UI.StarSystemPanel.DisplayVisuals(StarSystem system) in C:\Users\Mike Strobel\Workspace\supremacy\Mainline\SupremacyUI\StarSystemPanel.cs:line 289
at Supremacy.UI.StarSystemPanel.Refresh() in C:\Users\Mike Strobel\Workspace\supremacy\Mainline\SupremacyUI\StarSystemPanel.cs:line 195
at Supremacy.UI.StarSystemPanel.SectorChangedCallback(DependencyObject source, DependencyPropertyChangedEventArgs e) in C:\Users\Mike Strobel\Workspace\supremacy\Mainline\SupremacyUI\StarSystemPanel.cs:line 131
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, OperationType operationType)
at System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp)
at System.Windows.Data.BindingExpression.Invalidate(Boolean isASubPropertyChange)
at System.Windows.Data.BindingExpression.TransferValue(Object newValue, Boolean isASubPropertyChange)
at System.Windows.Data.BindingExpression.Activate(Object item)
at System.Windows.Data.BindingExpression.AttachToContext(AttachAttempt attempt)
at System.Windows.Data.BindingExpression.MS.Internal.Data.IDataBindEngineClient.AttachToContext(Boolean lastChance)
at MS.Internal.Data.DataBindEngine.Task.Run(Boolean lastChance)
at MS.Internal.Data.DataBindEngine.Run(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)


The infamous NameScope issue is here for me

According to add/remove software the framework is installed correctly.
I am running Vista home premium - fully patched etc, tho ofc being the .net framework it should not
matter which recent OS it runs on

Please can you advise how I can resolve this - I have itchy fingers to play the game!

All the best,
Chris

you need the beta.

Thanks for the replies!

OK I'll hang in there a little longer by playing BOTE, and I'll check back regularly to see when you have had the chance to patch it

Thanks again and keep up the great work!

All the best.

Chris