I just upgraded my Surface to W10 and tried to run CE, and am getting the whole "A problem occurred in initializing Direct3D. Hardware Acceleration maybe disabled, please run DXDIAG" message.

Anyone know of any fixes? I feel like I had this once before but am not quite sure what I did...

Sapien works however.
Edited by Masters1337 on Jan 26, 2015 at 09:48 PM

try downloading the latest version of direct x from the Microsoft web site

I guess we'll have to look beneath the surface to find this answer... hehe

(sorry had to)

run DxDiag, then read

Had to set it into Vista compatibility mode, W10 has an option to find a compatibility mode. But now I run in a psudo windowed mode and the settings reports me running at 0hz for my refresh rate and blank for resolution, trying to change the resolution makes me exception.

yeah, the technical preview. I wouldn't go from 7->10 though, but 8.1.... oh yeahhhhh

Just to let you know, CE worked fine on my machine after upgrading to Windows 10 from 7. As others stated, make sure you're update on you redistribution packs and sturf.

I didn't need to run it in compatibility mode either. Also for some reason Win10 broke OS and HAC2 working together. They'd work separately but together was a no go.
Edited by TailsTheGamer on Jan 27, 2015 at 10:46 PM

By update, they mean re-install the dx9 redist, surely?

Why can't all future win os updates revolve around custom edition???

I'm staying with win8.1.

That happened on windows 8 too.

That's why I don't update yet a lot of video drivers problems try to disable the visual effects.

I have Halo CE working fine on windows 10, just make sure you have it installed with the latest update.

Then make sure you modify the config file in the root folder to accept your graphics card (instead of it registering as unknown). Also OS and Hac are not compatible due to OS being updating in a different fashion.

OS worked fantastic, I must say, on Windows 10. HAC 2 however, just errors constantly, no way to run Halo with HAC2//

I seem to be running everything just fine. Just updated this week. No errors yet anyways.

Played through Evolved on Windows 10 for the first time.
T'was 'on fleek'

-
Edited by Crossbow SR on Jan 10, 2018 at 07:39 AM

Win10 + haloce and the hek worked fine for me. Just yesterday though I rolled back to 8.1

I just can't take the fact slide show flip rates have been capped at 1minute.

halo ce standard edition will no longer work on my surface too also running windows 10 as when i try to run the game it always says "please login with administrator privileges and try again".

I'm trying to run Halo CE on my PC with Windows 10 and I'm not getting any errors it just doesn't launch. I've tried running it in all the different compatibilities only one that made a difference was 640x480 resolution and it goes black screen and then back to desktop.

Any advice?
Edited by IWannaBeATiger on Aug 13, 2015 at 03:20 PM
Edited by IWannaBeATiger on Aug 13, 2015 at 03:24 PM

Ya.

> Create a shortcut from the actual Haloce app to your desktop.

> Right click on the shortcut your created for halo and select "properties"

> Inside the properties window move to the shortcut tab and look for the "target" dialog.

> Now inside the "target" field should be this address:

"C:\Program Files\Microsoft Games\Halo Custom Edition\haloce.exe"

> Now you need to modify the address by adding the -safemode command line.

> Basically it should now look like this:

"C:\Program Files\Microsoft Games\Halo Custom Edition\haloce.exe" -safemode



> Hit apply and okay run the shortcut, if halo boots up correctly you may notice alot of features will have been disabled, this is not an error it's just inherent of what -safemode does.

> If halo booted up properly close halo then run halo again without using the safemode shortcut and it should in theory work correctly report back.

How would you go about modifying the config folder to accept the graphics card?

hay read this about win 10

http://www.computerworld.com/article/2975004/microsoft-windows/4-overblown-windows-10-worries.html

Windows 10 can't even stop people from pirating Windows 10. How the heck did people believe it could stop other pirated software?

I'm honestly conflicted whether to keep 10 or not.
There's no reason for me to change, but I do feel more comfortable on 7.
All that noise about Win 10 is pretty annoying too.

Idk how you can deal with the pace of your desktop slide show being restricted to 60 seconds.

Switch bak 2 7 or 8 m8.

Hold down the Ctrl key when you double click on the halo executable or shortcut.

Then locate the vendor ID assigned to the graphics card. (highlighted below).


Next navigate to your root folder and open the config file. (back it up in case you mess up)


Next navigate to the correct category of your graphics card vendor.



Once found go to the bottom of the list within it, and enter the Vendor ID (highlighted above) along with the name of the gfx card. (in theory you can name it whatever you want).


Follow the format, save and now your gfx card will be recognized by the game. However make sure in your gfx control panel halo ce is using it over a less powerful one (if you have 2 or more cards)
Edited by supersniper on Aug 29, 2015 at 11:12 AM
Edited by supersniper on Aug 29, 2015 at 11:19 AM

I tried running Sapien on my Windows 8/8.1 laptop. But it'd crash once I input a cmt single player campaign scenario. But I'm not going to update to 10 because of certain reasons.
Edited by KAD on Nov 22, 2015 at 08:27 PM

talking about video drivers,

whoever uses windows 10 here and plays halo on it,

has anyone experienced scaling options not working?

for example, my screen is 1366x768 but if I wanted to play the game at 720p resolution, it will change but some black borders will fill the rest of my screen, and fullscreen would not work no matter what do I do in the graphics control panel?

I'm on Windows 10 and scaling works just fine for me. If you are running Halo CE at a lower resolution than your monitor I would suggest using windowed mode instead, unless your screen is really small.

I remember the black bars thing would happen to me on my 4:3 monitor when I set a wide screen resolution. I think OS fixes that, but I'm not sure.

As if they ever provide any useful information.

I found some useful info there a couple times.

However, it was unrelated to what i was looking for.