Bug Reports / [ANNOUNCEMENT] Bug Report Template

Author
Message
MadLad Designs
GameGuru Master
17
Years of Service
User Offline
Joined: 4th Nov 2006
Location: Look outside......
Posted: 29th Oct 2013 19:15 Edited at: 14th May 2014 00:44
When creating a bug report it would be a lot easier for TGC to get to the root of the problem quickly if you could provide the following information as fully as possible (Here's an example):





----------------------------------------------------------------------------------

OS:- Windows 7 Home Premium 64-bit SP1



CPU:- Intel Core i5 3330 @ 3.00GHz



RAM:- 8 Gb DDR3



GFX Card:- 2048MB NVIDIA GeForce GTX 660



FPSC-R Version:- Beta 1



Error Report:- When exiting out of a test game and coming back to the editor, the Player Start Marker is orientated in a completely random direction.



Is it repeatable? Yes



If so, how? Placing the Player Start Marker, testing the game, exiting the test game and coming back to the editor.



[screenshots / video of bug if possible]

----------------------------------------------------------------------------------



Q: How do I get all my computer information?



A: There is a free program called 'Piriform Speccy' that will give you a complete specification of your machine, you can download it from http://www.piriform.com/speccy. I use it constantly and is what I use when creating bug reports.





Check out the [FPSC Reloaded FAQ]!



Also check out my YouTube Gaming Channel: /user/MadLadDesigns
Scene Commander
Support Manager
15
Years of Service
User Offline
Joined: 3rd May 2008
Location:
Posted: 5th Nov 2013 18:34 Edited at: 5th Nov 2013 18:34
Sound advice Madlad.





Can I also remind everyone that it is often helpful to supply a DXDIAG following the instructions in the official bug reporting thread, and if applicable, a FPM showing the issue.



Thanks,



SC

Bringing you games since 1981!
Green Gandalf
19
Years of Service
User Offline
Joined: 3rd Jan 2005
Location: Cornwall UK
Posted: 5th Nov 2013 20:32
Quote: "Can I also remind everyone that it is often helpful to supply a DXDIAG "




On my system it wouldn't be helpful because DXDIAG only reports the Intel GFX card not the Nvidia one. This might apply to anyone using the so-called Nvidia Optimus system.



I haven't yet found a way to force or trick DXDIAG to report the existence of the superior Nvidia card.





Powered by Free Banners
Titantropo
GameGuru TGC Backer
12
Years of Service
User Offline
Joined: 1st Aug 2011
Playing: Diablo III
Posted: 1st Dec 2013 14:45
Do I need to provide all the info from a problem already identified? (And it was said the problem was already solved, but I guess not.)



How do I get a dxdiag file?

Here, there and everywhere.
PM
The Rev
20
Years of Service
User Offline
Joined: 26th Apr 2004
Location: Mississippi USA
Posted: 2nd Dec 2013 05:08
amd athlon dual 64X2 processor

windows vista 32 bit

3 gig

asus radon hd7770 2 gig



happened on beta 1003 this is what my model looked like in the test run mode

also in beta 1002 i could have multi textures like in the old fps by taking the texture name out of the the fpe file and the x file info would work it worked in beta 3.002 but in 3.003 this what i get in beta 3.003 the bug one is the 3,003 bug file the second is the beta 3.003 test with the muti that's editor and testsmode2
PM
Titantropo
GameGuru TGC Backer
12
Years of Service
User Offline
Joined: 1st Aug 2011
Playing: Diablo III
Posted: 4th Dec 2013 02:51
Anyone?

Here, there and everywhere.
PM
Scene Commander
Support Manager
15
Years of Service
User Offline
Joined: 3rd May 2008
Location:
Posted: 4th Dec 2013 09:59 Edited at: 4th Dec 2013 10:04
@Titantropo



This thread is to outline the bug reporting process which is why your post was missed.



If you have a bug that was reported as fixed but is still happening for you, and has a thread, please post on that thread.



If that thread is

Login to post a reply

Server time is: 2024-04-27 00:47:44
Your offset time is: 2024-04-27 00:47:44