5 filer liked
757 kommentare
2 videoer
3 uploads
60 følgere
32.855 downloads
@szhitt try one of these:
http://download2176.mediafire.com/7mu4vecorvvg/86paxb3gzpkuztn/RDE+3.1.zip
http://www.mediafire.com/file/86paxb3gzpkuztn/RDE+3.1.zip
@OG_Grinskin91 The SixStarResponse script has a debug mode you can enable if you want. Play the game and when it crashes send the log file.
@MarineMan2016 If you use/steal military type vehicles at some of the lower stars (I believe 4 or 5) the military may show up
Failed to instantiate script 'SinglePlayerApartment.SinglePlayerApartment' because constructor threw an exception:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at nativeCall()
at GTA.Native.?A0xe506951e.NativeTask.Run()
at GTA.ScriptDomain.ExecuteTask(IScriptTask task)
at GTA.Native.Function.Call[T](UInt64 hash, InputArgument[] arguments)
at SinglePlayerApartment.SinglePlayerApartment.LoadMPDLCMap()
at SinglePlayerApartment.SinglePlayerApartment..ctor()
Just an FYI on Biker DLC
@trgman No, i don't work on anything GTAV Related anymore.
@joshbon007 Can you tell me exactly what line you're changing to 6 and in which file
@napervillerob Most if not all of those models are vanilla models, perhaps you're using an RPF mod that borked them? I'd disable all RPF mods and just load the dispatch ghost fix to see if these all fail still or not.
@juniorh I tested 2.4 right now and World.GetAllPeds works fine for me, make sure that your actually using 2.4
@napervillerob Either your game doesn't have s_f_y_hwaycop_01 or your computer cant handle loading all these peds at the start of the game. Try pressing the 'insert' key on your keyboard after about 2/3 minutes and see if they all load. If it doesn't load still and you don't notice cars driving with no driver, then I wouldn't worry about it.
@damzen I forwarded your message to the guys working on RDE, this script doesnt deal with gameconfig.xml so it's not really something I can fix myself.... Regardless, after talking with the guys, this is a known issue and will be resolved with the v2.2 release.
Thanks for the heads up though!