Create account / Log in

Roadmap for VASSAL 4

Discussion area for the development team.

Moderators: Tim M, uckelman

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby uckelman » May 30th, 2011, 8:45 am

Thus spake lancel:
> I did a quick test on my Ubuntu 64-bit but when executing test, I got an
> error "cannot execute binary file".

I didn't expect the Linux build to work. It's compiled on Fedora, so
it's most likely linked against different versions of the libraries.

> On the Windows 7 64-bit, it is the
> same "the application was unable to start correctly..." I think you
> have all the dlls this time but somehow I think one or some of the dlls
> are not compatible with W7 and/or Vista.

This just baffles me.

Can I get the complete text of the error messsage again? I'm going to
ask in the #fedora-mingw IRC channel about this.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8147
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Roadmap for VASSAL 4

Postby Rindis » May 31st, 2011, 5:25 pm

Just tried it on the WinXP machine at work. When I run test.exe I see a console come up, then a window opens, and then it all disappears. No error, nothing. It just vanishes.
User avatar
Rindis
 
Posts: 196
Joined: December 22nd, 2007, 12:49 am

Re: Roadmap for VASSAL 4

Postby lancel » June 1st, 2011, 8:35 pm

Joel,
The error message is:

The application fails to initialize properly (0xc0000142). Click OK to close the application.

Lance
lancel
 
Posts: 93
Joined: August 30th, 2010, 3:47 pm
Location: NY, NY

Re: Roadmap for VASSAL 4

Postby lancel » June 1st, 2011, 8:52 pm

Joel,
I found out what the problem is. I replaced the glew32.dll and glew32mx.dll in your package with the ones I took from SourceForge site and after that, I have no problem running test.exe.

Lance
lancel
 
Posts: 93
Joined: August 30th, 2010, 3:47 pm
Location: NY, NY

Re: Roadmap for VASSAL 4

Postby lancel » June 1st, 2011, 9:05 pm

Rindis,
I have no problem running Joel's package on my WinXP laptop. I think your XP's OpenGL version may be a bit out-of-dated. You may want to download the glew package from this SourceForge site: http://sourceforge.net/projects/glew/fi ... p/download.

Unzip it and then run the file called "glewinfo.exe" in the package. You can then see which version of OpenGL libraries you have on your machine by inspecting the resulting glewinfo.txt file.

Lance
lancel
 
Posts: 93
Joined: August 30th, 2010, 3:47 pm
Location: NY, NY

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby uckelman » June 1st, 2011, 9:50 pm

Thus spake lancel:
> Joel,
> I found out what the problem is. I replaced the glew32.dll and
> glew32mx.dll in your package with the ones I took from SourceForge site
> and after that, I have no problem running test.exe.
>
> Lance
>

That's great news! I'd still like to understand why the DLLs I build
don't work, though. I uploaded two new ones, built with a slightly
newer MinGW setup, here:

http://www.vassalengine.org/~uckelman/v4-demo/

Do they work?

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8147
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby Brent Easton » June 1st, 2011, 10:09 pm

Testing on 32bit Vista I had the same error. Downloaded the new glew libraries and I now get the error

terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct NULL is not valid

Running glewinfo tells me I have OpenGL Version 4.0, not 4.1 (latest). Updated my video drivers and now have OpenGL Version 4.1. Same error.



*********** REPLY SEPARATOR ***********

On 1/06/2011 at 2:05 PM lancel wrote:

>Rindis,
>I have no problem running Joel's package on my WinXP laptop. I think
>your XP's OpenGL version may be a bit out-of-dated. You may want to
>download the glew package from this SourceForge site:
>http://sourceforge.net/projects/glew/fi ... p/download[1].
>
>Unzip it and then run the file called "glewinfo.exe" in the package.
>You can then see which version of OpenGL libraries you have on your
>machine by inspecting the resulting glewinfo.txt file.
>
>Lance
>
>[1]
>http://sourceforge.net/projects/glew/fi ... p/download

____________________________________________________________
Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton@exemail.com.au
User avatar
Brent Easton
 
Posts: 2758
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby uckelman » June 1st, 2011, 10:19 pm

Thus spake "Brent Easton":
> Testing on 32bit Vista I had the same error. Downloaded the new glew librarie
> s and I now get the error
>
> terminate called after throwing an instance of 'std::logic_error' what(): bas
> ic_string::_S_construct NULL is not valid

This is because you didn't specify a map image on the command line,
and I'm not bothering to do any error checking because it's a demo.
Sorry.

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8147
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby Brent Easton » June 1st, 2011, 10:21 pm

