Topic: Widelands Dev builds terminated by Runtime under Win7ProSP1 and 8.1
chuckw Topic Opener |
Posted at: 2015-01-20, 01:34
Build 18 runs the game with no problem. Encountering problem on ALL of my Windows boxes. Do not have any Linux boxes handy to try. Neither 32bit nor 64bit development builds will get me to the playing board. Error occurs when "New Game" is selected under Single Player. I can get as far as "Begin Network Game" under multiplayer, but encounter error message when clicking on start a new game. No *err.txt files generated. I've renamed my original .widelands folder, but problem persists. BelArc Advisor reports Visual C++ 2010 x86 Redistributable 10.0.40219 What should I do? I see little people. Top Quote |
wl-zocker |
Posted at: 2015-01-20, 13:53
r7360 works fine for me on Win7. You can get output files when starting Widelands in the command line, using "Only few people know how much one has to know in order to know how little one knows." - Werner Heisenberg Top Quote |
chuckw Topic Opener |
Posted at: 2015-01-20, 14:49
Thanks! I'll give it a try. I'm sure that mine is an isolated case that likely has to do with something other than WL. I see little people. Top Quote |
chuckw Topic Opener |
Posted at: 2015-01-20, 15:26
I have now have files. stderr.txt is empty. stdout.txt:
Looks to me like I have some deprecated settings somewhere. Where should I look? I see little people. Top Quote |
Tino |
Posted at: 2015-01-20, 15:45
Both the 32- and 64-bit version on my page are compiled with MinGW, so there should be no dependency to a (specific version of) VC Redistributable. If you have renamed your folder <Userhome>/.widelands there should be no side effects with old config, because widelands generates a new one. Not sure what is happening here. The soundhandler messages are ok, because my packages don't contain the music... Top Quote |
chuckw Topic Opener |
Posted at: 2015-01-20, 16:03
I found the keys referenced in ~.widelands\config along with the line stating the file had been dynamically created by Build 18. I renamed that config file and ran rev7360 32bit. Same error encountered. stderr.txt is empty. stdout.txt:
I now have no clue. Suggestions? Edited: 2015-01-20, 16:12
I see little people. Top Quote |
simplypeachy |
Posted at: 2015-01-20, 20:55
Is the M: drive some sort of network path, symbolic link, substituted drive letter, or other unusual path? Are you running any security software which may be inspecting/mangling the process? Do you have any Windows Updates (incl. "Optional" Updates) waiting to be installed? Are there any other instances of programs crashing if you press Win key, type "problem reports", and click "View all problem reports"? Have you had any other unusual behaviour or crashes with other software? WARNING: New-style view packet not found. There may be strange effects regarding unseen areas. |
simplypeachy |
Posted at: 2015-01-20, 21:08
Using build 7360 64-bit without a .widelands profile directory, the game works fine here. Make sure that, rather than just renaming your Widelands config file, you rename the whole directory. It's possible that a corrupted save/reply/map could be causing a problem. Edited: 2015-01-20, 21:09
WARNING: New-style view packet not found. There may be strange effects regarding unseen areas. |
chuckw Topic Opener |
Posted at: 2015-01-20, 21:17
M: is a physical HD in the same case. (My OS is on an SSD.)
Possibly, though I've had no problems with it in the past.
All are up to date.
No other programs are demonstrating problems. There is a Problem Report for Widelands from today with a Status of "Not reported"
No. Thanks for your attention to this. I see little people. Top Quote |
chuckw Topic Opener |
Posted at: 2015-01-20, 21:18
I've done that, but will try again and report back. I see little people. Top Quote |