Construct crashes frequently, won't load most .cap files.

Whenever I load up construct, it tends to crash.

Also, I cannot load most .cap files. It crashes the program.

Any idea why this might be occuring?

What's your video hardware and system specs?

Here's a quick summary. If you need more info, I can print a system scan out.

Vista 64 bit Home premium

2 Nvidia 8800 GT 512mb graphics cards running SLI

Intel Core 2 Quad CPU Q6600 2.40 ghz

XFX Nforce 780I SLI intel socket 775 ddr2 motherboard

4 gigs of ram ddr2

2x 250g sata hard drives

Here's a quick summary. If you need more info, I can print a system scan out.

Vista 64 bit Home premium

2 Nvidia 8800 GT 512mb graphics cards running SLI

Intel Core 2 Quad CPU Q6600 2.40 ghz

XFX Nforce 780I SLI intel socket 775 ddr2 motherboard

4 gigs of ram ddr2

2x 250g sata hard drives

64bit Windows... lulz

Let's emulate 32bit software and run slower than 32bit Windows... yay!

At a random guess, I'd blame that.

~Sol

64bit Windows... lulz

Let's emulate 32bit software and run slower than 32bit Windows... yay!

At a random guess, I'd blame that.

~Sol

I don't think that's the problem. AsparagusTreavor mentioned a while back in this thread that he uses 64-bit Vista, but he hasn't mentioned any problems with it.

I have no idea why this would happen. Has it always done it?

Did you run the entire installer?

64 bit windows is the only version that will recognize 4 gigs of ram, unfortuantely.

To be more specific, when I attempt to load most .cap files I get a runtime error. It claims an abnormal program termination.

Other than that, it simply frequently shuts down for no apparant reason when I use it, or simply stops respoinding.

I reinstalled it, and I am having the same issues. Is there anything I can do to give you more info to assist in resolving this? This program looks excellent, and I'd very much like to start using it.

I really can't say. It sounds like something unique in your setup is preventing Construct from running, because it works for everyone else. All I can think of to do is try redownloading it (in case the file was corrupt), try other older builds (see if theyre the same), or to as a last resort download the source and run it through the debugger to see what really is happening. That's a lot to ask of a non-programmer though...

32bit Windows still recognises 4gb of RAm, it just won't use it for Windows... though it does use it as a ram drive for other programs that are built to support extra memory.

Anyway, your other option is to dual boot your PC with another OS like Windows XP or a 32bit version of Vista... then you can just pick which OS to boot into on startup. The only other thing I can suggest is to make sure you have the latest BIOS revision and Chipset (INF) Drivers for your motherboard. It could be something simple in the memory paging or data precache pipelines... new drivers and/or bios may fix the problem.

You aren't overclocking or anything? This may have some effect if you are... the only last thing I can think of is to disable SLI and see if it's any better. When I run SLI with Construct for some reason it seems a little more unstable as well... though not as bad as what you are reporting.

~Sol

32bit Windows still recognises 4gb of RAm, it just won't use it for Windows... though it does use it as a ram drive for other programs that are built to support extra memory

No, you really can't use the last 500mb/1gb of RAM in a 32 bit system - the actual memory addresses are assigned to VRAM, other system devices, etc. so any physical RAM you install beyond this point will go completely unused.

> 32bit Windows still recognises 4gb of RAm, it just won't use it for Windows... though it does use it as a ram drive for other programs that are built to support extra memory

>

No, you really can't use the last 500mb/1gb of RAM in a 32 bit system - the actual memory addresses are assigned to VRAM, other system devices, etc. so any physical RAM you install beyond this point will go completely unused.

Yeah it's a limitation of 32 bit architechture. When I said it uses it as a ram drive, I meant it will allocate it to things like virtual memory, vram, and system cache. It still "uses" it, but Windows doesn't "use" it.

Also, I have experienced lots of crashes with opening cap files on my big rig, but only when SLI is enabled. If I turn SLI off, it will open without a hitch. Weird.

~Sol