Sign in to follow this  
Followers 0

Lump read speed

What happened to loading lumps into text in the latest beta? I try to open hexdd.wad (that Hexen addon) and it begins reading the first lump (DEMO1). It's still cycling through the lines as I'm typing this.

Share this post


Link to post

Sounds like a crash to me, it reads the Hexen iwad fine. (could be to do with the fact it's marked as an iwad or something, I know wintex can't read it at all)

Share this post


Link to post

No, it eventually read the file. But it shouldn't take 10 minutes to read and display a single DEMO1 lump.

Share this post


Link to post

I don't think this is not new to the latest beta.

One of the initial goal for XWE was to be able to edit all the lump types, this would include DEMO lumps. Right now the demo "editor" is display only, and it is in fact pretty slow. Not to mention sort of useless: I don't think anyone is reading through the demo movement data. (Those guys who deal with demos probably use one of the more specialized demo tools anyway.) For the next version I'll think I will just take this out, or make the demo "editor" display only the first few pages of the data or something.

Meanwhile, open up the xwe.ini file (it's a simple text file), locate this entry: [DEMO]. Put a semicolon in front of the line "Editor : DemoEditor". This will prevent XWE from using the slow demo "editor", and the lump will be displayed as a hexdump.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0