>That's great news! I'd still like to understand why the DLLs I build
>don't work, though. I uploaded two new ones, built with a slightly
>newer MinGW setup, here:
>
>http://www.vassalengine.org/~uckelman/v4-demo/
>
>Do they work?

The old 'failed to initialise' problem on Vista
User avatar
Brent Easton
 
Posts: 2758
Joined: December 21st, 2007, 3:06 am
Location: Berry, NSW, Australia

Re: Roadmap for VASSAL 4

Postby lancel » June 3rd, 2011, 5:26 pm

I have the same problem with Win7 as well. My current guess is that the native Win32API libaries used to link with the glew dll files on the MinGW may be a bit out-of-dated. That may explain why it fails only on Vista or newer version of Windows.

I have no problem building the glew32 files using the source code downloaded from SourceForge with VS 2008 C++ Express and those dll files can be loaded by the test.exe on my Win7 without any problems.

Lance
lancel
 
Posts: 93
Joined: August 30th, 2010, 3:47 pm
Location: NY, NY

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby uckelman » June 3rd, 2011, 5:47 pm

Thus spake lancel:
> I have the same problem with Win7 as well. My current guess is that the
> native Win32API libaries used to link with the glew dll files on the
> MinGW may be a bit out-of-dated. That may explain why it fails only on
> Vista or newer version of Windows.

I doubt it's that---the Win32API libs which I linked GLEW against are
the same ones that all of the other DLLs you're using are linked against.

> I have no problem building the glew32 files using the source code
> downloaded from SourceForge with VS 2008 C++ Express and those dll files
> can be loaded by the test.exe on my Win7 without any problems.

I'm in the middle of working through the problem with someone from the
#fedora-mingw IRC channel now. We'll see where that goes.

BTW, the code is available at SF now:

http://vassalengine.git.sourceforge.net ... ;a=summary

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8147
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Roadmap for VASSAL 4

Postby lancel » June 4th, 2011, 3:11 am

I compiled the code with VS C++ 2010 Express to see how it looks on my W7 netbook. The counters look good now on my W7 netbook. However, the map screen got an extra layer of white "canvas" that I can drag around inside the viewport. I eventually had to move that white layer all the way over to the top of the map before I could see the entire map since that white "canvas" is like a blanket. I wonder if you can see that too on your Linux boxes and if it is an artifact of building it with MS Visual Studio.

Lance
lancel
 
Posts: 93
Joined: August 30th, 2010, 3:47 pm
Location: NY, NY

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby uckelman » June 6th, 2011, 5:33 pm

Thus spake lancel:
> I compiled the code with VS C++ 2010 Express to see how it looks on my
> W7 netbook. The counters look good now on my W7 netbook. However, the
> map screen got an extra layer of white "canvas" that I can drag around
> inside the viewport. I eventually had to move that white layer all the
> way over to the top of the map before I could see the entire map since
> that white "canvas" is like a blanket. I wonder if you can see that too
> on your Linux boxes and if it is an artifact of building it with MS
> Visual Studio.
>
> Lance

No, I don't see that on Linux. What size is this object?

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8147
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: [messages] [Developers] Re: Roadmap for VASSAL 4

Postby uckelman » June 6th, 2011, 5:42 pm

Thus spake uckelman:
>
> I think what we need to do is ensure that all textures are made square
> and have their dimensions padded out to the next highest power of 2.
> I'll do that tomorrow, it should be easy.

The current version I've uploaded (0.0.0-d226f9f9) uses only power-of-
two-sized textures. If you're still seeing some map tiles or piece faces
as blank on any machine with this or later builds, please let me know.

Also, the GLEW libs I've included in the Windows build are the ones
distributed by the GLEW project, not ones I built, so you should not need
to replace them.

http://www.vassalengine.org/~uckelman/v4-demo/

--
J.
User avatar
uckelman
Site Admin
 
Posts: 8147
Joined: December 10th, 2007, 9:48 am
Location: Durham, England

Re: Roadmap for VASSAL 4

Postby LB » June 7th, 2011, 10:07 am

I gave the latest demo a try. Zooming (with mouse wheel and holding down middle mouse button), panning, rotating all worked perfectly for me.

All the previous demo versions failed. I'm on Windows 7.
LB
 
Posts: 60
Joined: July 23rd, 2010, 5:01 am

PreviousNext

Return to Developers

Who is online

Users browsing this forum: No registered users and 2 guests