So I was bored...

[another_commander]

Hmm, interesting. I cannot reproduce this, so I don't think I can be of any help here, but at least I can say that the RTSHookInterop.exe is not an Oolite related process.

Edit: ninja'd.

[ADCK]

ignore what i said about RTS thingy... that was just because i had it running on my second monitor, part of some software i'm running...

As for there being 2 instances of it, doesnt seem to harm it any, could use the degugger fine to spawn in some ships.

[Frame]

well for starters he should try disable it(the rtshook thing), then run the debug console again...

the debug console: it works fine on this note book that runs vista home premium on a 64 bit intel centrino 2 inside...

i would not be surprised that this is a multi monitor error thingi since the rtshook thingi seems to be connected to a program named ultramon. why it tries to hook into the console i do not know, but likely its something about the debugconsole connecting to Oolite... and oolite runs in fullscreen on 1 monitor and the debug console on another monitor..

Purely speculation from my side here...

if so stop ultra monitor, and run the debug console a system that is only operating on 1 screen, and see if that works..

i usually run Oolite in a window and switch to debug console when needed (something you would need todo anyway)

and spawn my test objects there.


funny, that last post was not there when i read this,..., :S the time of the two posts make no sense to me either,,,
cheers Frame,,

[ADCK]

well for starters he should try disable it(the rtshook thing), then run the debug console again...

the debug console: it works fine on this note book that runs vista home premium on a 64 bit intel centrino 2 inside...

i would not be surprised that this is a multi monitor error thingi since the rtshook thingi seems to be connected to a program named ultramon. why it tries to hook into the console i do not know, but likely its something about the debugconsole connecting to Oolite... and oolite runs in fullscreen on 1 monitor and the debug console on another monitor..

Purely speculation from my side here...

if so stop ultra monitor, and run the debug console a system that is only operating on 1 screen, and see if that works..

i usually run Oolite in a window and switch to debug console when needed (something you would need todo anyway)

and spawn my test objects there.


funny, that last post was not there when i read this,..., :S the time of the two posts make no sense to me either,,,
cheers Frame,,

Phpbb2 is buggy at best, or it could be a disturbance in the space-time continuum!

[Zieman]

Is there a program for making screenshots of the models? As my PC uses a very hi res and I don't want to use in-game shots for posting pics...

Umm... you can always resize the in-game screenshots before posting.
And many online picture sharing sites do resizing themselves.
The way I usually do this is to grab a screen, crop & resize it to show what I want with the detail level I want (and to keep the filesize down), and upload it to some webservice which supports thumbnail-linking on web pages (like this Forum).

[ADCK]

Is there a program for making screenshots of the models? As my PC uses a very hi res and I don't want to use in-game shots for posting pics...

Umm... you can always resize the in-game screenshots before posting.
And many online picture sharing sites do resizing themselves.
The way I usually do this is to grab a screen, crop & resize it to show what I want with the detail level I want (and to keep the filesize down), and upload it to some webservice which supports thumbnail-linking on web pages (like this Forum).

I'm aware of that, but thats not really the point. Theres only so much you can do with the debug console and screen shots, they're not really good for just displaying models. Frame's model viewer is along the lines of what i'm talking about, but it doesn't seem to handle shaders or normal maps.

[Kaks]

Using the console, you can display ship models in the comfort of a mission info screen, there was a thread about viewing ships models inside Oolite not too long ago, with the relevant information in it.

Shouldn't be too difficult to track down.

[JazHaz]

Is there a program for making screenshots of the models? As my PC uses a very hi res and I don't want to use in-game shots for posting pics...

Umm... you can always resize the in-game screenshots before posting.
And many online picture sharing sites do resizing themselves

FlickR.com is quite useful for this, as it generates several different sizes upon uploading. (And if you have a Pro account, you can access the original size too).

[ADCK]

Anyways, Back on topic, (This topic is about shader versions of Sungs textures that i've made for those that have forgotten.)

Textures: Done,
Permission: Granted,
All systems go.

Er... or not... One final step to go...
Anyone know a place that's reliable (and free) that i can upload a 23 Mb file to?

[Greyman]

Try box.net - most people here use it to share their files. They have a 25MB file size limit.

And don't keep us waiting too long!

[ADCK]

Try box.net - most people here use it to share their files. They have a 25MB file size limit.

And don't keep us waiting too long!

Ah thought it was a 20MB limit there, uploaded, starting new thread.

[Greyman]

Yeah, thank you for being bored!

[ADCK]

OoDebugConsole.exe *32 Strikes again, it REALLY doesn't like my PC, i'm assuming it's a mix of using a 64 bit system and a conflict with my dual monitor software.

My computer came to a complete stop, and the quad core processor was running at 100% and was alarmingly making a humming noise... I went and Ctrl Alt Del'd and after about 2 mins of waiting for the Task Manager to come up I found the cause of the problem was none other than OoDebugConsole.exe *32 with 5 instances of it running (I did a lot of debugging tonight)

I guess I should stop running it.

[allikat]

The humming sound is quite likely your case/cpu fans winding up to full speed. Normally most machines will run them well below full speed to keep things quiet.
If you are worried, then running something like coretemp speedfan or CPU-ID Hardware monitor will allow you to keep an eye on things.
Core temperature for most cpus is entirely safe up to 60c, many can cope with more but 60c is a good point to say "here, this chip is getting darned warm!"

The other possible source for humming sounds is the memory manager paging things to the hard-drive. Which normally happens if you are running too much for your RAM to hold, and it uses the HD to put un-used stuff. Normally this is not a problem, it's when so many things are running it starts having to put running tasks onto the HD. This is when things slow to a complete crawl.

My advice in that case: Just check the task manager after a while, and make sure you're only running one instance of the debugger.

[Svengali]

...the cause of the problem was none other than OoDebugConsole.exe *32 with 5 instances of it running (I did a lot of debugging tonight)

2 processes were always there on my XP Pro machine (maybe socket + proggie) in both versions of the console, but 5?

And are we talking about processes or instances? Instance would mean that the console is started a few times, processes are another thing. A application can have multiple processes...