Yeah, but it's found elsewhere apparently. Goto Control Panel > Action Center > Change Action Center Settings [ Left Panel] > Problem Reporting Settings > Select 'Each time a problem occurs, ask me'.

Try running the game in windowed mode to begin with - That will take care of the mouse capture issue.

3questions:
1: How useful this would be to a mere mortal, i.e. player, notmodder?
2: How stable is OBSE 20 beta? Because would hate to move from stable to problematic OBSE
3; Which is the first mod in the runtime series and is it any good for players?

1. Not much.
2. I wouldn't really know - My game sessions never last more than 5 minutes.
3. The RuntimeEditorIDs plugin [ Link in my siggy ]. It allows players to use editorIDs in the console.

Try it. Either it breaks one of your mods immediately (unlikely but usually very obvious, and also you should report that to the OBSE team), or it doesn't and you're fine. OBSE never causes any stability issues in the "game crashes sooner rather than later" sense, beta status is just a question of whether all the commands are working as intended.

Ah, yes, I had shut that off because the messages were getting stupid. I didn't realize that shut off error reporting too.

I'll try running in windowed mode, but I have had a lot of trouble with focus issues and I've been told that it is an outstanding issue that MS is apparently looking at. Probably due to all the fancy crap they tried to add to make windoze behave like a Mac Just giving you a head's up more than anything else, because I don't know if there's much you can do about it.

It wouldn't, actually. You can still lookup individual reports in the event viewer [ Control Panel > Administrative Tools ].

Well, that's how the game handles mouse input. I'll see if I can temporarily disable it when the debugger is active.

Well, it seems to be better when running Oblivion in windowed mode, so I'd leave it unless you get similar reports from other players. I'm not sure if part of my problem is a setting somewhere. I have most of the aero theme stuff active and that could be the issue.

Now I need to figure out how to get RUDE to do what I want... I'm pretty sure it's just a case of figuring out what the different settings do. Do you have a way to skip out of a loop, for example? I'm guessing that I would need to define a second breakpoint outside the loop and use the skip to next break command, but with scripts running in what basically amounts to a loop (every xx seconds), I'm finding this a bit tricky to set up the way I'd like.

There isn't a tool to skip out of loops, though it can be implemented with some help from OBSE. Wrapping your loop with a couple of DebugBreak statements should do the trick in your case. Or have I misunderstood ?

Yeah, that might do the trick as well. Basically I was watching a loop until a certain point, and while I wanted the loop to continue, I didn't want to watch it anymore. I could remove the break point inside the loop (DebugBreak) and add one just after the loop from the RUDE console window, correct?

One minor request: could you fix up the formatting of the PDF so that we could print it? Right now it doesn't seem to match up to letter or legal size paper (or even A4). The same for CSE actually. I think to print these types of things and then I add my own notes to them.

Right.

Certainly. Although, aren't PDF viewers supposed to have tools to change page layout for printing ?

Not to that extent. They won't break the text up into pages to match your page size. I think if you have the standard version of Adobe, that allows editing of PDF's, you can repaginate, but I don't think most readers can do that. It might be easier for you to just supply a Doc or ODT file... :unsure:

Yeah, PDF is explicitly a layout format. You can resize the pages, but their aspect ratio and the positions of all elements are fixed, so if you've formatted for e.g. A4 paper and the person printing it is using U.S. Letter-size, they'll wind up with particularly wide margins on the left and right. There's no way for the text at the bottom of page 1 to flow onto page 2 so the margins can be made even, because the pages are individually encapsulated.

Looks like the only reason you're using PDF is to embed the image, there's no fancy layout otherwise. Seconded that you should use a word processor format (.odt or .doc for maximum compatibility), or even just HTML. Something where the content is the primary data and the layout is flexible.

If you haven't considered it, perhaps you can host the non-essential documentation online, e.g. using a free wiki hosting site. It doesn't work well if you have multiple versions released, but it would be a lot easier to format and cross reference.

Right. I'll bundle the document file in future updates.

I used to do that with my mods. But as you stated, it ended up making the updating process even more tiresome with each new build.

I'll try this and let you know how it goes. Thanks

Obligatory bump.

Is there any way to resume the game, and then call the debugger back up?

Yes. Hit the 'Toggle breakpoints' button in the UI before resuming. That will prevent DebugBreak statements from invoking the debugger. When you want it back, simply commit the 'ToggleBreakpoints' (can't remember the name correctly - Should be mentioned in the manual) command in the console.

The manual didn't say anything about specifically resuming the game and then calling the editor back up. I read it, I promise. If it is in the manual, I overlooked it.

No, I don't believe it does. I was merely stating that info about the script command should be present in it.

Oh, okay. I misunderstood. It does say mention the script command.