Runes of Magic US / AU

I also run 64 but W7 and have had absolutely no problems with this patch at all. Now I did do a search for this error and found it is releated to the actual programing code used to make RoM (actually it is used to amke a lot of programs). Only way I can see to fix this is to download the newest copy of the client and do a full reinstall. Yes it is a pain but after searching for a way around this I have found no other way to fix it.

Quoted from "labatts;530771"

I just upgraded to version 4.0.11.2525.en. After clicking the Start Game button I get the error message that says "Error assembling VS". After clicking OK I get the Crash Report window. I am running 64 bit Windows 7.

Receiving the same error message on Win XP-32 bit in BOTH the Slim AND Full clients.
Must be a new "Game Feature"...
HOPEFULLY, a virgin reinstall will fix it...

Quoted from "Nytefall;530891"

This issue can be fixed without a client reinstall.

Simply update your DirectX client directly from Microsoft's website:

www.microsoft.com/en-us/download/search.aspx?q=directx

Simply click the "DirectX End-User Runtime Web Installer", and allow it to install.

Thanks. Seeing as I was unable to find anything that led to this ahving anything to do with Direct X I just put what I found out. Hopefully more will see this.

Quoted from "Nytefall;530891"

This issue can be fixed without a client reinstall.
Simply update your DirectX client directly from Microsoft's website:
www.microsoft.com/en-us/download/search.aspx?q=directx
Simply click the "DirectX End-User Runtime Web Installer", and allow it to install.

OK - It worked, HOWEVER...

Reinstalling DirectX as a fix to the exploding Game patch makes LESS THAN ZERO sense:
(1) My DirectX was never out of date (Windows was and remains 100% current PRIOR to the Game patch).
(2) The only thing that changed was the Game patch got installed.

Reasonable conclusion: The Game patch broke DirectX...

Concerns:
(1) Why is RoM changing the underlying OS WITHOUT clear notification that it is doing so?
(i.e. The Game {and all legit software for that matter} should USE existing OS features, DLLs, APIs, etc; NOT modify them to suit secret purposes.)
(i.e. Changing underlying OS behavior is what Viruses & Malware do, NOT legitimate programs.)
(2) What else are you secretly putting on my machine under the guise of updating the Game?
(i.e. Backdoor, Key loggers, other virus like behavior, etc.)

I'd like to see a real reason/explanation (not smoke & mirrors or excuses) from an official source for this situation, please...

i just spent 2 days trying to reinstal this [redacted] and i still get the same file missing..ive tried to uninstal and reinstal both clients twice..can anyone give me any other ideas this is starting to piss me off i wasted money on diamonds and i cant even get teh damn thing to download right

Quoted from "thelegend373;530994"

i just spent 2 days trying to reinstal this [redacted] and i still get the same file missing..ive tried to uninstal and reinstal both clients twice..can anyone give me any other ideas this is starting to piss me off i wasted money on diamonds and i cant even get teh damn thing to download right

First, young man, kindly watch your language.

Second, had you read Nytefall's message above, you would have seen what he said about updating your DirectX installation.

Go here: http://www.microsoft.com/en-us/downl...aspx?q=directx Follow the instructions on installing the DirectX update.

The problem is not having some of the older Directx 9 files that Microsoft has deemed not necessary due to their idiocy. Even having Direct X 11 I still had to get the correct files from Microsoft. And I am rather (I would use another word but the one I want means [redacted]) about updating everything at least once or twice a week. SO this problem hit me and all it took was a visit to Microsoft and an install of the missing Directx 9 files.

Quoted from "Nytefall;530997"

The last patch required the most up-to-date version of DirectX 9 - this error message only appeared if your version of DirectX was not completely updated.
The game client does not modify the operating system (Runes of Magic doesn't even leave any registry entries) - It just alerted you that a component was out-of-date.

Nytefall -

Bluntly, my "stuff" was never out of date. Like MegaMouseSEC, I am pretty obsessive about updating my system: I run multiple maintenance programs (Secunia PSI, IOBit Adv Sys Care, Anti-Malware, Anti-Virus, Windows update, etc.) WEEKLY to keep my OS 100% up-to-date, that leaves your patch as the only "new" variable.

To "fix" the problem as you suggested, I reinstalled Direct-X v9 update v9.29.1974; published: 4/18/2011; file name: directx_Jun2010_redist.exe; size: 95.6 MB. I used the VERY SAME FILE I used some 12 months ago when I did the initial install and update of the Win XP OS; the VERY SAME Direct-X distribution that has worked flawlessly UNTIL this last Wednesday patch... Since the "fix" involved over-writting something that (1) previously worked flawlessly (2) with the VERY SAME files that were there previously, I am left to surmise that the only variable in the equation, your patch, caused the change in behavior...

Therefore, while your suggestion cured the Game problem, your assurance that the RoM Game patch did not cause the problem is substantially less than reassuring: My experience (and that of numerous other players according to your own forums) does not support your claims of innocence...

The full directx install is not always up to date.
Microsoft updates directx very regularly, sometimes monthly, sometimes even more often.
The best way to get the latest updates is to run the webinstaller. It looks at what you have & installs only the updates you don't have from the latest directx release.

The webinstaller is compatable with all versions of Microsoft Windows, even those versions running directx 11.

To my way of thinking Runewaker actually did it right this time & used the latest version of directx when putting their patch together.