ISXVG Status

[gp1001]

Amadeus, do you think it would be possible to put a status flag for ISXVG on your main page?

Example:

ISXVG Current Status:
GREEN = Extension is fully operational

YELLOW = Extension is operational with some minor issues.

RED = Extension broken ,needs to be updated.

I think this would stop allot of people from posting on the forums during patch day.
When people see that the status is RED they know your aware and working on fixing it.

Just a suggestion.

Thanks.

 

[Amadeus]

For most patches, the extension should just refuse to load when it is broken. Then, just keep trying it until it loads (every 15 minutes or so) and you'll know when the new one is available.

Or, people could come to IRC on patch days.

But, honestly, it's all pretty redundant. The point of the matter is that if there is *ANY* patch to Vanguard, ISXVG will be broken. Then, it's broken until I release a new version, which will usually be placed on the auto patcher (which runs everytime you attempt to load the extension.)

 

[aChallenged1]

Screw that. If someone using it isn't intelligent enough to realize that ISXVG needs to be updated (big hint, it CTDs you) then they aren't someone who should be using it, IMO.

If something has to be done, make it flash to the screen in big red letters, "ISXVG update required!" Since we know it is an autoupdater that should be enough to let us know that we shouldn't load it for a while. I just wish it would not cause CTD, just unload and repeat the warning each time it is attempted to be loaded while it has not been updated.

 

[Amadeus]

It actually shoudn't CTD you nowadays for most patches. It should refuse to load.

The last one was a crash one because they only updated one file.

 

[gp1001]

For most patches, the extension should just refuse to load when it is broken. Then, just keep trying it until it loads (every 15 minutes or so) and you'll know when the new one is available.

Or, people could come to IRC on patch days.

But, honestly, it's all pretty redundant. The point of the matter is that if there is *ANY* patch to Vanguard, ISXVG will be broken. Then, it's broken until I release a new version, which will usually be placed on the auto patcher (which runs everytime you attempt to load the extension.)

Cool...

Screw that. If someone using it isn't intelligent enough to realize that ISXVG needs to be updated (big hint, it CTDs you) then they aren't someone who should be using it, IMO.

If something has to be done, make it flash to the screen in big red letters, "ISXVG update required!" Since we know it is an autoupdater that should be enough to let us know that we shouldn't load it for a while. I just wish it would not cause CTD, just unload and repeat the warning each time it is attempted to be loaded while it has not been updated

I know exactly what your saying but you always get the post "VG crashed when i load ISXVG"

 

[aChallenged1]

But, as Amadeus pointed out, it should not crash, it should simply refuse to load.

 

[gp1001]

ROFL
told ya...
http://www.isxgames.com/forums/showthread.php?t=947

 

[Warmech]

ROFL
told ya...
http://www.isxgames.com/forums/showthread.php?t=947

shut up ok? I didn't know, I've barely gone on this site.

 

[abbadon]

heh

shut up ok? I didn't know, I've barely gone on this site.

Wow. I think that statement alone might disqualify you from use of this product lol.

Didn't you have to read past the following section of the release announcment to get to the attachment?



"Instructions There is ONE install file that comes with the ISXVG distribution:

* ISXVG-[version].exe

As of March 8, 2007, ISXVG comes with its own patcher. What this means is that when a new version of ISXVG is available, it should automatically download and update itself. This routine is called when you load the extension, so it should be something that you rarely have to think about.

As with most of my extensions, when Vanguard patches, you have to wait to use ISXVG until I update the extension. Typically I release a new version of ISXVG on the evening/night of the day in which the patch took place (Central US time). However, sometimes it may take longer depending on my schedule and/or other factors. If you wish to be up-to-date with the most recent information regarding releases, you should be hanging out on our IRC channel.

ISXVG should reject loading when there is a version mismatch. So, the best thing to do on a patch day is run VG with InnerSpace, and then every so often try "ext ISXVG" (which tries to load the extension.) When a new version is available it will automatically download and reload itself for you."

 

[jake_craner]

shut up ok? I didn't know, I've barely gone on this site.

*E-HUG* We were all nubs at one point. Everyone else, stop taking it as a personal attack when people dont know whats going on. It would be one thing if they posted WTF I PAID MONIES FOR TEH BOTS UPDATE U LAZYS! Amadeus will spread the love when its ready.

 

[kingfisher]

If you dont have the most current version, it patches to the most current version and then tries to load it causing a crash. But then once you reboot and restart it will refuse to load like it should.

 

[Amadeus]

If you dont have the most current version, it patches to the most current version and then tries to load it causing a crash. But then once you reboot and restart it will refuse to load like it should.

This is not something that I anticipated. I'll look into it and make it so that this situation will still cause it to 'refuse to load' even if you're not patching from the latest version.

This is a good report.

 

[aChallenged1]

When I logged in this morning, after the patch (used wrong shortcut, I knew ISXVG wouldn't work) it attempted to patch and when it was unable to it unloaded and told me to try again later.

So, not everyone is crashing when trying to load the first time after a patch.

 

[gp1001]

I had the same thing as King happen when i loaded.
I have mine setup to load ISXVG like it says in the Howto, on the startup tab.
It crashed as soon as the character select screen came up.

 

[aChallenged1]

I had the same thing as King happen when i loaded.
I have mine setup to load ISXVG like it says in the Howto, on the startup tab.

As do I, on the profile I loaded with after the patch this morning.

Apparently, only some people have been affected in that way (crashing upon loading the out of date ISXVG), while the rest of us simply get a message in the console in game that says to wait for the new release.

 

[gp1001]

As do I, on the profile I loaded with after the patch this morning.

Apparently, only some people have been affected in that way (crashing upon loading the out of date ISXVG), while the rest of us simply get a message in the console in game that says to wait for the new release.

Yeah, I only crashed once, now I get the message in the console to wait.
I'm good.

 

[Amadeus]

April 12, 2007 -- By Amadeus
[ISXVG-20070411.0007]
* From now on, ISXVG will do a sanity check before trying to load the extension AFTER doing a patch of the dll itself.  In other words,
  if you're patching from a version other than the latest version, you won't crash on patch days.