Export Bug in 2.984

[red-haze]

export at 4000x3000 works in non-beta but hangs in 2.984 beta. running on Dell Inspiron 9100 mobile radeon vid and 2 gig of system ram.

good news is that with the beta I can run at full screen but non-beta smears tiles at full screen resolution (1920x1200).

beta exports at lower resolutions.

once, the beta exported and din't hang but output a pic that was oriented vertically with big black bars on both sides.

why use 4000x3000? ah, have a printer that can go to 19"x13", and have access to another printer that does 4'x3'. have used topofusion to map our local trail system(s) and everyone wants a map '>
exporting is the best way to get to the bigger print sizes.

thanks for the great program and its always getting even better!

bob

[Krein]

I had a chance to look at this today.  I had noticed some problems with large exports on my system.  I definitely don't want the beta to be a downgrade in this category.

I just put out 2.985 that uses a little different method (perhaps slower) of exporting large images.  Please download it and give it a try.

I was able to get 8000x8000 going.  Before anything over 4096x4096 would fail.  If this version still doesn't work, can you post your log file from a failed export?  Thanks.

[Krein]

Also, thanks for the report about no smearing!  Great to hear that problem cleared itself up!

[red-haze]

just tried the new beta, still failed but now the exception handler pops up, I filled in my email and sent the log file, a couple of times '>

thanks again!

[red-haze]

more info.
exception handler comes up on all export resolutions, not just 4000x3000. tried using "current" detail setting instead of "max". failed there too.

