TopoFusion support forums

Archived  - Use Search => Archived Support => Topic started by: hardwire on April 25, 2005, 06:05:12 PM

Title: Access Violation-Make Network
Post by: hardwire on April 25, 2005, 06:05:12 PM
I know I have done this fine on previous versions. But.... I have made 3 tracks in an area and wanted to use the MAKE A NETWORK option. It runs then errors about halfway with the following error...


I have tried using each of them individually but it get the same error??
LOG:
TopoFusion 2.50 Log Begin
Windows Major Version: 5
Windows Minor Version: 1
Windows Build Number : 2600
Windows Platform ID  : 2
<snip>
recreateVideoMemoryPool: Finishing up

Caught Exception:
 Function: ManagerThread (Network)
 Exception: Access Violation
Title: Access Violation-Make Network
Post by: alizhan on April 26, 2005, 06:21:42 PM
Yeah, I've had this problem off and on as long as I remember. Same spartan log message as you get. I find that restarting Windows (not just TF, the whole computer) sometimes helps, but not always. Some tracks just won't convert. I'll send one in.
Title: Access Violation-Make Network
Post by: hardwire on April 26, 2005, 06:58:39 PM
This evening I went back to my old tracks to make sure I was not dreaming and all of them work fine ... ??? So it sounds like it is not the version.... ???
Title: Access Violation-Make Network
Post by: hardwire on May 01, 2005, 10:37:13 AM
Hmmm I may have discovered a repeatably problem...  ??? Looks like it is related to the first few track points.... This first picture gets the error...

and when I move the first point down so it does  not cross the trail like this...

It makes a network just fine without a problem....
It seems to be related to just the beginning of the trail.... Because, and don't laugh  :p  SInce I was having problems locating this cache, I went in circles a few times ... this one one makes a network just fine...
Title: Access Violation-Make Network
Post by: tdcarter on May 02, 2005, 08:41:36 AM
I also got the violation... but I didn't restart winders, just TF.

Ran the same network trails again, and also got it.

I tried moving the top listed track down the list (remove & re-add), it was actually right in the middle of the network, and re-ran and it worked.

I looked at the TF log, and it shows a DirectX error right after catching the violation.. speciafically:

DirectX Error [2405]: Access to this surface is being refused because the surface is already locked by another thread.

I saved the log if anyone wants it?

TC
Title: Access Violation-Make Network
Post by: Alan on May 02, 2005, 04:53:59 PM
Scott will have to take a look at this, he wrote all the network code.  He's out riding the Arizona trail currently.  He should be back in a couple weeks.
Title: Access Violation-Make Network
Post by: hardwire on May 02, 2005, 05:10:23 PM
Gosh, no problem....   :D  I wish I was out there!   Wonderful tool!
Title: Access Violation-Make Network
Post by: Jimt on May 03, 2005, 10:23:45 PM
I read this post today, as I was having exactly the same issues. I was reassembling a single loop from a series of walks that covered much of the same ground. So I had to cut out lots of duplicate tracks resulting in occaisional breaks in the original loop. Before using the "make network" to stitch these segements into one continuous loop, I went back to make sure that no lines intersected. All the segments were touching, and there were not cross-over points. But still "make network" barfed, as described in the previous posts. Something is too unstable in this function...:(
Title: Access Violation-Make Network
Post by: tdcarter on May 07, 2005, 05:21:09 PM
Try changing the order of them (segments) in the list.

Worked for me.... least, this time.