. /../GUIDE: Getting Noctis to run.../ 12
written by Batmanifestdestiny on Sep 16, 2009 01:16
After some tweaking, I managed to get DOSBox to run NIV extremely smoothly!


What I ended up doing to the configuration was this:

set memory to 32 MB, instead of 16

Set the core to always be Dynamic, because if it's on auto, it won't run right

set full resolution to 0x0

make sure that fulldouble is false

Also be very sure that aspect is false

set cycles to max




I think that's all I did. I managed this with DOSBox 0.73, with 8GB memory on a quad-core vista 64, so older computers may run slightly slower. If that's the case, and you don't mind squinting a bit, then set scaling to none, and it will run even faster!
journeyman
written by Stargazer on Sep 16, 2009 16:01
Thanks for the heads-up, BMD!

I can confirm that this absolutely works! There is still an odd frame-stop happening every now and again, I can't seem to trace down the source, but usually, it works fantastic here as well with DosBox 0.73.

By the way, if these settings works for you, you could try to set the scaler to advmame3x to get some anti-aliasing. Also, to have Noctis automatically load up when you start dosbox, add these lines to the end of your Dosbox config (this assumes Noctis is installed at "c:\noctis\")

[autoexec]
mount c: c:\noctis\
c:
cd modules
noctis.exe
I have tested with the original Noctis, NICE, and Noctis IV Plus. All of them works just fine on my machine using those settings: starmap, GOES, pictures and everything seems nominal.
written by Cryoburner on Sep 17, 2009 08:37
I decided to try out Noctis in DOSBox again, and while Noctis IV's performance still isn't exactly stellar on my Athlon 3500+, I ended up being surprised by something else. First I'll detail my results with Noctis IV. : )

To be able to switch settings with relative ease and make setup a bit easier, I used D-Fend Reloaded to create and run a DOSBox profile for Noctis. I played around with the settings, and found that only a couple of these listed seem to be of major importance. Setting the core to dynamic and the cycles to max on the CPU tab seemed to be the important ones. Increasing the memory is probably pointless since Noctis doesn't use extended memory. The graphics settings had a relatively minimal effect for me, though I kept mine at normal2x, original fullscreen resolution, since that looked fine on my CRT.

The results were interesting. Both inside the stardrifter and on the surface of planets, I averaged around 4 frames per second. While that may seem low, it surprisingly remained borderline playable, with navigating menus on the stardrifter being the only major concern. The interesting part is that when on the roof of the stardrifter, Noctis actually runs at full speed, or possibly even faster with speedup enabled. At first, I thought this might be related to speedup disabling the framerate limit on the roof, but further testing disproved this. Even with a version of Noctis IV that has the limiter completely removed, or in NICE with speedup also enabled within the drifter, the framerate remains around 5 times faster on the roof than anywhere else.

Following this, I decided to try out Noctis II. This was the real surprise. Not only was Noctis II running at full speed everywhere, but it was running with sound. The stardrifter menus beep, the surface capsule audibly launches and even thumps off the ground. On the surface, the rain pours and thunder crackles during storms, while the wind howls across frozen tundras. I always thought Noctis was fine without sound, but having heard how well it works in Noctis II, I'd love to see it reimplemented in Noctis IV Plus. It might not play natively on modern computers, but works beautifully in DOSBox.

Anyway, I also tested Noctis I and Noctis III, and both of those run at full speed as well. This is on my 3500+, a processor that came out five years ago. Pretty much any desktop released in the last few years should be able to handle Noctis I, II, and III at full speed in DOSBox. Noctis III is quite similar to Noctis IV as well, so it's strange that they perform so differently when off the stardrifter's roof. Something must have changed in Noctis IV that significantly hurts its performance, so it might be worth looking for a solution. I did notice that activating 'disable display' on the main menu seems to improve performance slightly, so maybe it has something to do with the way the transparent text is being handled. The text does disappear when on the roof, after all. Of course, no such text is visible when on planetary surfaces, and performance appears roughly equal in either location. It's definitely something to look into though.
doing pushups
written by Megagun on Sep 17, 2009 19:30
Cryoburner said:
Following this, I decided to try out Noctis II. This was the real surprise. Not only was Noctis II running at full speed everywhere, but it was running with sound. The stardrifter menus beep, the surface capsule audibly launches and even thumps off the ground. On the surface, the rain pours and thunder crackles during storms, while the wind howls across frozen tundras. I always thought Noctis was fine without sound, but having heard how well it works in Noctis II, I'd love to see it reimplemented in Noctis IV Plus. It might not play natively on modern computers, but works beautifully in DOSBox.
Sound could be implemented fairly easily by making use of Xnice. Can't remember if NIV+ is Xnice-enabled though, so it might have to be ported over first.
written by Crystal on Oct 07, 2009 03:00
Hmmm... I can't seem to get this to work.

I've used D-Fend Reloaded for the configuration and tweaked everything, but when I run it every time it always says: This program cannot run in dos mode (or something along the lines of that).

I've changed all the settings Batman mentioned, but it still doesn't work. Does anyone know what I'm doing wrong?

Edit: And by the way, I'm running D-Fend Reloaded on Crossover Games (on a Mac).
written by Lornex on Oct 07, 2009 03:04
Oops. That last post by Crystal...that meant to be by me. Sorry about that.
r'lyeh sweet r'lyeh
written by Neuzd on Oct 07, 2009 07:19
Make it simple, dude.
Use the native mac DOSBOX release.
http://www.dosbox.com/download.php?main=1

Anyways Noctis doesn't run fast enough on my iMac, but as I mentioned somewhere else, the performance increase is definetely noticeable, so it could be that a more recent machine is powerful enough.
written by Lornex on Oct 07, 2009 14:18
Neuzd said:
Make it simple, dude.
Use the native mac DOSBOX release.
http://www.dosbox.com/download.php?main=1

Anyways Noctis doesn't run fast enough on my iMac, but as I mentioned somewhere else, the performance increase is definetely noticeable, so it could be that a more recent machine is powerful enough.
I am using dosbox and edited the configuration settings, but it still doesn't work. (I'm using 0.73) I just get that same message: This program cannot be run in dos mode...
doing pushups
written by Megagun on Oct 07, 2009 14:27
Run noctis.exe in the modules folder; not go!.exe
r'lyeh sweet r'lyeh
written by Neuzd on Oct 07, 2009 14:29
In about 3 hours I'll be able to tell you how to have it running.
For starting you could try running directly /modules/noctis.exe, instead of the GO!.exe.

