Messages

51

Closed bug reports / Re: r4021: Linux64 game host freezes after first command

« on: 4 February 2013, 08:26:51 »

i had the sudden closing by connecting to headless again yesterday with 4080. It happened two times one after each other. I saved the cache to try to reproduce this error.
Then I cleared the cache and there was no problem to connect to headless.

After that I restored the cache and tried to connect with the headless again. That worked with no problems.

Although clearing the cache seems to help if you cannot connect  to headless, is this error not reproducable with just the content of the cache. I am not sure, but I think this connction issues only appear after a crash by ZwGet or the sudden closing. I will have an eye on that.

Greets

52

Closed bug reports / Re: r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 2 February 2013, 14:56:36 »

something new: 4080 crashed today after a view good games(!) in the lobby!
logging was of, but there is a dmp-file: http://www.datafilehost.com/download-54e238e5.html

Greets

53

MegaGlest / Re: (False positive) virus detection on megaglest.exe, AVG

« on: 2 February 2013, 13:10:15 »

as I said - its not recognized by scanning, but by identity protection.
as I said, its acting unpredictable.
read this, to get an idea:

http://www.avg.com/de-de/faq.pnuid-faq_v3_avg_identity_protection

you have to play MG regular to be detected, not to scan for a virus. Yesterday AVG was rather busy:



May be there must be more things happen to be detected, as it is by alphatesting, as i did:

port80 or 443 connection open in browser simultaniously
replace an exe witn another version
call MG.exe by another programm
execute  MG.exe in an unusual location (D:)
and you have to do this often.

as you can see in the picture (click to enlarge) AVG detected cmd.exe as infected. and of course you can scan cmd.exe and there is no positiv! Its just the one who called the suspicious burglar, which is banned then.

it dissapeared right after playing and sometimes on next boot.

Greets

54

MegaGlest / Re: (False positive) virus detection on megaglest.exe, AVG

« on: 1 February 2013, 23:09:32 »

It seems that AVG is accumulating information of the behaviour of programs.

History of Detection:

Code: [Select]

"Erkennungsname";"Ergebnis";"Erkennungszeit";"Objekttyp";"Prozess"
"Unbekannt, D:\372.dev\megaglest.exe";"Gesichert";"20.01.2013, 10:02:53";"Datei oder Verzeichnis";""
"Unbekannt, D:\372.dev\megaglest.exe";"Gesichert";"22.01.2013, 11:55:28";"Datei oder Verzeichnis";""
"Unbekannt, D:\372dev\megaglest.exe";"Gesichert";"22.01.2013, 13:22:07";"Datei oder Verzeichnis";""
"Unbekannt, D:\372dev\megaglest.exe";"Gesichert";"23.01.2013, 00:02:15";"Datei oder Verzeichnis";""
"Unbekannt, D:\372dev\megaglest.exe";"Gesichert";"01.02.2013, 10:15:49";"Datei oder Verzeichnis";""
since even the releasecandidates of megaglest do not provide any information about its version in filename or comments in the code showed in windows so called "properties" its hard for me to decide which of the daily changing dev-releases I did run. Espacially as I missed the actual detection as a virus for weeks and was wondering how sometimes some file seem to dissappear. But I was not wondering tooo much because I am runng about 8 instances of megaglest in the house and think its possible to get confused managing the daily update of  the last new nightly build on different machines.

At last it was the relasecandidate 3.7.1.
megaglest v3.7.1 Compiled using: VC++: 1600 on: Nov 23 2012 00:38:33 platform: Windows endianness
: little
SVN: [Rev: 3948] - using STREFLOP [SSE] - [no-denormals]

which was busted. Mostly it were the dev-versions which were detected, propably because they were called by batch on my system.
The AVG is wide configurable to ignore positiv falses by the user. AVG is not telling too much about the methods of detections of course.

They suggest, the user shall report false positives to them so they will analyze the application and manage their next update.
I think its not worth the time to bother them with development versions.

