A.I. Disabled

[Hovercat]

Hi there, me and a couple of friends are making our own mod, and I'm in charge of making the maps. I started off making the first one, which worked as I wanted it to, but once I step through the trigger_changelevel to the next map, it says "A.I. Disabled..." in the lower right corner, also, all the NPC's are now frozen. It stays there even when I go back to the first map, I have all the info_node's and everything works 100% correctly before the map needs to be changed. I am currently using hl2 to test the maps, and the only time I get the "Node graph out of date: Rebuilding" error is when the map is changed. Please Help. I attached a image in case you don't know what i mean. Please Help.

P.S. Even though it says there are no path nodes in the developer, there are.

 

[bbson john]

pirate half-life

 

[kineaesth]

Do you own a legitimate copy of Half-Life 2?

 

[Hovercat]

Yes, i bought a copy from microcenter for $8.

 

[gFrohman]

Try deleting the nodes you have currently, then create new ones. Sometimes Hammer has random PMS attacks and if you give it fresh entities it might help.

Otherwise I would verify the game cache. If it still doesn't work, I'm stumped.

 

[bbson john]

The last resort, contact Valve by E-mail. Telling them the problem and everything you have done.

 

[Hovercat]

Try deleting the nodes you have currently, then create new ones. Sometimes Hammer has random PMS attacks and if you give it fresh entities it might help.

Otherwise I would verify the game cache. If it still doesn't work, I'm stumped.

Aaaawww.... Is there a way to select more than one entity of the same entity at once? like can I select every node without selecting anything else? That would work beautifully here instead of clicking and hitting delete for 700 nodes.

And, I will also contact valve if this isn't resolved, which the other guy said, but I didn't quote, cause i'm on vacation spending 30 cents a ****ing minute.

 

[Ricco1962]

a.i disabled problem

Hey Hovercat,
Don't know if this helps but there is an unacknowledged (by Valve/Steam) bug in the 64-bit version of HL2 (at least the Orange Box version but I have seen post for this problem dated years ago) that will cause the 'node rebuilding/a.i. disabled' problem. This (for me) happens whenever you die and reload or if you just reload a save.

The only solutions I have found are:
1 manually re-enable the ai with the command ai_disable 0 in the console every time it happens (can't remember if you need cheats enabled for this).
2 you can manually disable 'node rebuilding' with ai_norebuildgraph 1 command in your autoexec.cfg but I have found that this can cause weird stuff to happen. Yes weird IS a technical term.
3 you can try to reinstall HL2 as the problem will come and go with each install. I am up to four installs (because I am always playing with my OS and often break it) and am 50-50 with the problem.
4 you can force the game to run in 32-bit mode by adding -32bit to the command line of your shortcut or in the Steam->My Games->Right click->Properties and add -32bit to the 'Set launch options'.

or

5 you can wait to see if it just goes away.

The fourth (current) install of my Orange Box was giving me this problem so I changed ALL Valve HL2 games to -32bit and the problem stopped, but since then I have installed FFCinema Mode 10 and removed the -32bit command from all the 'launch options' and now the problem is not showing up. However I don't see the message that I am starting in 64-bit mode when I run a game (which supposedly will auto-detect if you have 64bit OS) so I not sure what mode I am in. I suppose I am in 32-bit and could force it to 64 with the -64bit command but I am too gun shy to try it at this point.

And now for a little 'rant'

To all those that cannot seem to understand that this problem is a 'for real' bug that affects 'bought and paid-for' versions of HL2 and has been around forever. It is a problem that Valve/Steam is doing NOTHING about or even seems to be acknowledging. Maybe you 'rabid pirate labelers' give them the excuse to say that this is just a pirate version problem so they don't have to deal with it. Or maybe it's just because they DON"T CARE!

So, WHILE PIRATED COPIES MAY HAVE THIS PROBLEM BECAUSE THEY ARE CORRUPT, they may also have this problem BECAUSE IT IS A BUG IN THE IMPLEMENTATION OF THE 64BIT CODE and Valve/Steam IS DOING NOTHING ABOUT IT.

So instead of labeling users with the dreaded 'pirate' label and/or asking them to show you a picture of their their game box and/or serial and doing nothing to help people with a legitimate problem, why don't you contact Valve and demand to know when they will fix the bug. Or you can just SHUT UP and not post your less then useful replies.

I apologize to everyone if this starts a flame war, but I for one have this problem with a real, 'bought and paid-for' version of Orange Box and am sick and tired of seeing these people being rude, obnoxious and unhelpful to all the people with this problem.

 

[Pi Mu Rho]

Nice rant. Funny thing is, a good 95% of the people that have come here for help with the ai_disable error have been using a pirated copy. So no cigar for you.

 

[Ricco1962]

Ha!I don't smoke anyways so I have no need for no 'stinkin' cigars

but...

I would like to know how you came up with this 95% number, because even if your statistic is
correct, there are still lots of people, with legitimate copies, who have this problem. btw if you
go onto the steam forum there are threads on this topic as well and I have yet to see Valve/Steam say themselves, in any kind of press release, that this is a 'pirated copy' problem, in fact I have not seen them ever talk officially about this issue.

 

[Rizzo]

Im sorry.