WED Crash....

[Peter T.]

Hey guys, i don't know why but everytime i save and then export scenery...it crashed, i dont know what cause this to happen but it really annoying.

[karingka]

This means there is an error with a facade you created. Delete recently created facades, and try exporting again.

[Peter T.]

it also seemed earlier...i cant create .pols with any curved edge....

[chris k]

POLs cannot have bezier curves, Known issue.

 

- CK.

[JohnMAXX]

Peter may also be the ground_details.pol I tired cutting holes into......I would delete that first and try 2 different polys for that particular layer......

[Redfisher]

WED is a total PITA to work with right now.

[ryancz]

It crashes way too much.

It needs to give a warning of why this won't work, instead of trying to do it and crashing.

[chris k]

It crashes way too much.

 

Huh? There's only EVER 2 conditions which makes WED crash: (From my own experience only...), and the crashes are predictable and repeatable:

 

1. You run out of Memory. Same problem that X-Plane 32 has. Easily done when zooming way out and you have orthophotos loaded.

 

2. You Export a Bezier Curve on a POL.

 

Other that that - I have never experienced any kind of "random" crash at all. WED has been Rock Solid for every one of my projects since January. (aka once you know what contributes directly to the only 2 reasons it  crashes - if you simply avoid them, then I can use WED for hours and days and weeks without a single crash). Heh.

 

- Ck.

[ryancz]

Missing objects (actually missing, and some even when they're there), and apt.dat error, of the top of my head.

There's many I have gotten.

[chris k]

Sorry to hear you're having "missing object" and "apt.dat" error. ( can you elaborate on these?)

[ryancz]

I've been bedridden all day, sick.

I'll post a shot of the missing object error.

Any apt.dat error is where something is wrong in an apt.dat. (ie: two runways with same designation) when imported, this apt.dat crashes wed.

[Sgt R Lee Ermey]

Mine crashes after I add a 13th orthophoto.. I can't seem to break past 13 for an area. 

 

Starting to tick me off, there has to be a way around this, others have done hundreds. 

[Redfisher]

Mine crashes after I add a 13th orthophoto.. I can't seem to break past 13 for an area. 

 

Starting to tick me off, there has to be a way around this, others have done hundreds. 

 

What size are your images?

[chris k]

So- break it up into smaller operations. You can only load a few TIFFs into RAM before you end up filling the 32-bit memory space in WED.

 

So....

 

1. Load 2-3 TIFFS

2. Make Draped Polygons out of them

3. Delete the TIFF Overlay in WED (as it's now a .POL)

4. Convert those TIFFs that are now in .POL files to PNG

5. Convert PNGs to DDS

 

Repeat; and you'll end up with a whole bunch of DDSes in WED which occupy very little RAM when using WED.

 

Basically, youre running into the 32-bit memory limit on WED. Same thing would happen if you loaded those TIFFs directly into X-Plane 32bit (if there was some method).

 

....TIFFs can be absolutely HUGE.

 

- Ck.

[Sgt R Lee Ermey]

Yeah I had came to that conclusion as well.  I realized this is a 32 bit app after I tried to force it to quit and realized it would be a mem issue.  I will just have to only do 3-4 at a time and then switch them over to png. 

 

Thanks though