Send P2mapper mailing list submissions to
p2mapper@list.valvesoftware.com
To subscribe or unsubscribe via the World Wide Web, visit
http://list.valvesoftware.com/cgi-bin/mailman/listinfo/p2mapper
or, via email, send a message with subject or body 'help' to
p2mapper-requ...@list.valvesoftware.com
You can reach the person managing the list at
p2mapper-ow...@list.valvesoftware.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of P2mapper digest..."
Today's Topics:
1. Beta Hammer Memory Usage Redundancy Error (Josiah Jack)
2. Hammer 3D Viewport Navigation Error (Josiah Jack)
3. Re: Beta Hammer Memory Usage Redundancy Error (Cory De La Torre)
----------------------------------------------------------------------
Message: 1
Date: Thu, 27 Oct 2011 21:53:36 -0500
From: "Josiah Jack" <jos...@jackconstruction.com>
To: "P2 Mapper List" <p2mapper@list.valvesoftware.com>
Subject: [P2mapper] Beta Hammer Memory Usage Redundancy Error
Message-ID: <728D56370F5A40F98F801FFFD47D22B9@Saraneth>
Content-Type: text/plain; charset="iso-8859-1"
Hello,
I compiled a map and minimized the compiler while it compiled, and when I came
back to bring Hammer up it wasn't responding. So I brought up Task Manager to
see if it had crashed and checked the Processes tab and it showed Hammer as
fine and using 450mb memory (as per usual). In few seconds hammer responded
and came back up, but that's when the memory usage spiked up to 1,500mb!! It
trippled in memory usage in less than 15seconds. In a bit of a panic I closed
it down since the memory usage kept climbing.
If any valve representative reads this, then please let the coders know that
there's a memory glitch in the Portal 2 Beta SDK's Hammer Editor. Sorry I
don't have a crash dump, since it technically didn't crash.
Just FYI
------------------------------
Message: 2
Date: Thu, 27 Oct 2011 21:57:45 -0500
From: "Josiah Jack" <jos...@jackconstruction.com>
To: "P2 Mapper List" <p2mapper@list.valvesoftware.com>
Subject: [P2mapper] Hammer 3D Viewport Navigation Error
Message-ID: <CE04D3B57F3946BF88764C06F6A77B5F@Saraneth>
Content-Type: text/plain; charset="iso-8859-1"
3D Viewport WASD Navigation is slow to respond and jumps from point to point
instead of having smooth camera movement.
I tend to want to use SDK's Hammer instead of the Portal 2 Beta one because of
this.
Is anyone else experiencing this issue?
------------------------------
Message: 3
Date: Fri, 28 Oct 2011 11:23:45 -0700
From: Cory De La Torre <mrtwovideoca...@gmail.com>
To: Josiah Jack <jos...@jackconstruction.com>, P2 Mapper List
<p2mapper@list.valvesoftware.com>
Subject: Re: [P2mapper] Beta Hammer Memory Usage Redundancy Error
Message-ID:
<CAKcryTio0osEdKEQw5e0fwXA9qcFDD7RgrxEbjq=qftzyue...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Welcome to 2006.
On Thu, Oct 27, 2011 at 7:53 PM, Josiah Jack <jos...@jackconstruction.com>wrote:
> Hello,
>
> I compiled a map and minimized the compiler while it compiled, and when I
> came back to bring Hammer up it wasn't responding. So I brought up Task
> Manager to see if it had crashed and checked the Processes tab and it showed
> Hammer as fine and using 450mb memory (as per usual). In few seconds hammer
> responded and came back up, but that's when the memory usage spiked up to
> 1,500mb!! It trippled in memory usage in less than 15seconds. In a bit of
> a panic I closed it down since the memory usage kept climbing.
>
> If any valve representative reads this, then please let the coders know
> that there's a memory glitch in the Portal 2 Beta SDK's Hammer Editor.
> Sorry I don't have a crash dump, since it technically didn't crash.
>
> Just FYI
> _______________________________________________
> P2mapper mailing list
> P2mapper@list.valvesoftware.com
> http://list.valvesoftware.com/cgi-bin/mailman/listinfo/p2mapper
>
--
--Geardev
------------------------------
_______________________________________________
P2mapper mailing list
P2mapper@list.valvesoftware.com
http://list.valvesoftware.com/cgi-bin/mailman/listinfo/p2mapper
End of P2mapper Digest, Vol 6, Issue 16
***************************************
