Game Development Community

Collision and link point editor bug in demo - RESOLVED

by Josh Kimmelman · in Torque Game Builder · 05/03/2010 (9:17 am) · 55 replies

Hello,

I'm running the 2D demo v1.7.5 on a Windows XP machine. The collision editor and the link point editor do not appear to be functioning correctly. The editor window pops up, but I cannot add, subtract, or edit points. Each point I add becomes a giant grey block that completely obscures the source object. Has anyone else had this problem?

About the author

Recent Threads

Page «Previous 1 2 3 Last »
#1
05/04/2010 (10:20 am)
i also confirm this on my full version too. Mac and Windows 7 on my macbook pro
#2
05/04/2010 (11:20 am)
Are you sure you're not running 1.7.4 by mistake? This was a bug we discovered during QA and it was fixed. I just confirmed that the uploaded download is the correct version with the fix on all platforms.

Moved to TGB.
#3
05/04/2010 (2:37 pm)
i am not runing 1.7.4 i am running 1.7.5 and i installed it on my fresh Snow leopard and Windows 7 machines ( i even tried it on a virtual machine) that bug is there, where it wasnt in 1.7.4

i have a macbook pro early 2009 model (pynren)
#4
05/04/2010 (3:06 pm)
I am having the same issue. When I bring up the collision editor I see nothing. I can't add new points or change existing ones. If I remove all points then I can see my spite but I still can't add new points
#5
05/05/2010 (6:02 am)
I am definitely running 1.7.5
#6
05/05/2010 (12:08 pm)
Ah, my bad, I actually you were referring to a different bug with the linkpoint editor originally. I've confirmed this as a bug.

TGB-501
#7
05/05/2010 (6:20 pm)
So when will this bug be fixed? I am trying to evaluate the engine and at the moment my project has ground to a halt.

Is there anyway around this bug? I really would like to continue using the software before my trail runs out.
#8
05/05/2010 (11:27 pm)
I have pretty much the same problem as James.

Once I first experience it with 1.75, I started working with 1.74... But then I accidentally opened the project in 1.75 and it is now un-open-able in 1.74, so I have to work with 1.75; but obviously I can't

Any new progress found with the bug?
#9
05/06/2010 (12:31 am)
Some kind of response would be nice. I just want to know how long I am likely going to have to wait before I can continue using the product.
#10
05/06/2010 (1:09 am)
Hello,

I have the exact same issue using Torque 2D 1.75 (Full Version w/out Source) too.
I should mention that I had 1.74 installed and the Collision Editor was working fine for it too so I suspect it's an issue with the latest build.

Here is relevant parts of my DXDiag in case it contains any useful information.

------------------
System Information
------------------
Time of this report: 5/6/2010, 18:06:38
       Machine name: -
   Operating System: Windows Vista™ Ultimate (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)
           Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
       System Model: P5Q-PRO
               BIOS: BIOS Date: 06/12/08 01:01:23 Ver: 08.00.14
          Processor: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (4 CPUs), ~2.4GHz
             Memory: 4094MB RAM
          Page File: 2117MB used, 3027MB available
        Windows Dir: C:Windows
    DirectX Version: DirectX 10
DX Setup Parameters: Not found
     DxDiag Version: 6.00.6001.18000 32bit Unicode


------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)


---------------
Display Devices
---------------
        Card name: NVIDIA GeForce 9800 GT 
     Manufacturer: NVIDIA
        Chip type: GeForce 9800 GT
         DAC type: Integrated RAMDAC
       Device Key: EnumPCIVEN_10DE&DEV_0605&SUBSYS_829C1043&REV_A2
   Display Memory: 2287 MB
 Dedicated Memory: 495 MB
    Shared Memory: 1791 MB
     Current Mode: 1680 x 1050 (32 bit) (60Hz)
          Monitor: Generic PnP Monitor
      Driver Name: nvd3dumx.dll,nvd3dum,nvwgf2umx.dll, nvwgf2um
   Driver Version: 7.15.0011.7813 (English)
      DDI Version: 10
Driver Attributes: Final Retail
 Driver Date/Size: 10/23/2008 14:47:58, 8458240 bytes
      WHQL Logo'd: n/a
  WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-4545-11CF-766D-97A202C2CA35}
        Vendor ID: 0x10DE
        Device ID: 0x0605
        SubSys ID: 0x829C1043
      Revision ID: 0x00A2
      Revision ID: 0x00A2
      Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C ModeVC1_B ModeWMV9_B ModeVC1_A ModeWMV9_A 
 Deinterlace Caps: (removed)
DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled

#11
05/06/2010 (6:44 am)
@James,

If this is the only issue holding you up from purchasing the engine, I wouldn't worry too much. It is frustrating to not hear back though. If you do opt to pick up TGB, you could always download 1.7.4 instead of 1.7.5 since this problem doesn't seem to appear on there.

There's usually a little more help on the forums but some people are on vacation and/or having some family things that are keeping from helping out.

I've tried to replicate your problem on a WIndows 7 and Windows XP 32 bit computer and can't... What video card do you have - it could very possibly be remedied by a setting change. Do you have any custom XP theme running?

Patrick
#12
05/06/2010 (6:50 am)
Thanks for the reply.

http://i218.photobucket.com/albums/cc24/manazeal/screencap.png

This is a screen shot of the problem that someone else posted in another thread.

My graphics card is an Nvidia 9600gt, no custom theme, no special drivers. Just a vanilla windows XP install.

It seems the issue is a bug and that other people are having it. Hopefully it is something that can be fixed with a few tweaks on my end. So far the engine looks great for what I want to do. However I was wondering how versions and patches work after purchase. Do I have to buy a new version of the engine every time one is released or is there some kind of upgrades system. Also if a known bug is patched, will that be released for free or will it just be added to the next version of engine.

Thanks for your response.
#13
05/06/2010 (8:10 am)
@James
I apologize that your evaluation of the engine has hit a rocky spot. While there were only a few bugs that slipped through on the final build before it went out, they were some big ones and they've affected the Binary version more than the Pro.

I don't have a timeframe for when the bug will get fixed, but it will happen quickly. Currently we're gathering up the reports of the bugs that the community found and then we'll assign resources to them accordingly.
#14
05/06/2010 (8:41 am)
Thanks for the response. Is there a way I can download a trail version or 1.7.4

I really would like to play with the engine some more before I commit to buying it.

EDIT: I have found a 1.7.4 trail version online. It does not have the bug. I will use this version until the bugs are fixed. Thanks :)
#15
05/07/2010 (1:00 pm)
Same issue here - TGB 1.7.5 on OS X 10.6.3
#16
05/07/2010 (2:59 pm)
At this rate, it sounds like it's not us but the patch.

Has anyone hear from GG or anything about a fix?
#17
05/08/2010 (8:58 am)
I submitted a bug report for my system... hopefully they fix this soon as i am taking a class and have purchased the version 1.7.5 already. As of yet it is not stopping me... but real soon it will.

(windows vista, ati radeon 3200.. 64 bit) no customizations.. factory built hp device.
#18
05/09/2010 (7:53 am)
@George Fairs, i told that to Michael Perry the other day in the IRC. But he said he wasn't aware of this.
#19
05/09/2010 (2:25 pm)
While it's appreciated, there's no need to continue submitting bug reports on this one. It was confirmed and logged already.
#20
05/09/2010 (4:29 pm)
I think people would like to know when it will be fixed.
Page «Previous 1 2 3 Last »