Polyworks 2.0 - testing

[Anna]

I'm releasing an early version of PW2 for testing. So far I've (partially) re-implemented the move, select, create, and vertex colour tools.

Download (requires the .NET Framework 2.0, DirectX October release or later)

For now it must be extracted to your Soldat folder.

People have reported slow initial loading times, so don't be surprised if it takes more than a few seconds to start. The main thing I'm interested in is if it actually runs. Any feedback on the new interface is welcome as well (even though most of it is disabled at the moment).

[Mr. Domino]

I have .NET Framework 3.0 installed on this PC, and it crashes when I attempt to launch it. I know you say it's for 2.0 in your post, but I thought I'd mention it for any who upgraded.

[VirtualTT]

.NET Framework 1.1; 2; 3 are installed separately and are not updates to each other...

[Anna]

I forgot to mention this: you also need DirectX from October 2006 or later.

[Mr. Domino]

.NET Framework 1.1; 2; 3 are installed separately and are not updates to each other...

It any case, it's not working. All I know of .NET is that it's Microsoft's answer to Java. That's all I care to know about it.

[VirtualTT]

1. It's working
2. Just install .NET framework 2 and fresh DirectX...
3. .NET is not Microsoft's answer to Java 

[Mr. Domino]

2. Just install .NET framework 2 and fresh DirectX...

I already have it installed:

v1.0.3705
1.0 Hotfix (KB886906)
1.1
2.0
3.0

[VirtualTT]

and what exactly happens when you try to run it?

[iDante]

ummm... will you ever make an os x version?

[jrgp]

I got it working on my pc. Had to grab .net framework 2. I got it here.

The new interface is a lot easier to use and looks cleaner, but it also looks a little bit to microsoftish. The menu's remind me of the ones in Word 2003.

I like the new scroll wheel, how you can zoom in where the cursor is pointing at the specific moment and not have to click there first.

All in all I like it a lot. I just hope the main release of polyworks 2 doesn't require .net 2 framework because I want to upgrade back to  3.

[ramirez]

All in all I like it a lot. I just hope the main release of polyworks 2 doesn't require .net 2 framework because I want to upgrade back to  3.

You can have multiple versions of .NET installed at the same time. When you start an application that requires .NET it detects the best available version installed, and uses that. For example .NET 1.1 apps run on .NET 2.0 even if 1.1 isn't installed. But if 1.1 is installed it's used for apps compiled for .NET 1.1, even if .NET 2.0 is installed as well. I haven't tried .NET 3.0 myself yet, but I doubt it changes anything in the way .NET versioning works.

.NET Framework 1.1; 2; 3 are installed separately and are not updates to each other...

Like I previously stated, they're still backward compatible with each other. Well not sure about if 3 is backward compatible with 2.0 and/or 1.1, but at least 2.0 is backward compatible with 1.1 (there are some things that may not work due to certain changes in the framework, but basically 95% of 1.1 apps should run fine on 2.0 only system).

Anyways I'm installing latest DirectX so I can try this. I'll edit details later.

[FliesLikeABrick]

ummm... will you ever make an os x version?

As far as I know, .NET programs are windows-only.  Same for the fact that it requires DirectX.

[ramirez]

Well there's Mono framework for Mac Os X that can be used to run .NET apps, but I doubt it works with managed DirectX, unfortunately.
Anyway I tried it and it loads pretty fast for me and runs smoothly as well.

[FliesLikeABrick]

Spam by EnEsCe deleted

[Keron Cyst]

Functions for me. Great work so far! Alt highlights File in selection subtraction, so perhaps subtraction should be handled through a different key (Z?), or its ability to select File should be disabled.

[Anna]

Thanks guys, the next version will hopefully be complete enough to actually be used for mapping.

I really want to fix those small annoying issues in the old PW like the keyboard and mouse focus not working correctly all the time, keyboard shortcuts not behaving like they should, etc. I'm probably going to make a customized menu bar control to fix the alt highlighting menu problem, and to enable click-through. C# and Windows Forms are great to work with, especially compared to how it was in VB6. Also I have some more tool function related ideas that should be interesting.

[Thomas]

It doesn't start...
(Yes, i have .net 2.0 and DX9c installed)
You could let it crate a debug log.

[Trank]

Tested on vista => works perfect here!

[ElephantHunter]

I thought I had the latest version of DirectX on Vista (since Vista officially came out after October), but apparently that is not the case. Those of you having problems on when Polyworks 2 starts should download the October DirectX Redistributable.

After installing the latest version of DirectX I had no issues.

[iDante]

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.

[chrisgbk]

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

[EnEsCe]

My comment was about .NET being lame, not VB. VB was good.

[DorkeyDear]

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?

[stryke]

i can't open maos!!!
wtf?

[iDante]

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?

[Anna]

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.

[chrisgbk]

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. 

[stryke]

sorry i would write: i can't open "maps".

thats the error: http://img263.imageshack.us/img263/2041/problempwgr3.png

[Laser Guy]

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??