rebooted (cause it's good for windows :)O
and still couldn't export anything.

log file (incase it didn't get emailed with the exception handler)
TopoFusion 2.985 Log Begin
Setting internet settings..
GPSMaster.ocx, Initialize...
Windows Major Version: 5
Windows Minor Version: 1
Windows Build Number : 2600
Windows Platform ID  : 2
Windows CSD Version  : Service Pack 2
Initializing Winsock
Initializing Direct3D
Direct3D : Driver "ATI MOBILITY RADEON 9700" (ati2dvag.dll)
Direct3D : Display properties - 1920x1200, Format=22, Refresh = 60
Free Texture Memory = 155189248 bytes
Direct3D : Hardware supports rendering after flips (is relatively fast)
Direct3D : Hardware supports at least DX7
Direct3D : Hardware supports at least DX9
Direct3D : Hardware supports anisotropic filtering.
Direct3D : Hardware supports ALPHA pixels in textures.
Direct3D : Hardware needs textures sized on powers of two.
Direct3D : Hardware doesn't support antialiased lines.
Direct3D : Hardware supports alpha blended lines.
Direct3D : Hardware supports textured lines.
Direct3D : Maximum Texture Width: 2048
Direct3D : Maximum Texture Height: 2048
Color Info : Sizes : R=8, G=8, B=8
Color Info : Shifts : R=16, G=8, B=0
Direct3D : Hardware supports color conversion.
Creating Surfaces
Creating Resource Tiles...
Creating Sprites
Successfully Created Surfaces
Initializing Memory Pool
Total Physical Memory: 2146652160
Physical Memory Free: 1784578048
Memory Load: 16 percent
Tile Cache Size = 1000
Free Texture Memory = 149946368 bytes
Setting gbLotsOfVideoRam
Initializing Threads
Initializing Index File
Sorting Index File.  Number of entries: 34201
Time to sort index file: 0.03 seconds
Initialization Complete

DirectX Error [.\master.cpp:6261]: D3DERR_NOTAVAILABLE

Caught Exception:
 Function: CGPSMasterCtrl::OnDraw
 Exception: Access Violation


--# FV EIP----- RetAddr- FramePtr StackPtr Symbol

  0 .V 10030f39 1002dadb 0012e2fc 0012e2a0 DllUnregisterServer +143145 bytes    Sig:  DllUnregisterServer
    Decl: DllUnregisterServer
    Mod:  GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: -exported-, file:

  1 .V 1002dadb 1000e780 0012e388 0012e2a0 DllUnregisterServer +129739 bytes    Sig:  DllUnregisterServer
    Decl: DllUnregisterServer
    Mod:  GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: -exported-, file:

  2 .V 1000e780 00000000 0012e3c0 0012e2a0 DllUnregisterServer +1904 bytes    Sig:  DllUnregisterServer
    Decl: DllUnregisterServer
    Mod:  GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: -exported-, file:

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

[red-haze]

beta 2.986 just d/l and installed

export error now says
"Couldn't create surfaces for export. Try smaller sizes next time!"
at 1024x768

doesn't hang the program but it did turn the font onscreen of my waypoints black! Options it still had white and would reset to normal when I "ok'd" the options screen.

does export with settings all at "current"

hmmm
thanks
bob

[Krein]

OK, thanks for confirming what I was beginning to suspect.

I have to rethink how to do exports.  It might have to be limited to the maximum texture size (4096x4096 on most newer video cards) for now.

Hopefully I'll have a new version soon.

[red-haze]

installed 2.99beta, export works better on all presets except for 4000x3000. doesn't hang anymore but makes an interesting picture,
resized for smaller file size.

3D generation seems faster now, nice!

thanks
bob

ps, planning a mtb trip to Sedona this april, any recommendations?

[red-haze]

but wait, there's more!

I've been using a secondary monitor (19" LCD) with my Dell Notebook and using the "Extend my desktop here" to have two screens and have noticed some interesting things when Topofusion is in the secondary screen.

The gpx tracks fade out when it zooms out. At 1:1.49 the gpx tracks appear, at 1:1.90 they disappear. Occurs in both the release version and beta version. I've been planning on using the secondary screen (actually S-video out to 56" bigscreen TV) this Friday to present the Sedona area at a party of those who might wanna come along. Was hoping to show the sedona gpx files I've picked up from motionbased. may have to look for updated video drivers, tho its an older video card and checked for updates a couple of months ago.

anyways, thought the secondary screen behavior might be interesting to ya.

thanks,
bob

[Krein]

Quote (red-haze @ Jan. 17 2007,11:01)

installed 2.99beta, export works better on all presets except for 4000x3000. doesn't hang anymore but makes an interesting picture, 3D generation seems faster now, nice! thanks bob ps, planning a mtb trip to Sedona this april, any recommendations?

Thanks for the report back on this.  Your card's max texture size (from your log above) is 2048x2048.  I'm somewhat surprised it can go larger than that, but obviously not all the way to 4000.

In a future beta we will take care of this issue by doing multiple exports and stitching them together.  This should allow everyone to go larger even than 10k by 10k, which was previously the limit.

But for the time being we're stuck with how it works now.  I'm going to hold off on any major feature changes like this until this beta goes "public."

Re: Sedona.  I've cycled thousands of unique miles of singletrack in AZ, but never have I laid tire to dirt (rock) in Sedona.  So much to do, so little time.  I'm sure I'll get there soon enough.

[Krein]

Quote (red-haze @ Jan. 17 2007,11:43)

but wait, there's more! I've been using a secondary monitor (19" LCD) with my Dell Notebook and using the "Extend my desktop here" to have two screens and have noticed some interesting things when Topofusion is in the secondary screen. The gpx tracks fade out when it zooms out. At 1:1.49 the gpx tracks appear, at 1:1.90 they disappear. Occurs in both the release version and beta version. I've been planning on using the secondary screen (actually S-video out to 56" bigscreen TV) this Friday to present the Sedona area at a party of those who might wanna come along. Was hoping to show the sedona gpx files I've picked up from motionbased. may have to look for updated video drivers, tho its an older video card and checked for updates a couple of months ago. anyways, thought the secondary screen behavior might be interesting to ya. thanks, bob

Definitely sounds like a driver issue, esp. if it's doing it in both versions.  TF (from our side) does nothing different when stretched across multiple monitors.  To the programmers it just a really wide monitor.  So everything's on the driver side.

Seems like you could just do video out without 'extending' the desktop, right?