Towncivilian

Please install the following: Graphics driver Audio driver Chipset driver Ethernet driver (if option to Repair or Uninstall is given, select Repair After installing all of the above, please provide another dxdiag report and also see if your crash is resolved.

Fixed aiming reticle for widescreen resolutions (thanks to Squiddy for his open-source fix). Draw distance and LOD display distance have been doubled from default: The weapon pickup message box (well, technically this is *every* message box that appears like this) moved out of the way of the chatbox for Vice and 3: Frame limiter is also forced on every game startup since several things do not operate properly without it being on (i.e. start game automatically, vehicle explosions are too fast). Now I need to figure out the aiming fix for GTA3.

Does GTA:SA work fine in single-player? Could you provide a dxdiag report? Press the Windows key + R, type dxdiag, press Enter, click Save all information... and post the contents of the saved log here within tags.

No, you don't need any D3D9.dll. I was asking you to check because if there is one present, it usually causes issues. Can you answer my question about when your game crashes (only in map editor, or elsewhere)?

Okay. Does your crash occur only when trying to use the map editor, or when trying to join a server or some other circumstance?

Is there a D3D9.dll in your GTASA directory? Update DirectX runtimes and install/repair Visual C++ 2008 SP1 runtimes. Do you get this issue only when trying to open map editor?

Is your version of GTA:SA a legit copy (i.e. bought from a store or Steam)?

Known incompatibility with Mobile Intel 4 Graphics Chipset. There is no fix yet, sorry.

Install this (if it gives options for Repair or Uninstall, select Repair) and this. EDIT: Wait, is that your GTA:SA directory? It should have more folders and files than that. Did you install it correctly? Or is it located in the "GTA SanAndreas" folder there?

Finished SSV SCM in something like 3 hours (with mistakes made at one point causing me to waste more time), it's really not as bad as I thought it would be. Hardest part was finding motivation to start. For obvious reasons extensive testing of everything will be required. Portland and Staunton, being less complex, would take maybe 2 hours each. New icon: Looks crappy as a 32x32 icon, but just about any icon would: The original icon () looks better, but it's color corrected. I'll have to tweak it some more before getting a decent usable 32x32 icon. Thanks to EliteTerm for photochopping the original to provide the icon. And I now have a nice, shiny new avatar.

Verify that you have a vorbisFile.dll in your GTASA directory. If not, buy a copy of GTASA!

Obtain a 1.0 no-cd exe.

Thanks for the three year bump. Try posting in the proper support section. Topic locked.

0.5 and its variants are still flagged as false positives.

I already said the site has errors in the "Site Errors" topic in this forum Topic locked EDIT: I posted this on my phone. I didn't actually check to see that the site was just displaying an index page. Oops.

Only 0.5 is flagged since it is UPX packed, no other 0.x version is

Could you provide a dxdiag report? Press the Windows key + R, type dxdiag, press Enter, click Save all information... and post the contents of the saved log here within tags.

Try this installer. It has a working server browser. There is probably nobody playing GTA3:MTA, though. You can try Liberty Unleashed.

Due to significant GTA3:MTA issues necessitating a re-do of all SCM work, a release will have to be pushed to January 31, 2011 (MTA 0.5's 6th birthday). There will be at least one more MTA:VC test sometime after Christmas. Sorry for the delay.

You may be able to rewrite the resource in SCM & CLEO for use in single player, but there's no automated way to do it.

My only option is to re-do everything using Sanny Builder instead of GTAMA, and I'll need to begin from stock 0.5's SCMs. I guess there's always MTA 0.5's 6th birthday on Jan 31st for a release; I think 4 days to redo the GTA3:MTA SCMs is just too little time and I'll forget certain things and overlook others. Of course, I noted most of my changes, but stuff will still be slow since I need to convert GTAMA-style code to SB's style, plus SB has no variable/label names or comments that are present in the GSRs used by GTAMA which are immensely helpful, so I'll waste more time glancing between the two as a result. I guess another Vice beta test will be good to do meanwhile.

goddamn mirc settings

Compiler error regarding variable values has caused a need to do one of the following: 1: find-and-replace original values for 150 to 200 variables per SCM using Sanny Builder, or: 2: re-do SCMs starting from 0.5 stock using Sanny Builder Sanny Builder didn't decompile GTA3:MTA's SCMs out of the box, but earlier today I made the opcode definition files identical between GTAMA and SB and to my surprise, SB works fine now. That also brought to light GTAMA's poor excuse for an SCM compiler. 30 minutes of work modifying SB's opcode definition file back in April would've saved me all of this headache now. In fact, trx sort of warned me about this issue back in January, but I overlooked it unfortunately. I had planned on releasing 0.5r2 on the 23rd, but perhaps I'll have to postpone things a bit depending on how long it'll take me to fix this mess. GTAMA's compiler errors are the reason why gamemode sync does not currently work, and probably some other stuff is not synchronized properly either as a result. This sucks.

Moved to Server support section.

They're necessary components for MTA:SA. They're from Microsoft, you won't get a virus.