Mike

I am, that was one of those little things that annoy me I will package it up tonight (I assume the changes are that we are simply including a bttf.img which the models will go in, and renaming bullet.dff and sparrow.dff in gta3.img) if there are any other changes just let me know. @DK thanks for uploading them ready.

I hate the new photobucket player, it takes an ice age for the videos to load even when playing them directly. Looks good though (I did at least get the latest 2 videos to load) @Angelo, do you have hell on the brain or something?

First one for the win and that length looks fine

Must admit I haven't actually applied this patch since there were no manual editing instructions, and I believe the file in question has been edited for some of the mod's we have installed here.

*Yo Carlos/K/Liam*

I was having a blonde moment. So how come it doesn't look as bright in the day? The one from the old buggy mod looks as though it stays the same (though that is perhaps because the present time was before 00:00) Edit - I would say it's the desert that's the issue then

Definately looks better at night. Is it possible to code it so that it uses a different set of models depending on the time of day? I know this would be doubling up on the amount of models you are adding, but, this way you could setup one set of models up for use during the day, and another set of models for use at night.

I prefer the bigger one myself.

That's cool Can you do a video of it in action?

That's ok, no major rush.

Completely off topic, but do you have time to fix up the wormhole code for VC so we can retest? I want to try and get VC fixed so it doesn't keep crashing on loading script.

My bad, I misread it.

I would upgrade it today if people could live with the default 3.x skin. I think I will need to end up paying to have someone make a skin for us.

You know, I don't get why you keep deleting it

It doesn't uncompile it completely though does it? Meaning that you don't get the original source code when you uncompile.

Link me up to some options and I'll look into installing it.

No, it is not compatable with Invision 2.x.

http://community.invisionpower.com/topic/2...toring-service/

Microman I must apologise for that, it was indeed a bot that signed up and then proceeded to PM everyone on the board. Both the member - Lyagushkka and their IP 94.142.128.140 have been banned.

Or they could just run my downgrader... Incidentally, Mini-Me successfully installed the mod on a stock V2 copy of San Andreas without downgrading it, and it worked. The lockout is in the .exe, and since that is replaced by the installer there shouldn’t really be a problem with people installing the mod on SA V2

I was planning on doing re-releasing the SA mod download with the .net check built in, and also have a .net required in big bold text on the download page, not required in the readme, since the installer won't start without a minimum of .net 1.1 installed.

and if .net is required for MSN many people will already have it for XP also. Option 1 it is, we can't babysit people every step of the way, even having an auto installer should be considered a luxury.

That's an about face from what you posted earlier isn't it? Fact is will just bloat the installer to include it.

They could download it from another machine and then copy it via USB stick or something like that, and the link in the error message would obviously be for people who have an internet connection, if they don't, then they will just have to write the link down and/or just use google when they get to a machine that has access to the internet.

People are naturally lazy I will work on making the link clickable, however I'm not sure how to do this yet since the error message text is in a macro which is called by NSIS !include DotNetSearch.nsi That is entirely possible I guess. However, what if the user is installing it on a PC which does not have access to the internet? You also have to remember that not everyone will want to install the English version of .net which would pose a problem using the NSISDL method you suggested as this would only link to one file. I'm all for option 1 myself. I just switched over to aMSN a few weeks ago since my version of MSN messenger (v7) stopped working, and I can't be arsed downloading that bulky Windows Live package just to get messenger, plus I don't like how the new version is laid out.