Anyway, for the 1000th time, do not expect this to be the final solution, Noctis will probably run terribly slow anyway.
I am a Mac user, and I installed Windows XP JUST to play Noctis in a safe environment.
written by Lornex on Oct 14, 2009 23:50
I got Noctis to work on dosbox 0.73, and it works virtually flawlessly. I can't believe I was stupid enough not to remember about the modules folder and noctis.exe...how embarrassing.
written by Jarmihi on May 28, 2010 15:34
I'm quite new to DOS (I've only been using computers since the late-90s), so I am clueless as to how to configure these settings. Would someone please lend their time and dumb down for me the process in the first post by Batmanifestdestiny?

doing pushups
written by Megagun on May 30, 2010 13:05
I'd advise to -instead- use VNoctis, but Only if your PC has AMD-V or VT-X hardware virtualization acceleration. If you have a recent AMD processor, it most likely will. If you have a recent non-budget Intel processor, it probably will too..

The VNoctis image: http://mooses.nl/nice/relatedprojects/vnoctis/vnoctis-freedos.7z

To use it, you'll need VirtualBox: http://www.virtualbox.org/

I think all you need to do is create a new FreeDOS machine in VirtualBox, skip the 'create new harddrive' bit and then assign the new machine the VNoctis .vdi image.

See: http://anynowhere.com/thread/4522 for the relevant thread. -- Please move any further discussion regarding VNoctis there as to not spoil this thread with unrelated information and keep all VNoctis discussion centralized..
written by Silvercoon on Nov 28, 2010 21:27
I'm running DOSBox in Linux (Peppermint OS). I have a Pentium 4 (3.33 Ghz), with 512 MB RAM.
Noctis has always been sluggish on my current system, but when I tried Batman's config, here is the result:

X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 139 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Value in failed request: 0x15
Serial number of failed request: 331
Current serial number in output stream: 332

I have scaled down the mem to 24, but it still doesn't work. I kept getting a message: 'Memory sizes above 31 MB are NOT recommended.
Stick with the default values unless you are absolutely certain.'

I used to run this on a Win98 system with 64 MB RAM, and barely any tweaking of DOSBox's config file. What's the problem here?
ah didn't learn anything!
written by Selbio on Nov 28, 2010 21:52
Silvercoon said:
I'm running DOSBox in Linux
Don't. Linux has dosemu, which is much, much better than DOSBox in terms of performance and compatibility. Noctis runs perfectly with native performance under it.
reading this thread
no members are reading this thread
. /../GUIDE: Getting Noctis to run.../ 12
39585, 13 queries, 0.121 s.this frame is part of the AnyNowhere network