gamedevlists-windows Mailing List for gamedev (Page 42)
Brought to you by:
vexxed72
Menu
▾
▴
gamedevlists-windows — List for discussing game development on the Windows platform
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(48) |
Oct
(58) |
Nov
(49) |
Dec
(38) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(124) |
Feb
(83) |
Mar
(17) |
Apr
(37) |
May
(12) |
Jun
(20) |
Jul
(47) |
Aug
(74) |
Sep
(62) |
Oct
(72) |
Nov
(54) |
Dec
(13) |
| 2003 |
Jan
(36) |
Feb
(8) |
Mar
(38) |
Apr
(3) |
May
(6) |
Jun
(133) |
Jul
(20) |
Aug
(18) |
Sep
(12) |
Oct
(4) |
Nov
(28) |
Dec
(36) |
| 2004 |
Jan
(22) |
Feb
(51) |
Mar
(28) |
Apr
(9) |
May
(20) |
Jun
(9) |
Jul
(37) |
Aug
(20) |
Sep
(23) |
Oct
(15) |
Nov
(23) |
Dec
(27) |
| 2005 |
Jan
(22) |
Feb
(20) |
Mar
(5) |
Apr
(14) |
May
(10) |
Jun
|
Jul
(6) |
Aug
(6) |
Sep
|
Oct
(12) |
Nov
(1) |
Dec
|
| 2006 |
Jan
(18) |
Feb
(4) |
Mar
(3) |
Apr
(6) |
May
(4) |
Jun
(3) |
Jul
(16) |
Aug
(40) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2007 |
Jan
(5) |
Feb
(2) |
Mar
(4) |
Apr
(1) |
May
(13) |
Jun
|
Jul
(26) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(4) |
Dec
(5) |
| 2008 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mickael P. <mpo...@ed...> - 2002-10-11 09:16:29
|
> Hi,
>
> I would say it is a problem of memory, but not of
> resources. As Javier had just point out, a resource
> leak is not fixed once you kill the application.
> Yesterday, I had the same kind of corruption : drawing
> the GUI of any of the open application was taking
> ages... The Task manager show me CodeWarrior was using
> 500 Mg, and that there was more than 1 gigaoctet
> used...
> Once I killed CodeWarrior, everything was OK again...
<rant>
Killing CodeWarrior generaly solve a lot of things...
</rant>
Well, more seriously, in my experience resource leaks
were fatal under windows 95/98 (millenium also I suspect),
but not always under windows 2k. Depending which kind of
resource was abused 2k sometimes manage to restore it's
internal state when the abusing program is killed, for some
other kind of resources he does not manage to do it.
By resource I mean things like file system handles, gui
items, and basicaly all these things you have to allocate
and then release but are not necessarily related to memory.
The worse problems I had were with DLL, because of the
reference counting thing you not always manage to free
it from memory, so the lost resources I still considered
as used.
Mike
|
|
From: <e_a...@ya...> - 2002-10-11 08:37:07
|
Hi, I would say it is a problem of memory, but not of resources. As Javier had just point out, a resource leak is not fixed once you kill the application. Yesterday, I had the same kind of corruption : drawing the GUI of any of the open application was taking ages... The Task manager show me CodeWarrior was using 500 Mg, and that there was more than 1 gigaoctet used... Once I killed CodeWarrior, everything was OK again... Emmanuel --- Mickael Pointier <mpo...@ed...> a écrit : > > Pierre Terdiman <p.t...@wa...> wrote: > > > > > I didn't say that, but maybe that was unclear. > I'm running W98 but > > > the bug *does* indeed occur on other machines, > e.g. with W2K. > > > > The only way I have ever managed to corrupt the > Win2K GUI was by creating > > graphics resources and not deleting them: bitmaps, > DCs, fonts, etc. The > last > > time I had this was because I was creating a new > bitmap every time the > > window was resized / redrawn, but not freeing the > previous bitmap > properly. > > I second that. > > This kind of behavior is generaly not memory > related, but "resource" > related. You can kill a windows 98 simply by doing a > loop that call > "CreateWindow" repetetively. > > Mickael Pointier > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=555 ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |
|
From: Mickael P. <mpo...@ed...> - 2002-10-11 07:28:26
|
> Pierre Terdiman <p.t...@wa...> wrote:
>
> > I didn't say that, but maybe that was unclear. I'm running W98 but
> > the bug *does* indeed occur on other machines, e.g. with W2K.
>
> The only way I have ever managed to corrupt the Win2K GUI was by creating
> graphics resources and not deleting them: bitmaps, DCs, fonts, etc. The
last
> time I had this was because I was creating a new bitmap every time the
> window was resized / redrawn, but not freeing the previous bitmap
properly.
I second that.
This kind of behavior is generaly not memory related, but "resource"
related. You can kill a windows 98 simply by doing a loop that call
"CreateWindow" repetetively.
Mickael Pointier
|
|
From: Javier A. <ja...@py...> - 2002-10-11 06:51:01
|
Pierre Terdiman <p.t...@wa...> wrote: > I didn't say that, but maybe that was unclear. I'm running W98 but > the bug *does* indeed occur on other machines, e.g. with W2K. The only way I have ever managed to corrupt the Win2K GUI was by creating graphics resources and not deleting them: bitmaps, DCs, fonts, etc. The last time I had this was because I was creating a new bitmap every time the window was resized / redrawn, but not freeing the previous bitmap properly. I was surprised to see Windows corrupted even after I shut down the offending program, Restart needed. Javier Arevalo Pyro Studios |
|
From: Rich <leg...@xm...> - 2002-10-10 23:49:28
|
In article <04eb01c270b5$bf7802e0$0e00000a@pierre>,
"Pierre Terdiman" <p.t...@wa...> writes:
> I didn't say that, but maybe that was unclear. I'm running W98 but the bug
> *does* indeed occur on other machines, e.g. with W2K.
Well, lots of stuff in the GUI is in user mode I suppose, so could be
corrupted by an errant app. Things like image lists are definately in
your process space and could be damaged.
--
Ask me about my upcoming book on Direct3D from Addison-Wesley!
Direct3D Book <http://www.xmission.com/~legalize/book/>
izfree: Open source tools for Windows Installer
<http://izfree.sourceforge.net>
|
|
From: Pierre T. <p.t...@wa...> - 2002-10-10 23:37:40
|
Hi Rich, > Sounds like what I was going to suggest... use a tool like Purify, > BoundsChecker, etc., to find the problem. I just installed BoundsChecker. Going to see what I can find. > You say it only occurs on Win98, but I'm willing to bet that's not I didn't say that, but maybe that was unclear. I'm running W98 but the bug *does* indeed occur on other machines, e.g. with W2K. Going to check my bounds right now. Pierre |
|
From: Rich <leg...@xm...> - 2002-10-10 23:16:16
|
In article <F23...@FR...>,
Andrew Grant <ag...@cl...> writes:
> I've seen things like that before, and when it's happened I've found I've
> been trashing memory somewhere.
>
> Weird I know, but there you go.
Sounds like what I was going to suggest... use a tool like Purify,
BoundsChecker, etc., to find the problem.
You say it only occurs on Win98, but I'm willing to bet that's not
quite true. If its a memory bug, its probably occuring everywhere,
just that the effects are more damaging on Win9x. Purify only works
on NT-based platforms (so not 9x), but its worth it, IMO.
--
Ask me about my upcoming book on Direct3D from Addison-Wesley!
Direct3D Book <http://www.xmission.com/~legalize/book/>
izfree: Open source tools for Windows Installer
<http://izfree.sourceforge.net>
|
|
From: Andrew G. <ag...@cl...> - 2002-10-10 21:35:32
|
I've seen things like that before, and when it's happened I've found I've been trashing memory somewhere. Weird I know, but there you go. Andy @ Climax Brighton > -----Original Message----- > From: Pierre Terdiman [mailto:p.t...@wa...] > Sent: 10 October 2002 22:08 > To: gam...@li... > Subject: [GD-Windows] Nasty GUI bug > > > I have a nasty bug that breaks Windows GUI big time. > > Here's the context : > - Windows 98 RC2 > - 3DS MAX 4.0 > - A MAX plug using the MFC, among other things > > And what happens : > - I run MAX, plug gets loaded and works fine for a moment. > - Then after some manipulations, the whole Windows GUI breaks > down, falls > appart, goes berserk, becomes mad. Not only in MAX : in > Wordpad, in Notepad, > on the desktop, well, in all other apps. Fonts change for the > ugly years-old > system fonts. Icons disappear. Drag-and-drop doesn't work > anymore. Notepad > don't run anymore. Paint doesn't either, saying there's not > enough memory to > complete requested operation. I could go on for hours. > - Even when the whole world is fucked up, everything goes > back to normal the > second I close MAX. > - And if I remove the MAX Plug, the bug never comes, so I > guess it's the > guilty one. > > I simply have no idea how to track that one, or what could be > happening. > Ideas ? > > Example of fucked-up GUI : > http://www.codercorner.com/GUI_Bug_Fileselect.jpg > http://www.codercorner.com/GUI_Bug_WordPad.jpg > > The problem seems to appear on some other machines, not only > mine, but not > on all of them. Most of the time, it works. > > ..... > > Pierre > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=555 > |
|
From: Pierre T. <p.t...@wa...> - 2002-10-10 21:10:03
|
I have a nasty bug that breaks Windows GUI big time. Here's the context : - Windows 98 RC2 - 3DS MAX 4.0 - A MAX plug using the MFC, among other things And what happens : - I run MAX, plug gets loaded and works fine for a moment. - Then after some manipulations, the whole Windows GUI breaks down, falls appart, goes berserk, becomes mad. Not only in MAX : in Wordpad, in Notepad, on the desktop, well, in all other apps. Fonts change for the ugly years-old system fonts. Icons disappear. Drag-and-drop doesn't work anymore. Notepad don't run anymore. Paint doesn't either, saying there's not enough memory to complete requested operation. I could go on for hours. - Even when the whole world is fucked up, everything goes back to normal the second I close MAX. - And if I remove the MAX Plug, the bug never comes, so I guess it's the guilty one. I simply have no idea how to track that one, or what could be happening. Ideas ? Example of fucked-up GUI : http://www.codercorner.com/GUI_Bug_Fileselect.jpg http://www.codercorner.com/GUI_Bug_WordPad.jpg The problem seems to appear on some other machines, not only mine, but not on all of them. Most of the time, it works. ..... Pierre |
|
From: David N. <dno...@mi...> - 2002-10-10 21:04:11
|
Also, attaching a debugger after the program has started (manually or = with an int 3), can help to track down issue. David -----Original Message----- From: David Notario [mailto:dno...@mi...] Sent: Thursday, October 10, 2002 2:00 PM To: Pierre Terdiman; gam...@li... Subject: RE: [GD-Windows] Debug or not debug under VC++ Some suggestions from VC team: - F5 gets a different memory heap from NT than CTRL+F5. Try pageheap or = appverifier to help determine if this is the problem. - Maybe you have an uninitialized local that gets a different value in = both scenarios. Try Warning level 4. David -----Original Message----- From: Pierre Terdiman [mailto:p.t...@wa...] Sent: Thursday, October 10, 2002 1:42 PM To: gam...@li... Subject: [GD-Windows] Debug or not debug under VC++ Under VC++, I've a computational geometry algorithm that fails (finds no solution) when I run the exe with "Ctrl-F5", but it works with "F5". What are the exact differences between the two, as far as the machine = state is concerned ? It's probably some FPU-related issue... Pierre ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Gamedevlists-windows mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=3D555 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Gamedevlists-windows mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows Archives: http://sourceforge.net/mailarchive/forum.php?forum_idU5 |
|
From: David N. <dno...@mi...> - 2002-10-10 21:00:06
|
Some suggestions from VC team: - F5 gets a different memory heap from NT than CTRL+F5. Try pageheap or = appverifier to help determine if this is the problem. - Maybe you have an uninitialized local that gets a different value in = both scenarios. Try Warning level 4. David -----Original Message----- From: Pierre Terdiman [mailto:p.t...@wa...] Sent: Thursday, October 10, 2002 1:42 PM To: gam...@li... Subject: [GD-Windows] Debug or not debug under VC++ Under VC++, I've a computational geometry algorithm that fails (finds no solution) when I run the exe with "Ctrl-F5", but it works with "F5". What are the exact differences between the two, as far as the machine = state is concerned ? It's probably some FPU-related issue... Pierre ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Gamedevlists-windows mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=3D555 |
|
From: Pierre T. <p.t...@wa...> - 2002-10-10 20:43:59
|
Under VC++, I've a computational geometry algorithm that fails (finds no solution) when I run the exe with "Ctrl-F5", but it works with "F5". What are the exact differences between the two, as far as the machine state is concerned ? It's probably some FPU-related issue... Pierre |
|
From: Space N. E. <SPA...@ho...> - 2002-10-02 19:03:46
|
Hi, I have a Win32 app (no MFC) with a lot of subclassed common controls - subclassed so I can draw them the way I like. One big problem I've run into is that I can't seem to control the colors that scrollbars are drawn with when a window has WS_VSCROLL/WS_HSCROLL styles specified - this happens, for example, when a the data in a tree control is too large to fit in the client area. I know that the SysColors are used to control the drawing of window scrollbars, but I don't want to change the color of all scrollbars (and 3d controls in general), just those of my app. And more specifically, I'm a plugin, not an app, so I REALLY don't want to change the colors of the host app. I also tried double buffering - tweaking the WM_PAINT/WM_NCPAINT messages I receive, and sending in an offscreen HDC when I call the tree control's default window proc. Then I render over top of the scrollbars to effectively draw my own. This works very well, except that the scrollbars somehow redraw themselves without the aid of WM_PAINT/WM_NCPAINT when they are being dragged around, yielding a horrific flickering. How do web pages change IE's scrollbar colors? I'm guessing that the web browser control either has custom scrollbars, or uses a scrollbar control, etc. Bummer. Well, if anyone knows of a good way to do "owner draw" scrollbars on a window (not scrollbar controls), let me know! Thanks, Brian |
|
From: Tom F. <to...@mu...> - 2002-09-19 09:39:32
|
Changing PCI slots forces the IRQ arbitration to be re-done, so it solves a suprising number of conflicts on all sorts of cards. This combo is (a) incredibly common and (b) prone to problems. Randomly installing drivers and moving PCI slots usually eventually sorts it, but it's all just voodoo, and in some cases I've had to simply turn hardware sound accelleration off completely, so DSound is doing the mixing in software and using the legacy (but reliable) WaveOut stuff. Tom Forsyth - purely hypothetical Muckyfoot bloke. This email is the product of your deranged imagination, and does not in any way imply existence of the author. > -----Original Message----- > From: Eero Pajarre [mailto:epa...@ko...] > Sent: 18 September 2002 19:53 > To: gam...@li... > Subject: Re: [GD-Windows] DirectSound(3D) and Windows XP, known > problems? > > > Jon Watte wrote: > > > Interrupt sharing not working? That's so lame. What is the > sound and > > graphics cards, so I can avoid one of them? :-) > > > > Nvidia (Geforce 4) based graphics, and Creative (SB Live) soundcard, > easy to avoid ;-) > > Seriously, I don't really know what was happening, except > that changing > to a different PCI slot apparently fixed it. (actually according the > the motherboard docs there should not have been direct > conflicts in the > original slot either). It is quite possible that I am doing something > wrong with DirectSound, and it just has worked so far. > > I will also finish my OpenAL backend, in my tests it at least > had different > problems. > > > Eero > > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: AMD - Your access to the experts > on Hammer Technology! Open Source & Linux Developers, register now > for the AMD Developer Symposium. Code: EX8664 > http://www.developwithamd.com/developerlab > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=555 > |
|
From: Jon W. <hp...@mi...> - 2002-09-18 21:31:23
|
> Nvidia (Geforce 4) based graphics, and Creative (SB Live) soundcard, > easy to avoid ;-) Yeah. I'll mark that combo as "not supported". Thanks. :-) That aside, I've had horrible experiences with SB Live drivers on Windows XP. The update that you can get from Microsoft Update was worse than anything else I've tried, and the latest download from soundblaster.com isn't a whole lot better. Blech. Cheers, / h+ |
|
From: Eero P. <epa...@ko...> - 2002-09-18 18:53:26
|
Jon Watte wrote: > Interrupt sharing not working? That's so lame. What is the sound and > graphics cards, so I can avoid one of them? :-) > Nvidia (Geforce 4) based graphics, and Creative (SB Live) soundcard, easy to avoid ;-) Seriously, I don't really know what was happening, except that changing to a different PCI slot apparently fixed it. (actually according the the motherboard docs there should not have been direct conflicts in the original slot either). It is quite possible that I am doing something wrong with DirectSound, and it just has worked so far. I will also finish my OpenAL backend, in my tests it at least had different problems. Eero |
|
From: Jon W. <hp...@mi...> - 2002-09-18 17:12:56
|
> But I was sort of lucky, I happened to notice that the screen mode > which was used correlated with the sound problems. This made me suspect > interrupt issues between graphics and sound card. Moving the sound > card to a different PCI slot seems to solve the problem. Interrupt sharing not working? That's so lame. What is the sound and graphics cards, so I can avoid one of them? :-) There's really no excuse for spending more than like 50 microseconds in an interrupt handler these days. Cheers, / h+ |
|
From: Eero P. <epa...@ko...> - 2002-09-18 11:52:41
|
Tom Forsyth wrote: > Sound driver problems. Who would have thought it? :-) > > Sound driver quality ranges from bad to appalling. Most code I know always > uses software mixing and the fewest number of features possible. By all > means have an "advanced" panel so the user can re-enable all the > 3D-surround-sound-hardware-accellerated loveliness, but make it advanced, > not default, because it's so flaky, and the flakiness is so random. Better > to get basic 2D sound without hisses and crackles and distortion on all > platforms than get really cool sound on some and BSODs on others :-( > > It's usually sound driver and/or motherboard driver related. Because of my specific requirements, downgrading from the 4-channel audio was not really possible. But I was sort of lucky, I happened to notice that the screen mode which was used correlated with the sound problems. This made me suspect interrupt issues between graphics and sound card. Moving the sound card to a different PCI slot seems to solve the problem. For me this is an ok fix at the moment. (I understand that for a typical game providing a reliable fallback alternative is a must) Eero |
|
From: Tom F. <to...@mu...> - 2002-09-16 10:32:53
|
Sound driver problems. Who would have thought it? :-) Sound driver quality ranges from bad to appalling. Most code I know always uses software mixing and the fewest number of features possible. By all means have an "advanced" panel so the user can re-enable all the 3D-surround-sound-hardware-accellerated loveliness, but make it advanced, not default, because it's so flaky, and the flakiness is so random. Better to get basic 2D sound without hisses and crackles and distortion on all platforms than get really cool sound on some and BSODs on others :-( It's usually sound driver and/or motherboard driver related. Tom Forsyth - purely hypothetical Muckyfoot bloke. This email is the product of your deranged imagination, and does not in any way imply existence of the author. > -----Original Message----- > From: Eero Pajarre [mailto:epa...@ko...] > Sent: 13 September 2002 18:56 > To: gam...@li... > Subject: [GD-Windows] DirectSound(3D) and Windows XP, known problems? > > > I have written a simulator which uses the DirectSound3D > to position several sound efects around the user. > Typically the simulator is used in a 4 channel > setup so I found the 3d interface useful. > > I have compiled it using the dsound which was > included with VC++ 6.0, which must mean something > quite old. I do my graphics in OpenGL so I have > not had the need to follow the latest DirectX versions. > > The simulator works ok with Windows 98 and Windows ME > using SB Live and Live 5.1 soundcards, but with > WindowsXP there are serious sound quality problems. > > Also when testing with the Creative speaker test program > I think I hear something wrong with the sound on the > Win XP machine. > > Has anybody seen (heard) this before. Should I be looking > for a driver, DirectX, or application bug? > > > Eero > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=555 > |
|
From: Eero P. <epa...@ko...> - 2002-09-13 17:56:22
|
I have written a simulator which uses the DirectSound3D to position several sound efects around the user. Typically the simulator is used in a 4 channel setup so I found the 3d interface useful. I have compiled it using the dsound which was included with VC++ 6.0, which must mean something quite old. I do my graphics in OpenGL so I have not had the need to follow the latest DirectX versions. The simulator works ok with Windows 98 and Windows ME using SB Live and Live 5.1 soundcards, but with WindowsXP there are serious sound quality problems. Also when testing with the Creative speaker test program I think I hear something wrong with the sound on the Win XP machine. Has anybody seen (heard) this before. Should I be looking for a driver, DirectX, or application bug? Eero |
|
From: Rich <leg...@xm...> - 2002-09-12 17:29:26
|
When: Friday, September 27th, 2002
7pm - 10pm
Where: Old Fine Arts Museum
(just north of the ART building)
<http://www.map.utah.edu/umaplink/0036.html>
<http://www.xmission.com/~legalize/stusiggposterfall2002_1_web.gif>
All digital artists (that includes you coders, too!) are welcome!
--
Ask me about my upcoming book on Direct3D from Addison-Wesley!
Direct3D Book <http://www.xmission.com/~legalize/book/>
izfree: Open source tools for Windows Installer
<http://izfree.sourceforge.net>
|
|
From: Timur D. <ti...@cr...> - 2002-09-12 08:27:26
|
No in .NET F12 is still generating user-breakpoint, but not '-' key. I once saw F12 somewhere in VC debugger documention, but i guess it can = be found out only by accident :) _________________ Timur Davidenko. Crytek Studios (www.crytek.com) > -----Original Message----- > From: Javier Arevalo [mailto:ja...@py...] > Sent: Thursday, September 12, 2002 8:40 AM > To: gam...@li... > Subject: Re: [GD-Windows] Weirdest Error Ever >=20 >=20 > Joe Collins <jo...@mu...> wrote: >=20 > > Hi all. I have a very very weird error that I am getting.=20 > If I hit the > > '-' key on the keypad while running > > my app in the vcnet debugger. > > Its getting an exception in the GetMessage call >=20 > When you run an app under the VC6 debugger, pressing F12=20 > instantly breaks > into the debugger (just like hitting "break" in vc6's Debug=20 > menu). Could > this be .NET's equivalent? I never saw F12 documented=20 > anywhere (I never > looked for it, either)... >=20 > Javier Arevalo > Pyro Studios >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows > Archives: > http://sourceforge.net/mailarchive/forum.php?forum_id=3D555 >=20 |
|
From: Javier A. <ja...@py...> - 2002-09-12 06:38:09
|
Joe Collins <jo...@mu...> wrote: > Hi all. I have a very very weird error that I am getting. If I hit the > '-' key on the keypad while running > my app in the vcnet debugger. > Its getting an exception in the GetMessage call When you run an app under the VC6 debugger, pressing F12 instantly breaks into the debugger (just like hitting "break" in vc6's Debug menu). Could this be .NET's equivalent? I never saw F12 documented anywhere (I never looked for it, either)... Javier Arevalo Pyro Studios |
|
From: Joe C. <jo...@mu...> - 2002-09-11 20:17:58
|
Hi all. I have a very very weird error that I am getting. If I hit the
'-' key on the keypad while running
my app in the vcnet debugger.
Its getting an exception in the GetMessage call
so my code looks like this....
while (GetMessage(&msg, this->hWnd, 0, 0))
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
the exception occurs in the GetMessage call, and the call stack
basically goes into the kernel at that point and basically gives me no
indication as to what the hell is going on.
So I figured it was some dumb code of mine. Well I created a new win32
solution/project and built it. And it
has the same problem. Hit the '-' keypad key while in the debugger and
it throws an exception.
The app seems to work ok outside of vc.NET debugger
So this is a bug right? Not some weird hotkey or something...
-Joe
P.S. I never saw anything as weird as this while using vc++ 6 :)
|
|
From: Andrew G. <ag...@cl...> - 2002-09-11 18:23:03
|
I found doing Pump message loop TestCoopLevel Lock/Load/Unlock Between each resource and handling errors accordingly got rid of these ctrl+alt+del crashes on nvidia hardware. I may just have been lucky however. Andy @ Climax Brighton -----Original Message----- From: Javier Arevalo [mailto:ja...@py...] Sent: 11 September 2002 18:39 To: gam...@li... Subject: Re: [GD-Windows] Windows paints my window! [I moved most of this stuff to the DXList] Rich <leg...@xm...> wrote: >> There is an issue between some drivers and the D3D runtime which >> will cause D3D to return invalid pointers when you lock resources. >> This is apparently not fixable in the drivers, so it has to be >> worked around in the app. > the workaround was to be more picky about when and where you call into > Windows. So, bottom line: should PeekMessage() be called or shouldn't it while loading video resources? We're going to try commenting it out (since the window white effect was successfully removed by the hollow brush) and see if it happens less often. Javier Arevalo Pyro Studios ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ Gamedevlists-windows mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=555 |
14 messages has been excluded from this view by a project administrator.
