what's with the 'compatibility' mode?

ushere wrote on 5/9/2012, 9:00 PM

i understand the ability to use the modes, and thanks to a link how they work, what i'm unsure of is why they're needed?

in an attempt to make 11 as stable as possible i checked video card as tom suggested, and tried 'win7' compatibility - having written in another thread that it froze vegas on 'creating windows', this time i left it - it took almost 3 minutes for vegas to create the windows!!! i'm not sure whether this is a good sign or not, but it certainly isn't helpful when opening new instances ;-(

it would be great if scs could just explain what is going on and why we might need to use such workarounds.

btw. nvidia 550ti - 296.1

Back to post

Comments

Laurence wrote on 5/16/2012, 4:57 PM

No, just a current version of Windows 7 64 bit.

Laurence wrote on 5/16/2012, 6:11 PM

I'm going to start my day tomorrow in V11 and see how far I get. I would so love to be able to join the guys slamming those losers with the problems... ;-)

Tom Pauncz wrote on 5/16/2012, 7:34 PM

Steve,
I am using Aero themes. Why did you ask??

Tom

rmack350 wrote on 5/16/2012, 8:08 PM

Aha!...

That's very interesting. So compatibility mode fixes the crashing of your OFX filter dialogs, but evidently messes with the privileges of something needed for your render.

Remember, none of this is a "fix". It's a workaround. SCS still has to fix the problem.

Could you refresh everyone's memory? What were you rendering to when it crashed?

Definitely share that with support. Do they ever answer your tech support requests? They don't seem to respond to mine. I don't even get an automated email response.

Rob

rmack350 wrote on 5/16/2012, 8:13 PM

I am using Aero themes on both PCs. One crashes the OFX dialogs, the other doesn't.

I keep the Aero-ness very simple but it gives me a few features that are really useful (it's been a while and I can't remember what they are, just that no Aero was no good).

The one that doesn't crash uses an ATI RadeonHD 2400 XT card. The one that does crash uses Intel integrated graphics from the i5-2500 CPU.

Yes, Aero has access to a lot more system memory, even with a discrete graphics card. Sometimes it even uses that memory.

Rob

rmack350 wrote on 5/16/2012, 8:22 PM

I just noticed in the Answers section of the tech support page that there's a new post about compatibility mode.

https://www.custcenter.com/app/answers/detail/a_id/5097

Looks like someone stopped playing Duck and Cover long enough to post it. That's promising.

Rob

Steve Mann wrote on 5/16/2012, 9:22 PM

Laurence: Are you running Aero?

Aero is a GPU intensive feature of Windows 7. Try turning it off by selecting a simple Windows theme.

Laurence wrote on 5/16/2012, 9:46 PM

No, I'm just running a simple desktop.

rmack350 wrote on 5/17/2012, 12:21 AM

I don't think Aero affects the OFX dialog window crashes. I just checked it out with Aero off and compatibility mode off. OFX dialogs crash within about six adjustments.

I can't speak to Laurence's crashing renders. Maybe Aero is a factor there.

Rob

Laurence wrote on 5/17/2012, 8:40 AM

No Aero here. I get an "unable to write to protected memory" error and then it crashes. Running it as an administrator seems to bypass this error.

I get crashes not only with OFX effects, but with the new Sony titler. Going back to the old titler seems not to crash as much. Maybe the new titler is OFX.

Edit: I take that back. I can't render in compatibility mode with the administrator tab checked either. Same "can't write to protected mode memory" error then crash.

Going back to V11 683 "au natural". I'm going to just avoide OFX plugins and see how far I can get. The other day I couldn't make it through a V11 render like this, but that was with an hour and a half event. It would crash at different points midway partly through the render. Today I am working on a shorter project and may well be ok.