Hi,

I uninstalled my earlier version of A7, downloaded the new version, shut off my antivirus software to keep it from interfering with the installation, and installed 7.6. I made sure that my keys were in the new install. When I try to run, the acklog reports that my wrs files are successfully located and my paths are listed, then SED dies with and error dialogue:

"The instruction at "0x..." referenced memory at "0x..." (same location) The memory could not be "read"

Any ideas? Thanks for your time!

Although I don't know your project and can't tell why it crashes, there are many suggestions what to do in such a case on the following pages:

http://manual.conitec.net/debugging.htm

and

http://manual.conitec.net/bugs.htm

Once you've found out more about the problem, you can post here details about it - then other users can help you.

BTW, you don't need to uninstall the earlier A7 version before updating. Just installing the update in the Gamestudio folder will suffice.

Thanks for the references JCL

Despite my efforts, I'm still baffled.
I discovered that I cannot "update textures" or lights in WED, but I don't know if that's connected.

If I start a project from scratch it runs, but if I take my current project and strip everything out of it so that it is completely empty and I replace the level script with a fresh script, it still crashes. I get no warnings, or logs.

After reading the 7.6 update posts, I tried to make sure all my paths were .\blah instead of .\\blah.

It sounds like DDS files are broken right now- I use them in a couple of places, but I thought it was strange that A7 crashes even when I don't have any objects in my scene.

My graphics drivers are all up to date. DirectX is up to date and in "Retail" mode.

Sorry that I haven't been able to provide any more information. I don't have enough time to get this to work right now, so I'll just revert to a prior version.

Just out of curiosity, has anyone else not been able to get their projects to run, or am I the only one?

Thanks A7 family!

You are not the only one. Almost anyone programming games or programming anything ecounters such problems from time to time.

When you know that the problem is your level and not your script, the next logical step is starting only your bare .wmb level without any script or entities. For this you can just move the .wmb file into a separate folder. If it then still crashes, it's something in the wmb file. It's then probably a damaged texture file or something like that.

Hey JCL, I apologize- my question about being the only one does sound like trollish rhetoric. It feels like I've seen a number of posts about sticking with older versions and I thought I'd pry a little to gauge how people were dealing with the update. I don't mean to discredit A7 in any version; it has been adequate for all my needs thus far given the appropriate effort!

Thanks for the instructions on how to get our levels working. I'll get it to work eventually. It is a little peculiar to me that my levels didn't work when I upgraded, but when I went back to 7.5 they worked fine as before. If it's not my script and not the level content, what else can it be? Does the new version read assets differently? I'm not in a hurry since I can work with what I've got.

Often, damaged texture or entity files cause errors only under certain circumstances, such as with a certain version or in a certain level. Eliminate the entities as suggested and try again. Of course, it could also be an engine bug - but then it would since long have been also encountered by other people.

With the simple methods suggested, finding where a crash happens - in the script, the level, an entity, or the engine - is normally a matter of 10 minutes and much faster than posting or discussing here.

That genuinely hurts. Please don't assume we haven't made the effort. Look at the time between posts in this thread- significantly longer than 10 minutes, no? Surely I haven't been idle all the while. In any case, I'm grateful for your help.

What is crashing in your level, is it the WMB file or is it an entity?

If its an entity you can try to open it in MED and save it again, this will fix a damaged byte or so if the file is not completely broken.

If its a damaged file you should also check why its damaged, it could be a virus or a harddisk fault!