Windows 7 and Bf2Editor

[Wilkinson]

Does it work?
Any flaws?

Just want to make sure before I upgrade.

[l3etrayed91]

As far as I a aware BF2Editor only works with windows XP. At tleast that is what I remember the error message saying when I tried to run it with Vista.

[Rudd]

you can run it with vista via running in compatibility mode with XP, but its much harder to remove if you want to uninstal.

Win7 has a XP mode, so I guess it runs ok?

[Robbi]

Works fine wilkinson, ran it on the RC build 7100 and now on the x64 Pro version, no worries, and considerably less buggy than Vista.

Do as Rudd says with the installer aka run it in XP mode.

[dunem666]

this is good to know guys, gonna upgrade tommorow,

however....

How does bf2editor run with dx 10 / 11? seems to only work with dx 9 even with xp compat

any ideas?

[bad_nade]

How does bf2editor run with dx 10 / 11? seems to only work with dx 9 even with xp compat

BF2Editor has no knowledge what so ever about DX10/11. It will run fine, but it cannot use features beyond DX9.

[dunem666]

so guys....

Ive upgraded to windows 7 64 bit like i mentioned in my previous post...


BF2editor loads up fine, but when i load my map, which is 100 % working, i get nothing but continuous dump crashes,

the dump files says something about C:\WINDOWS\SYSWOW ?!?

i also have plenty of error's with my Pickup insurgent kits, they wont load anymore in editor... had to remove chinook, caused a nasty lag and collision fault... also the same with 3 static crates?!?!?

WHATS GOING ON??!?!?

i have everything unzipped and setup no different to before....

im at a real important stage of completing my map also and cant waste time reverting back.

any suggestions?

cheers guys

dunem666 (Baghdad Mapper)

[bad_nade]

I haven't yet set up my editor for PR 0.9 so I can't really help at the moment.

"C:\Windows\SysWOW64" maybe? It's a folder where 64-bit Windows keeps 32-bit versions of the system components for backward compatibilty. BF2Editor is probably trying to find a file/dll/etc. which is not there for some reason. Error message probably refer to a file that's actually in "C:\Windows\System32" folder (which despite its name holds 64-bit versions of the operating system). Sometimes finding these files and simply copying them into "C:\Windows\SysWOW64" is enough to sort out these kind of problems.