[ian-reeds-games] Re: Tactical Battle 1.12 dev 1
- From: Austen Perry <austentheaxewielder@xxxxxxxxx>
- To: ian-reeds-games@xxxxxxxxxxxxx
- Date: Sun, 20 Jan 2013 11:22:15 -0600
nice updates.
for some reason, i get this error when starting the game.
---------------------------
---------------------------
An error has occurred. Please notify the game creator of this error.
You can copy the entire error to your clipboard by pressing control +
C. Then you can paste it into an email by pressing control + V and
send the email to support@xxxxxxxxxxxxxxxxxxx.
System.IO.FileLoadException: Could not load file or assembly
'Noesis.Javascript, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=ae36d046c7f89f85' or one of its dependencies. The
application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log or use the
command-line sxstrace.exe tool for more detail. (Exception from
HRESULT: 0x800736B1)
File name: 'Noesis.Javascript, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=ae36d046c7f89f85' --->
System.Runtime.InteropServices.COMException (0x800736B1): The
application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log or use the
command-line sxstrace.exe tool for more detail. (Exception from
HRESULT: 0x800736B1)
at Game.JS.Initialize(Dictionary`2 scriptStorage)
at Game.World.Initialize() in
C:\Data\Recent\TacticalRPG\TacticalRPG\World.cs:line 74
at Game.Form1.Form1_Load(Object sender, EventArgs e) in
C:\Data\Recent\TacticalRPG\TacticalRPG\Form1.cs:line 73
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
msg, IntPtr wparam, IntPtr lparam)
---------------------------
OK
---------------------------
stinks lol wanted to try out chance.
austen
On 1/20/13, Zak Claassen <zak.claassen@xxxxxxxxx> wrote:
> Downloading it now, can't wait to try it out. I like that sound
> naming idea; so when random sounds come in, if you put numbers at the
> end of a sound name it will pick a random one, for example if you have
> attack1, attack2, attack 3 and attack4 it would pick one of those
> four, but if you only had attack 1 and 2 it would only pick between
> those two, or will there have to be a fixed number of random sounds,
> like three for each?
>
> On 1/20/13, Ian Reed <support@xxxxxxxxxxxxxxxxxxx> wrote:
>> Hey Allan,
>>
>> Thanks for the positive feedback. I'm really glad you like the
>> feature. I wasn't sure exactly what to do on the wording but decided it
>> wasn't as important as getting the basic chance flag out.
>>
>> You're totally right about the different sounds. I meant to get some
>> feedback on that and forgot.
>>
>> It breaks down into 2 things, 1 is the type of sound and the other is
>> numbering them so you can get a random one.
>> For instance a successful attack could have 3 different sounds and one
>> is randomly played each time.
>> And a failed attack could have it's own 3 sounds of a sword slicing
>> through empty air or being blocked.
>>
>> Here's what Craig had suggested about sound types:
>> Craig said: Regarding random sounds, I remember it was suggested before.
>> But regarding having sounds for hits, misses and critical and such,
>> maybe the sound naming scheme should be something more like:
>> * unit_skill_success
>> * unit_skill_fail
>> * unit_skill_critical
>>
>> I say: I think since we are already using warrior_attack.wav or just
>> attack.wav this should be the successful version since that's how it
>> currently works.
>> So then if you wanted a failing sound it would be warrior_attackfail.wav
>> or attack_fail.wav as Craig suggested.
>>
>> And the randomized sounds based on number suffixes would be separate
>> though maybe I can do that soon as well.
>>
>> Not sure how the critical will work exactly, but we're not there yet
>> anyway.
>>
>> Well, now that I've written it I think that will work out pretty well.
>>
>> Does anyone like or dislike the attack_fail.wav and
>> warrior_attack_fail.wav sound naming?
>>
>> Ian Reed
>>
>>
>>
>
>
Other related posts:
