There's some DATA resources now that 0.3a cannot read, which I successfully had exported shortly before the patch. 545AC67A_00BBD738_0DEFE533D4820159 would be one of them. The error I get is
Error reading resource 0x545AC67A-0x00BBD738-0x0DEFE533D4820159
Front-end Distribution: 14-0920-48
Library Distribution: 14-1116-502
Source: mscorlib
Assembly: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Exception has been thrown by the target of an invocation.
----
Stack trace:
at System.RuntimeMethodHandle._InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct& signature, RuntimeType declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct signature, RuntimeType declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.ConstructorInfo.Invoke(Object[] parameters)
at s4pi.WrapperDealer.WrapperDealer.WrapperForType(String type, Int32 APIversion, Stream s)
at s4pi.WrapperDealer.WrapperDealer.GetResource(Int32 APIversion, IPackage pkg, IResourceIndexEntry rie, Boolean AlwaysDefault)
at S4PIDemoFE.MainForm.browserWidget1_SelectedResourceChanged(Object sender, ResourceChangedEventArgs e)
----
Source: mscorlib
Assembly: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Unable to read beyond the end of the stream.
----
Stack trace:
at System.IO.BinaryReader.FillBuffer(Int32 numBytes)
at System.IO.BinaryReader.ReadUInt32()
at s4pi.DataResource.DataResource.Parse(Stream s)
at s4pi.DataResource.DataResource..ctor(Int32 APIversion, Stream s)
----
Happens with the 0.3a I was using as well as with a freshly redownloaded one; both can handle the pre-patch version just fine.
There's some DATA resources now that 0.3a cannot read, which I successfully had exported shortly before the patch. 545AC67A_00BBD738_0DEFE533D4820159 would be one of them. The error I get is
Happens with the 0.3a I was using as well as with a freshly redownloaded one; both can handle the pre-patch version just fine.