Σ 1.7 Bugs&Feedback

Discuss Median XL!
Bljadzon
Abomination
145 | 6
Common Popularity Badge
Has a thread with over 10.000 views
Hello, I've got this error while transferring items via shared stash.
In my stash I had:
1st page: a bunch of runes (about 15) plus two TU1: Spear and Saber
2nd page: a bunch of gems (about 10)
3rd page: empty
Image

One character can access the stash, the other cannot.

After emptying the stash, I can access it with a second character.

Anything I need to provide?
Fellerd
Thunder Beetle
58 | 11
OldPlayer wrote:
PizzaGater wrote:
Ani08 wrote:
Fellerd wrote:
OldPlayer wrote:Image
Why does the game crash when opening skills ??? Before 2.0, this did not exist at all, everything worked fine


I had a similar problem.Fixed it by running the game in Glide video mode


Hi! I have the same problem. When I open skills, or try to save the game. How can I run the game glide video mode?


when you launch median
open settings, then video mode menu and select 3DFX glide


oh really helped, thanks

edit now:

helped, but not for long, the game still starts to crash again, when opening skills ...


Yeah,same thing happened to me.I've tried most of the stuff in this list,but take a look yourself-something might work for you:

Make sure Diablo II.exe is set to run as an Administrator and in compatibility mode with WinXP SP3 while the Launcher as an Administrator. Try also restarting your PC. If this didn't solve the issue follow the instructions below:

1) Download d2mxl_dep_reset.bat (right click, 'save as') and Run As Administrator to delete any corrupted registry entries. viewtopic.php?f=42&t=20890&p=187940#1-2

2) Open Explorer, right-click Computer, Advanced System Settings, Advanced tab, Settings in Performance section, Data Execution Prevention tab.

3) Choose Turn on DEP for all programs and services except those I select

4) Add the Diablo II.exe and Game.exe processes to the DEP exclusion list

5) Restart the PC without opening the Launcher or the game
User avatar
OldPlayer
Lava Lord
97 | 0
Fellerd wrote:
OldPlayer wrote:
PizzaGater wrote:
Ani08 wrote:
Fellerd wrote:
OldPlayer wrote:Image
Why does the game crash when opening skills ??? Before 2.0, this did not exist at all, everything worked fine


I had a similar problem.Fixed it by running the game in Glide video mode


Hi! I have the same problem. When I open skills, or try to save the game. How can I run the game glide video mode?


when you launch median
open settings, then video mode menu and select 3DFX glide


oh really helped, thanks

edit now:

helped, but not for long, the game still starts to crash again, when opening skills ...


Yeah,same thing happened to me.I've tried most of the stuff in this list,but take a look yourself-something might work for you:

Make sure Diablo II.exe is set to run as an Administrator and in compatibility mode with WinXP SP3 while the Launcher as an Administrator. Try also restarting your PC. If this didn't solve the issue follow the instructions below:

1) Download d2mxl_dep_reset.bat (right click, 'save as') and Run As Administrator to delete any corrupted registry entries. viewtopic.php?f=42&t=20890&p=187940#1-2

2) Open Explorer, right-click Computer, Advanced System Settings, Advanced tab, Settings in Performance section, Data Execution Prevention tab.

3) Choose Turn on DEP for all programs and services except those I select

4) Add the Diablo II.exe and Game.exe processes to the DEP exclusion list

5) Restart the PC without opening the Launcher or the game



Everything that you wrote, I did, and still the problem did not go away (((( it also crashes and that's it ... I'm just in shock from 2.0, before it, the game worked quietly, without these "jokes"
BrecMadak
Rust Claw
82 | 5
Hey people, you all are not obliged to use this shitty CNC as a gun pointed at your head. Tech support on discord has been ruined since the launch, as I see many people have been suffering from tediousness CNC has brought in. I was also baffled that I've never witnessed that a mod recommended this.

Why don't you give it a try to d2dx (even though it doesn't support widescreen for median as of now - normally it does for PD2, PoD and vanilla.) More stable and more convenient all the way, get it here: https://github.com/bolrog/d2dx

The only downside is it doesn't let you adjust the window location on your screen if you are running windowed. However, you can still fixate on your favourable position prior, from its cfg.
Fellerd
Thunder Beetle
58 | 11
@OldPlayer: Ok,I was able to play for about an hour and no errors anymore.Here's what else I did:
1.I disabled ingame sounds
2.Set the launcher to run as administrator
3.Set Game.exe and Diablo II.exe to run as administrator
4.Went back to DirectDraw
5.When you press escape,you can change the skin of the HUD (it's Tartarus by default)-I changed to Red w/e it's name was (there's a drop-down menu when you click on it)
One of these worked for me,can't say which exactly,because I did them all at once :D .But I hope at least some of them work for you and anyone else.
Ani08
Imp
4 | 0
Fellerd wrote:@OldPlayer: Ok,I was able to play for about an hour and no errors anymore.Here's what else I did:
1.I disabled ingame sounds
2.Set the launcher to run as administrator
3.Set Game.exe and Diablo II.exe to run as administrator
4.Went back to DirectDraw
5.When you press escape,you can change the skin of the HUD (it's Tartarus by default)-I changed to Red w/e it's name was (there's a drop-down menu when you click on it)
One of these worked for me,can't say which exactly,because I did them all at once :D .But I hope at least some of them work for you and anyone else.



Thank you! I set the launcher, game.exe and diablo II.exe to run as administrator, and also change tartarus skin to crimson. (Didn't disabled sound or went back to directdraw). Now it seems that fixed my problem, the game didn't crash when I opened the skill tree or saved the game. I played too for about an hour without problem. :D
User avatar
OldPlayer
Lava Lord
97 | 0
Fellerd wrote:@OldPlayer: Ok,I was able to play for about an hour and no errors anymore.Here's what else I did:
1.I disabled ingame sounds
2.Set the launcher to run as administrator
3.Set Game.exe and Diablo II.exe to run as administrator
4.Went back to DirectDraw
5.When you press escape,you can change the skin of the HUD (it's Tartarus by default)-I changed to Red w/e it's name was (there's a drop-down menu when you click on it)
One of these worked for me,can't say which exactly,because I did them all at once :D .But I hope at least some of them work for you and anyone else.




Option 3 helped. All the same, the problem was solved, I set compatibility with XP in Game.exe and run it from the admin. And it helped the hike, and the problem finally disappeared, thanks for the advice!

I apologize for disturbing you if anything :)