But anyway, may be its a good idea to put an version info more easy accessable to the file somehow.

Greets

55

Closed bug reports / Re: r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 1 February 2013, 20:43:46 »

<softcoder> ok but nig says 3.7.1 works

The real scenario "Anarchy" with the Human Player doing nothing shows a slightly diffrent gameplay and you are killed bye green before the error appears.
If you use the game setting of the szenario Anarchy in a custom game and take team one as observer, then the gameplay is like the 3.7.2. devs and the error occures.

Greets

56

Closed bug reports / Re: r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 1 February 2013, 13:32:38 »

after a complete reinstall ( Ihad big issues ( inclusive instant crashes connecting to headless), which seem to relate to cache directory) I had a game on headless with 4077 on headless with leandro. Debug and logging was off. leandro was leaving early because of being found by overmighty cpu.

I played a little longer and everthing was fine. I didnt play to end because i had no chance against 3,9 Mega CPU. I quit the game.
I quit megaglest complete by pressing the "return" button and everything close nicely.

after all I saw this:



surprise, surpise! There is the promised dumpfile, but the Zwget did not appear...

dumpfile : http://www.datafilehost.com/download-d08907e4.html

Greets

[edit: may be leandro did not quit, but was thrown by unreported error? Headless was german Linux 3.7.1.]

[edit2: After that I let run "Anarchy" on Speedloops=2 again. Megaglest collapses at the well known time completely. No error Message, no dumpfile, no nothing. just closed]

57

MegaGlest / (False positive) virus detection on megaglest.exe, AVG

« on: 1 February 2013, 11:37:40 »

Some extraordinary intelligent virus-scanner might detect megaglest as virus.

This happened to me with http://www.avg.com/de-de/homepage .
The application detects (sometimes!) a danger of password-spying in megaglest by a modul called "identity protection". Megaglest seem to be dangerous because it looks for keyboard-events and send them over the internet.

I missed the warning-messages somehow especially running headless servers - and thats dangerous because some day AVG will decide, that this is a serious problem and will hide megaglest and some related objects like batchfiles and lnks without further notice. Its doing this unpredictable an well hidden on next reboot.

So, if you get strange issues of dissapearing megaglest.exe than have a look at your virus-protection.

Picture of the day:


Greets

58

Closed bug reports / Re: r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 31 January 2013, 10:27:37 »

D:\372dev>megaglest.exe
megaglest.exe v3.7.2-dev
Compiled using: VC++: 1600 on: Jan 30 2013 09:53:25 platform: Windows endianness
: little
SVN: [$Rev: 3951 $] - using STREFLOP [SSE] - [no-denormals]
AL lib: ReleaseALC: 1 device not closed

D:\372dev>

thats all it sais

[edit:] debug and network are written as told in ini: http://www.datafilehost.com/download-ffd2eb0d.html

59

Closed bug reports / Re: Your system supports OpenGL version "1.1.0" MegaGlest needs OpenGL 1.3 Error

« on: 30 January 2013, 22:02:08 »

I think, thats a good idea. For some resolutions it is displayed a while, but not properly and often somehow blocky, so that the Menu is not readable to change back...

60

Closed bug reports / Re: r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 30 January 2013, 14:51:20 »

huh?

i was fooled by the link in the megaglest-bugreport board right under the search, which lead me to the glest wiki : https://docs.megaglest.org/Compiling
instead to the megaglest-wiki https://docs.megaglest.org/MG/Windows_Compiling where i belong to.

sorry for complaining ... still afraid ...

Greets

61

Closed bug reports / Re: r4021: Linux64 game host freezes after first command

« on: 30 January 2013, 11:49:32 »

well, I did nothing to "summoner", I just pressed the button "join game" in the lobby. What do you mean?

62

Closed bug reports / Re: r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 30 January 2013, 11:19:58 »

well, win XP32 SP3, Geforce 6200 is running in an error too when looking at "Anarchy" on dev 4060. But the error-message is slightly different:



3.7.1. shows no error on this machine.

