Hi,
Perhaps someone knows a solution for my problem. It is mainly 3dgamestudio related.
3dgamestudio: extra 7.07
driver: latest ATI
card: x1650
My Problem:
I do a lot of programming in sed and have to start the engine (with the run button) very often. After ca. 10 times the window (1024x768x32) is only displayed in 640x480x32 only. Sometimes the engine freeze the computer for 10 or more seconds. After this time it runs without problems. But I can be sure, that the engine is only diplayed in 640x480 window mode next time.
And the fullscreen doesn't work at all.
I have minor problems with other applications too. Some direct3d crashs of two strategygames. (But this games work, when i restart them).
Thank you for reading (and perhaps answering)
MfG
Patrick

AFAIK, reinstalling it is your first option here
Btw, which OP do you operate on atm ??

Thanks in progress

Frazzle

About freezing, I know this.
It happens every time, when I run a script after playing several 3d games based on different engines.
Maybe it's because computer needs time to initialize new engine.
Screen gets black, but computer shows that its working about something - if I run a task manager before, perfomance diag shows maximum activity for those 4-7 seconds.
About fullscreen - try this:
Code:

---

video_window(nullvector,nullvector,1,"myApp");
video_switch(8,0,1);

---

this normally works.

This is common for me as DX is called time and time again but never purged when shut down.
Even with a memory manager this happens so I get about 10 to 15 runs before I have to restart to purge and go hard out again.

No real solution yet but as you say, it generally happens with GStudio, mind you, its the only editor I have worked with for over 4 years so I cant say that it is inherently the faullt of GStudio hence the note on DX (above) related apps that are called often.

nope, it's a SED bug i think.
it has nothing to do with the amount of times you run it, nor the size of the screen whatsoever.
this happens after you made a script error...
whenever you made a mistake (or accidentally ran the wrong file, not main but some other file that should be included) it gives you a crash, says something along the lines of user error, and then simply wont run ever again above 640x480.
i experienced this a lot as well XD and it sucks!

regards,

Sorry for that, I can`t help you I`m a total beginner.
And sorry for my next (maybe stupid) question.
I think I have a similar problem, with drivers (or something else):

- I have installed GS7 today (I can hear you laugh...)
- made a simple scene in WED
- pressed: build (it shows compiling screen with all ok)
- pressed: run
- that automatically started LITEC-7 (and again no mistakes reported)
- after that it showed a screen (engine, i suppose) but just for about 10 milli seconds and then closed it.

- I tried with a different options of (de)activating DirectX in Preferences.
- and so i tried many times - and always the same.

So, is this something familiar to you? Or somebody?
Thanks...

Hey, thank you all.
It helps to know that I am not alone

@frazzle: I use Windows XP edit: äh sorry I've red os I'am not so good in this shortcuts sorry I don't understand OP and atm <shame>
processor: AMD 3700+ 1GB ddr1 ram

@vadim647: I tried and tried, but until now I wasn't able to reproduce the error I will test your solution if the error apears again.

@nems: That's possible, but i've never experienced that problem with A6. I wonder if there is a way to reset the hole directx/driver or what ever

@helghast: It's possible to. But I wasn't able to reproduce the error with this "method" If it is an engine problem, there must be a way to reset the engine.

Thanks for replies.

@vanste:
Do you use a script? Which operatingsystem you are using?
Check your DirectX version (it has to be 9) with the dxdiag (execute -> dxdiag)

Im running A7 latest update and use both SED and WED and get the same results, though not with the window size, usually a memory access problem.
This also happened for me when using A6 previously.

@TheThinker:
Thanks man, yes, it was just a problem with a script (not using it...)
Regards