. /../Input issues/ 1
written by Elfhara on Jan 20, 2010 15:07
Hello everyone,

another wannabe stardrifter joins your ranks.

First of all, congratulations to the creators and all those that continue to improve this experience.

I just downloaded the 3.1 build of noctis iv and made it run smoothly on XP SP2 (2gb ram, core2duo@2.13, 256MB AtiRadeonX1900XT, AsusP5B mb, about 4-years-old system, in general).

(unzipped > go!.exe > play)

there are two problems however. the first is that in contrast to your screenshots, the game looks very pixelated on my system. Is there a way to change the resolution or is it something else?

the most important is that everything works fine until I press a key on the keyboard other than the arrows. when I do that, the game will pause and will not respond further.

anyone knows something about this?

Also, is there anything else I should download to improve or make the most out of the experience?

And last but not least, I am sorry in case I should have continued in an existing thread instead of making a new one but I didn't find any related topic.

Thank you.
r'lyeh sweet r'lyeh
written by Neuzd on Jan 20, 2010 15:37
About the aspect of the game, I think you might just have overlooked the screenshots, or maybe you watched the old NoctisV development shots.
Almost all NoctisIV screenshots posted are not in scale, nor have their quality reduced.
Noctis is a DOS program and so the graphics are restricted to 320x200 px.

For your input problem, it comes as a new one.
To control your movements use the mouse, and maybe you can try explain better what you did before the game froze and also try to take a screenshot (with the print-screen key, if Noctis is effectively frozen).
written by Elfhara on Jan 21, 2010 12:20
omg. this program is unbelievable. now I know where bioware took inspiration from to bring mass effect to life. anyway, thanks for your answer.

about the input problem.
it was my bad. the thing is that I have changed my keyboard input method to dvorak. it seems that noctis has a problem with this even if i ctrl-shift the input method back to qwerty. i had to completely remove the dvorak method as an option from the control panel in order for the game to respond right.

i searched a little on youtube and found out that my display quality is more or less the same with everyone else. i was just worried because for some reason the screenshots provided in the manual seem to be of better quality overall (better distinguishable fonts in the front main window in contrast to the more fuzzy I get, current option highlighted by a smooth blue solid frame instead of a similarly fuzzy border). anyway, that's not really an issue I was just wondering if there is a problem with me.

i ran into another problem however. sometimes, when I tried to set local target to specific planets (it happened in two different S06 systems), all the hud feedback disappeared and the screen kept stuttering until I Esc-canceled.

That's all. Thanks again.

oh! and neuzd I really enjoyed your diaries.
└> last changed by Elfhara on January 21, 2010 at 12:53
r'lyeh sweet r'lyeh
written by Neuzd on Jan 21, 2010 15:10
The screenshot in the manual you're talking about comes from Noctis III or could even be from a development version of NoctisIV.
The final fonts are bigger, less blocky and yes this gives them a fuzzier look.
We already realized of the inconsistency of some of the photos in the manual (specifically the pulsar shot: that doesn't look like other pulsars, and it is also different to what you'll see if you travel to that location).

For the other problem, if the info you provided are correct, there's nothing to worry.
Siply put, S06s never have any orbiting bodies, so the StarDrifter's computer is just replying to your command with something like a "Set local target to wha?!?".

Turn on the "Local Planet Finder" to know the status of the current system.

Thanks for the comment on my diary, sadly the content there is a bit out of date as I started that project when I was a very ignorant kitha, and I was also confined to play NICE.
I should seriously think to "reboot" it.
written by Elfhara on Jan 21, 2010 15:29
Neuzd said:
For the other problem, if the info you provided are correct, there's nothing to worry.
Siply put, S06s never have any orbiting bodies, so the StarDrifter's computer is just replying to your command with something like a "Set local target to wha?!?".
haha. this is very good to know. thanks again and good luck on your efforts.
written by Cryoburner on Jan 21, 2010 17:36
Elfhara said:
sometimes, when I tried to set local target to specific planets (it happened in two different S06 systems), all the hud feedback disappeared and the screen kept stuttering until I Esc-canceled.
I believe I've had that happen before as well. Occasionally, you get stuck in targeting mode, and can't move or escape from it just by clicking the mouse as you normally would. I think you can fix it just by right clicking a few times in quick succession though.

I tried Dvorak some years back as well, and even swapped the keycaps on a spare keyboard to match its layout. I wouldn't mind giving it a try again, though it would probably lead to increased typos when alternating between that and Qwerty. : )

As for the blurriness of Noctis, it's always been that way. On the plus side, the low resolution does a nice job masking any low-detail objects and textures. : ) I suppose it might be effected by how your monitor scales up low resolutions though. It would be nice to have higher resolutions available, but that probably won't come until the next major version of Noctis is released, which was in development some years ago, but got put on hold for a while. Alex mentioned recently that he might be getting back to work on it though. At least he has more processing power to work with now. : P
written by Elfhara on Jan 23, 2010 17:04
thanks for your response

Cryoburner said:
I believe I've had that happen before as well. Occasionally, you get stuck in targeting mode, and can't move or escape from it just by clicking the mouse as you normally would. I think you can fix it just by right clicking a few times in quick succession though.
exactly. either rapidly right clicking or pressing the Esc key, all will work.

Cryoburner said:
I tried Dvorak some years back as well, and even swapped the keycaps on a spare keyboard to match its layout. I wouldn't mind giving it a try again, though it would probably lead to increased typos when alternating between that and Qwerty. : )
i've changed to Dvorak as my main input for quite some time now. and from a point on, switching back and forth between the two methods is not really an issue. i don't know if a dedicated dvorak keyboard would be a solution to my previously posted problem, although an expensive one. eventually, i created an extra account just for noctis.
any suggestion to bypass this incompatibility issue is more than welcome.

take care.
absent more than alex
written by Shadowlord on Jan 31, 2010 21:57
Elfhara said:
sometimes, when I tried to set local target to specific planets (it happened in two different S06 systems), all the hud feedback disappeared and the screen kept stuttering until I Esc-canceled.
Oh, that was a bug. Did you say you were using the regular Noctis IV? You should probably get the latest version of NIV Plus, it has a lot of bug fixes in it.

Neuzd, do you know if you have the fix for that in NIV Plus? There was a fix for it in NICE, so if you have all the bug fixes from it, you probably have it.

If anyone wants more information on it: It didn't check to see if there were no planets, so it was trying to target a nonexistent planet and do stuff with it. Because it was DOS instead of something sane, it then went on to do math which triggered an error message on the bottom of the screen, scrolling the graphics, which was what was causing the screen to appear to shake.

In DOS when you divide by zero, or the like, instead of the program crashing, it displays an error message on the screen and the program continues to run. That's the kind of thing that was happening there.
reading this thread
no members are reading this thread
. /../Input issues/ 1
27852, 13 queries, 0.067 s.this frame is part of the AnyNowhere network