Matrix Games Forums

 Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Bombardment Bug

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [Current Games From Matrix.] >> [World War II] >> Uncommon Valor - Campaign for the South Pacific >> Tech Support >> Bombardment Bug Page: [1]
Login
Message << Older Topic   Newer Topic >>
Bombardment Bug - 8/19/2002 5:17:35 AM   
John Lansford

 

Posts: 2662
Joined: 4/29/2002
Status: offline 		Using version 1.2, I sent a task force of cruisers and destroyers to bombard the Shortlands. After shooting up some destroyers, they then began the bombardment routine.

Except instead of the usual screen showing the bombardment, it went to a ground attack screen involving the Kanga Force and a Japanese regiment. My task force took a few hits from 3" guns, and the summary looked correct (hits on the port, airfields and support facilities), but it looks like the combat screen routine is messed up.
Post #: 1
- 8/19/2002 7:04:24 AM   
Bernd Hesberg

 

Posts: 114
Joined: 10/11/2001
From: Germany
Status: offline 		This behaviour has been reported earlier, and it's on the list. AFAIK a memory leak is causing this, but since it doesn't get fixed with v1.30 I guess we'll have to wait for the next patch. It's not a game breaker, just messing up the display.

(in reply to John Lansford)
Post #: 2
- 8/19/2002 9:47:42 AM   
XPav

 

Posts: 550
Joined: 7/10/2002
From: Northern California
Status: offline 		"A memory leak is causing this."

Based off of what?

_____________________________

I love it when a plan comes together.

(in reply to John Lansford)
Post #: 3
- 8/19/2002 5:58:27 PM   
Bernd Hesberg

 

Posts: 114
Joined: 10/11/2001
From: Germany
Status: offline 		You may read Ross' reply in the following thread

[URL]http://www.matrixgames.com/forums/showthread.php?s=&threadid=23596[/URL]

Beside those posts I've had some correspondence via email. So I'm absolutely sure that this bug will be hunted down, but I don't know any details.

(in reply to John Lansford)
Post #: 4
- 8/20/2002 1:03:27 AM   
XPav

 

Posts: 550
Joined: 7/10/2002
From: Northern California
Status: offline 		I don't see how this could be a memory leak.

What it looks like is a buffer being reused without clearing it.

But that's not a memory leak, its a different problem.

Consider this part of my fight against every single technical problem being labeled a "memory leak".

_____________________________

I love it when a plan comes together.

(in reply to John Lansford)
Post #: 5
- 8/20/2002 5:42:10 AM   
Bernd Hesberg

 

Posts: 114
Joined: 10/11/2001
From: Germany
Status: offline 		Hi Alex,

I didn't think that using this particular term would hit your tender spot. :)

Since English isn't my native language, and you need specific knowledge to translate technical terms, I may have misunderstood or misused it. Of course, you may blame me for repeating it without prior checking if this term would be appropriate. But maybe you can give me a competent definition for memory leaks ?

(in reply to John Lansford)
Post #: 6
- 8/20/2002 11:56:39 AM   
XPav

 

Posts: 550
Joined: 7/10/2002
From: Northern California
Status: offline 		Memory leak is what Matrix says. I just don't buy it. :-)

A memory leak is when the program goaes "Hey! Operating System! Give me some memory to play with!"

It doesn't give it back, and forget that it has it.

Next time the program comes back to the same thing, it goes "Hey! Operating System! Give me some memory to play with!".

Do this enough from one program with big enough chunks of memory on the system and you can get the thing to start using so much memory that the OS has to really start working, swapping memory out to disk, etc etc.

The problems all go away when the program is completely terminated, or worse comes to worse (if the program really started doing some stupid things), when the computer is rebooted.

Memory leaks are a common problem when writing code in C and C++. The sad part is that there's so many, many ways to avoid memory leaks that we shouldn't have to deal with them.

_____________________________

I love it when a plan comes together.

(in reply to John Lansford)
Post #: 7
Page:   [1]
All Forums >> [Current Games From Matrix.] >> [World War II] >> Uncommon Valor - Campaign for the South Pacific >> Tech Support >> Bombardment Bug Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

1.000