ward of the elements bug

fjzig

Active Member
hey ever since the new ls revamp / WoE came out when ever i zone into it while using isxeq2 i get zoned in under the ground and can not be cohed evaced or fall to my death to get the zone to display normally any ideas why? cause when i use normal eq2 the zone loads just fine
 

Multicharacter

Senior Member
What makes you think you are zoning in under the ground? Normally if you are truly under the ground it'll move you to a safe point when you move. You sure it just isn't showing your surroundings? (I have that happen occasionally, you usually can just camp out and back in and then everything shows up) You're above ground, everybody else sees you exactly where you are suppose to be, it's just 3D isn't being rendered.
 

fjzig

Active Member
tried that, i was evaced and zoned in "under" the world, jumped and "fell" through the world died and respawned "under" the world, im assuimg i was under the world because i the only thing i could see above me was the towers for the water named
 

mycroft

Script Author: MyPrices
Not sure what your problem is , but zoning into WoE with isx loaded doesn't cause me any problems at all.
 

Pygar

EQ2Bot Specialist
Sounds like an eq2 problem, I've been doing WoE since launch with no issues.

I'd backup your everquest2.exe and do a full patch / scan, then restore your current exe.
 

fjzig

Active Member
Sounds like an eq2 problem, I've been doing WoE since launch with no issues.

I'd backup your everquest2.exe and do a full patch / scan, then restore your current exe.
im assuming you mean un and reinstall eq2?
 

wired203

Active Member
No that's not what he's saying, however since today is a patch day you don't need to backup your everquest2.exe

Use the normal patch launcher and under options there is the ability to do a full re-scan for any missing or busted files.
 

fjzig

Active Member
yeah just did that after the update, it didn't find any bad or missing files :(

:edit: but its not the normal eq2 that has the problem its isx when i go into WoE through normal eq2 it works just fine
 

Valerian

ISX Specialist
<Channel Name='Lax'>I call PEBKAC. One person is having this issue. Nobody else is having this issue. Dude, I'm sorry to say this, but there's SOMETHING fubar on your system. Don't blame Inner Space or ISXEQ2 unless you can bring some proof to the table. </Channel>
 

fjzig

Active Member
<Channel Name='Lax'>I call PEBKAC. One person is having this issue. Nobody else is having this issue. Dude, I'm sorry to say this, but there's SOMETHING fubar on your system. Don't blame Inner Space or ISXEQ2 unless you can bring some proof to the table. </Channel>
if it works just fine with normal eq2 and doesn't work properly when using inner space/isxeq2 how is it my system? if it was my system would it not also not work properly with normal eq2?
 

Valerian

ISX Specialist
if it works just fine with normal eq2 and doesn't work properly when using inner space/isxeq2 how is it my system? if it was my system would it not also not work properly with normal eq2?
When it's not happening to ANYONE ELSE, it must be something on your own system. ISXEQ2 and Inner Space work for EVERYONE else in that zone. You may have some software or driver installed that is conflicting. Make sure your drivers are up to date and not beta or third party drivers, you're not overclocking your video, your DirectX is up to date, your windows is up to date, etc.

As previously stated: Bring proof of what the problem is, or at the LEAST a way for others to reproduce the bug, and it can be looked into. At this point, all available data points to something awry on your system.

I don't say this to be a dick. I say this from a programmer's perspective of people claiming "your shit is busted" without any justification or proof.
 

fjzig

Active Member
When it's not happening to ANYONE ELSE, it must be something on your own system. ISXEQ2 and Inner Space work for EVERYONE else in that zone. You may have some software or driver installed that is conflicting. Make sure your drivers are up to date and not beta or third party drivers, you're not overclocking your video, your DirectX is up to date, your windows is up to date, etc.

As previously stated: Bring proof of what the problem is, or at the LEAST a way for others to reproduce the bug, and it can be looked into. At this point, all available data points to something awry on your system.

I don't say this to be a dick. I say this from a programmer's perspective of people claiming "your shit is busted" without any justification or proof.

ok and thank you Valerian, in all honesty if its only happening to me and i dont understand why i dont think i would be able to tell someone how to reproduce it but i will check everything out to make sure its all up to date and if not then i will start from there i didn't mean to blame innerspace/isx for the problem it just seemed logical to me considering it worked normally but with it only being a problem im having it shouldn't be a problem with innerspace/isx thanks again
 

Valerian

ISX Specialist
ok and thank you Valerian, in all honesty if its only happening to me and i dont understand why i dont think i would be able to tell someone how to reproduce it but i will check everything out to make sure its all up to date and if not then i will start from there i didn't mean to blame innerspace/isx for the problem it just seemed logical to me considering it worked normally but with it only being a problem im having it shouldn't be a problem with innerspace/isx thanks again
Generally speaking, you'd be correct. The only thing at this point that makes me think it's NOT Inner Space or ISXEQ2 is the fact that nobody else has mentioned having the issue, either on the forums or on IRC. There has been enough time for a pretty good sampling of ISXEQ2 users to play that zone, and many of those are vocal about any little problem.

Please, if anyone else IS having the issue, post in this thread and complain! The quickest way to resolve an issue like this would be to compare notes and figure out what is common between the systems that have the error.
 

Kannkor

Ogre
I have a slight variation of this bug.

When I zone to WoE, I can see everything. If/when I die, on 2 of my 3 computers, I can no longer see Digg (but only Digg). I log out, and back in, and he is back.

I can still melee/attack him while he's "invisible", however all spell icons are red because it doesn't think he's in range.

An annoying bug, however it's not a life altering bug for me... I don't have many common elements as to why it's working/not working on some of my PCs.
Working: Vista64 - graphics as low as possible - ATI card
Not working:
Vista64 - NVidia
XP32 - NVidia
Both with graphics as low as possible

The two NVidia's are extremely different cards (about 2 years apart).
 

Valerian

ISX Specialist
I have a slight variation of this bug.

When I zone to WoE, I can see everything. If/when I die, on 2 of my 3 computers, I can no longer see Digg (but only Digg). I log out, and back in, and he is back.

I can still melee/attack him while he's "invisible", however all spell icons are red because it doesn't think he's in range.
That sounds more like the model bug, which some people report on trak and other miscellaneous mobs. EQ2 bug, not related at all to IS/ISXEQ2. Toggling between the new (soga) and old models generally corrects that particular issue. Could be wrong, but that one doesn't seem to relate to the whole missing world bug this thread was started about.
 

mycroft

Script Author: MyPrices
The only related item, is this only happens in WoE, and only on Digg...
I've had this on wipe in Digg when running ISX and when not running ISX , happens to me on Trak also sometimes....toggling the soga on and off cures this as Val says.
 
Top Bottom