Author Topic: Polyworks 2.0 - testing  (Read 8487 times)

0 Members and 1 Guest are viewing this topic.

Offline chrisgbk

  • Inactive Staff
  • Veteran
  • *****
  • Posts: 1739
Re: Polyworks 2.0 - testing
« Reply #20 on: March 28, 2007, 08:19:04 am »
As far as I know, .NET programs are windows-only.  Same for the fact that it requires DirectX.
Well, I know I am just wondering if anything involved with Soldat will ever be mac-ready. bah.

Spam by EnEsCe deleted
would this have been about how its made in visual basic?
cause if it was then i have to respond: It doesn't matter if the cat is black or white as long as it catches mice.

This version (2.0) isn't written in VB; it's written in C#.NET

Offline EnEsCe

  • Retired Soldat Developer
  • Flamebow Warrior
  • ******
  • Posts: 3101
  • http://enesce.com/
    • [eC] Official Website
Re: Polyworks 2.0 - testing
« Reply #21 on: March 28, 2007, 10:16:21 am »
My comment was about .NET being lame, not VB. VB was good.

Offline DorkeyDear

  • Veteran
  • *****
  • Posts: 1507
  • I also go by Curt or menturi
Re: Polyworks 2.0 - testing
« Reply #22 on: March 29, 2007, 11:59:34 am »
not to get off topic but this is probably the best place to ask atm
but what is a .NET Framework simply put? i never knew :(

I DLed the .NET Framework 2.0 and directx 9.0c but it seems to not work :(
i extracted it in 3 places.. i extraced the folder on desktop, soldat directory, and the subfiles into the soldat directory.. none work, all end up with the same thing, crashes b4 it even gets a chance to open :(

what version of DirectX is the october release?
« Last Edit: March 29, 2007, 12:19:15 pm by DorkeyDear »

Offline stryke

  • Major(1)
  • Posts: 13
Re: Polyworks 2.0 - testing
« Reply #23 on: April 24, 2007, 08:41:17 am »
i can't open maos!!!
wtf?

Offline iDante

  • Veteran
  • *****
  • Posts: 1967
Re: Polyworks 2.0 - testing
« Reply #24 on: April 24, 2007, 05:34:31 pm »
This version (2.0) isn't written in VB; it's written in C#.NET
My comment was about .NET being lame, not VB. VB was good.
Bah I am missing a lot of stuff these days... Getting old.

i can't open maos!!!
what happens when you try to open them?

Offline Anna

  • Soldier
  • **
  • Posts: 213
    • my dev blog
Re: Polyworks 2.0 - testing
« Reply #25 on: April 24, 2007, 08:16:25 pm »
I'm starting to have doubts that I'm ever going to finish this. Since I accomplished most of my goals for this project (PW interface redesign, cleaner program structure, learn C#) I've lost motivation to work on it. On top of that I have a lot of other stuff to work on. I'm considering releasing the source code but some of it is fairly complicated and mostly undocumented and I doubt anyone would be able to complete it in the way that I had in mind, so I'm undecided on that.

Offline chrisgbk

  • Inactive Staff
  • Veteran
  • *****
  • Posts: 1739
Re: Polyworks 2.0 - testing
« Reply #26 on: April 25, 2007, 04:25:04 am »
I wouldn't mind having a look at it, and I'm proficient enough to understand it; however I would probably end up joining you in the "lack of motivation" boat.  :P

Offline stryke

  • Major(1)
  • Posts: 13
Re: Polyworks 2.0 - testing
« Reply #27 on: April 25, 2007, 09:48:28 am »
sorry i would write: i can't open "maps".

thats the error: http://img263.imageshack.us/img263/2041/problempwgr3.png
« Last Edit: April 25, 2007, 09:51:40 am by stryke »

Offline Laser Guy

  • Veteran
  • *****
  • Posts: 1679
Re: Polyworks 2.0 - testing
« Reply #28 on: April 25, 2007, 10:38:51 am »
Quote
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at Polyworks.MapFileIO.LoadSceneryElements(BinaryReader br, List`1& elements, Device& device)
   at Polyworks.Map.LoadMap(Device& device, String fileName)
   at Polyworks.Polyworks2.OpenFileDialog_FileOk(Object sender, CancelEventArgs e)
   at System.Windows.Forms.FileDialog.OnFileOk(CancelEventArgs e)
   at System.Windows.Forms.FileDialog.DoFileOk(IntPtr lpOFN)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Polyworks
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Jakub%20the%20Master/Moje%20dokumenty/Soldat%20Polyworks%202.0/Polyworks.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.DirectX
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.DirectX/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.dll
----------------------------------------
Microsoft.DirectX.Direct3D
    Assembly Version: 1.0.2902.0
    Win32 Version: 9.05.132.0000
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.DirectX.Direct3D/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.Direct3D.dll
----------------------------------------
Microsoft.DirectX.Direct3DX
    Assembly Version: 1.0.2911.0
    Win32 Version: 9.12.589.0000
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.DirectX.Direct3DX/1.0.2911.0__31bf3856ad364e35/Microsoft.DirectX.Direct3DX.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



and what am i supposed to do with that??
Text goes here...