Compiling on Win 7 64 seem to be nothing for noobs and the wiki seem to need a little update.

The link to Visual c++ 2008 Express is broken - and this one is not supporting WIN7 anyway, sais Microsoft. Jam is needing Visual c++ too.

Googling for Visual c++ Express running on Win7 64 shows up Visual c++ 2010 and: lots of "well known issues using c++ on 64 Bit Machines"

Pointers are always 64Bit, but some systemvariables are remaining in 32 Bit and conversion is done by truncating, if you do not program your own workaround, i read.

Seem to be too complicated for me little windowsgamer...sorry

Greets

63

Closed bug reports / Re: Your system supports OpenGL version "1.1.0" MegaGlest needs OpenGL 1.3 Error

« on: 30 January 2013, 00:05:09 »

I can provoke this error on my machine by setting the colour-depth to 8 Bit.

maybe Frost should delete his glestuser.ini to reset megaglest to default settings.

Greets

64

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 29 January 2013, 22:44:15 »

cool it baby. to get a samba file share working on fedora took me three weeks.
to get a second display working on nvidia cpu on suse takes two hours.
there is crap everywhere, if you are able to face the truth.

Greets

65

Bug reports / Re: [bug] rev 4065: Shadows and lighting issues on some resolutions; Win7 - 64 bit

« on: 29 January 2013, 22:34:41 »

1440 x 900 works fine to me... but there are sometimes "black flashes" on my 1920x1080 games, which i didnt saw before. since a few devs.... may be thats the same but just for one frame ... ?

greets

66

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 29 January 2013, 21:38:24 »

Using this tool: http://www.realtech-vr.com/glview/ i found, that there seem to be serious driver issues with nvidia drivers on Win 7 64 with open GL

to be precise, on the laptop I cannot get a positiv rendering test for open GL 3.0, 3.1.

everything blow is okay, 3.2 and 3.3 seems to work.  Dont know, if that means anything.

Greets

67

Closed bug reports / Re: r4021: Linux64 game host freezes after first command

« on: 29 January 2013, 21:22:58 »

today on 4065:

First network game was on that thai-headless with nevsky. Got disconnected after some laggy seconds as described above.
disconnect window was the same like server is quitting on slf hosted game. "error detected, player nig disconnected"

MG did not crash

In Memory of yesterday i tried log in on headless. that worked.

Than I fumbled around with Graphic card drivers.

than i wanted to start a game on german headless.... bang! immediate crash! logs: http://www.datafilehost.com/download-1a986d7f.html
tried again.. bang! immediate crash! logs: http://www.datafilehost.com/download-e815f9f4.html
tried again ... bang! immediate crash! too tired for more logs ...

then I cleared the cache - directory in the logpath directory , did nothing else    and tried again    .... working!

Is the immidiate crash just a bug in the loggingroutine after disconncecting?

Greets

68

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 29 January 2013, 18:19:11 »

Im using win 7  64 pro Sp1 on the laptop and Win7 64 Home premium  Sp1 on the desktop

Both are actual patched with "important updates"

both are having the described issues.

Congrates to your installation. Be Happy that its not Win8. They say this takes two weeks.

After your question I had a deeper look at system config again.

Using this tool: http://www.realtech-vr.com/glview/ i found, that there seem to be serious driver issues with nvidia drivers on Win 7 64 with open GL

Have a look at that. May be you find something. I am fumbling around here too.
May be you know another tool to check open GL-Functions?

Greets

69

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 29 January 2013, 08:40:20 »

logs of 4065, logged to HDD at speedloops=8, colourpicking:
http://www.datafilehost.com/download-65b75b46.html

logs of 4065, logged to HDD at speedloops=8, selectbufpicking:
http://www.datafilehost.com/download-70611b81.html

Greets

70

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 28 January 2013, 21:39:14 »

In linux I get no crash and there is not really a second attack of blue attacking yellow.
If blue attacks yellow the second time only oone building is left amd green is in blues "town" .

Yes, thats what I tried to describe. Same happens to me. The crash happens when the blue ghoul reaches the scene. A few secs before the last summoner guild of yellow dissappears

happens too at fastspeed=8, selectBuf was selected all the time

Greets

71

Closed bug reports / Re: r4021: Linux64 game host freezes after first command

« on: 28 January 2013, 21:25:07 »

Ladys and Gentleman!
There it is again:

I did three network games today with 4064.
All on headless Linux 3.7.1 and one other player.

In first one i was thrown out with Time out after 15 minutes or so.
then iplayed around with the "anarchy setting" mentioned in the other thread.

then I did another networkgame, which came to an end, but had some strange laggy moments (freeze for 1 to 5 secs and then hunting to sync in ultra speed ). Happened round about 5 times.

after that i tried again to log in headless for another game: bang!
 immidiate crash

restart glest try to login in headless: bang!
immidiate crash!

thats the exact behaviour for me like the days tom reported above.
In those days I reinstalled MG complete new and that does the trick.

Funny: there are two errors showing up: first:



if you press ok on the error window of OS, the second error appears:



after that Iwrote this post and tried to start a local game. that worked.
after that I tried to login on headless again without changing anything.

and it worked!

So may be, i just had to wait for windows to settle down after that crash? Anyway, looks for me quite similar to the event we had those days.

Greets

 

72

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 28 January 2013, 13:13:44 »

figured out, that you can look at the bug in a normal game, which settings are the same llike the sceanrio:


Download this image: http://www.datafilehost.com/download-003b6a36.html

I tried to find something unusual like big crowds or something blocked or whatever.
The error occures in the second attack of blue magic against yellow magic. yellow has lost its castle already by the green tech, and one battlemage of blue is attacking the final summoner guild, followed by some blue collegs. Game crashes befor they arrive and before summoner guild is finally down.

found nothing unusual until now, but:

Error does not occure when i load a saved game. I did the saving before and the game crashed like always. But not if i reload that save.
Error is independent of resolution of screen, but depends on the position of camera:
If I look on that fight described above at the yellow base, the error does not occure.
If  i look at green or blue base, the error occores.

That is all real magic

Edit (tomreyn): Image downloaded from file storage host, uploaded to image hosting site + embedded
Subsequent edit by Omega: The image host used by Tomreyn does not allow direct linking. Reuploaded to Imgur.

73

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 28 January 2013, 11:54:43 »

r4064: Its still there.
I fumbled around with fog of war, changing teams to have a look to see what is happening in the other teams. But every thing i do to just see what all the units are doing is changing the game play and the error disappears.

So Im am nearly convinced its just a silly event in the game play which causes that error. The main thing is not, that anarchy is crashing when you do nothing for 15 minutes (or just one at speedloops 16). The thing is, that this event happens in other games and is probably triggering the same error again.

interesting is the dependency on tilesets. does the tileset matter for the decisions of AI?. In Anarchy it has to be a movement of AI that triggers that error - but only in tilset winter_forest.

Greets

I remember I had a similar error long time ago with "my island". I could reproduce that error in that time by doing the same very defensiv tactic (try to be not to be seen too early).
If you do this in those days there will come an initiate and will discover your base. After a short time there was then the error appearing regulary.

So it might be there for long time - but just happening rarly

74

Closed bug reports / Re: r4021: Linux64 game host freezes after first command

« on: 28 January 2013, 11:38:33 »

the instant error never appeared again for me, although it was reproducable in those days.
But my activity playing glest have become less during the last week and I took the windows-dev headless urg offline again because i think its too frustrating that games break after 15 Min or longer quite often.
So the dissapearing of that bug might be not representative.

Greets

75

Closed bug reports / Re: [lacks info] r4001, Win7-64: Fails with ZwGetContextThread!ntdll (null)(0) +18

« on: 26 January 2013, 00:43:31 »

4060 : Anarchy crashed in the winter_forest again. This time I moved a bit.

logs: http://www.datafilehost.com/download-e895078c.html and greets