Questions from a icr2 newbie

[powersteamracing]

Hello everyone

So I'm trying to do some Indycar racing, and after some frustration with trying to simulate Indycars in N3, I finally figured out how to get icr2 to work on my laptop.

I managed to get icr2 to work with the help of DosBox, but I have some questions on icr2

#1. Is there a way to full screen the game? Using DosBox (I'm running Vista) I only get a small window. It's not a huge problem, but it is smaller than I'd like.

#2. What is the difference between Linear and Non-Linear steering?

#3. I always thought Indycars had a boost option or something. Does this exist in icr2? I ask because sometimes I just feel like the cars are just so much faster than I am.

#4. When I've played N3, the default ACE setup has almost always been acceptable for me to run top 10 on 100% AI difficulty. But in icr2, at 97% AI strength, the ACE setup seems like it's only good for 30th to 25th. Is the game much harder by default, or do you have to work harder on the setup than N3?

#5. How do I add newer carsets and the new body I see screenshots of in the newer posts?

#6. I am using a Logitech controller, and it seems to calibrate fine in N3, but in icr2 (using DosBox remember) the calibration scale jitters all around. Is this just icr2 being an old game and stubborn with newer controllers?

#7. I know it's a Dos game, but I find a lot of the screenshots I see from other people the game looks amazing, but I find the graphics seem choppy, and very dated right out of the box. Are there some graphics updates or something I'm missing?

#8. Aren't there spotters in Indycar racing? I keep expecting to hear "car low" but it never happens.

#9. Any other info a newbie might need. I'd like to try and run an Indycar season. Any help would be awesome.

Thanks in advance everyone.

[Oli]

Hi there,

for the use of DosBox I have found one way that works very good.
It very often has 30fps and it just goes a few time minor than that when passing the pit lane and the circuit goes much wider...
For good DosBox setting first copy your DosBox (0.74) settings to a save place.
Then paste it with the settings in my other post.
Maybe the problems from you question #7 also will be solved.

BOOST KNOB.
There is one boost knob in ICR2. And you can change the level of the boost with the numbers on your keyboard. The key "1" means that you wanna drive with turbo set on 1.
Very slow acceleration and only to recommend when you want to learn the groove of a totally new course.
Turbo 1 is fuel saving but still very slow...
Turbo 9 is the fastest turbo setting.


NEW CARSETS
For adding new carsets you have to add a new folder into your ICR2/CARS directory named the same way as the carset files name.
For example CARS96.DAT into ICR2/CARS/CARS96 or REYNRDXX into ICR2/CARS/REYNRDXX .
And you'll need to have the .DAT file and the DRIVERS2.txt into this directory.
When starting the game it should give you the option "car sets" under "driver info".
There you can choose between the carsets.

---

This version of the DosBox Options was new for me a few weeks ago and works very well! As mentioned in the other post it has up to 30fps.
The DosBox 0.74 options should have the settings between the marks " ".
You will have to play around with the fullscreen size. I have put it to 1152x864. You should be able to choose any other size that you want to have.
And of course you have also to alter the names of your ICR2 directory at the end of the config file. Hope it works.



"# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
# Lines starting with a # are commentlines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
# fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# Using your monitor's native resolution with aspect=true might give the best results.
# If you end up with small window on a large screen, try an output different from surface.
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# (output=surface does not!)
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
# autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
# sensitivity: Mouse sensitivity.
# waitonerror: Wait before closing the console if dosbox has an error.
# priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized.
# pause is only valid for the second entry.
# Possible values: lowest, lower, normal, higher, highest, pause.
# mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems. 1024x768


fullscreen=false
fulldouble=false
fullresolution=1152x864
windowresolution=1152x864
output=overlay
autolock=false
sensitivity=100
waitonerror=true
priority=highest,highest
mapperfile=mapper-0.74.map
usescancodes=false

[dosbox]
# language: Select another language file.
# machine: The type of machine tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=vesa_nolfb
captures=capture
memsize=31000

[render]
# frameskip: How many frames DOSBox skips before drawing one.
# aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler: Scaler used to enlarge/enhance low resolution modes.
# If 'forced' is appended, then the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=
scaler=hq3x

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000).
# 'max' will allocate as much cycles as your computer is able to handle.
#
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=pentium_slow
cycles=max
cycleup=5000
cycledown=20

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 1024, 2048, 4096, 8192, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=11025
blocksize=1024
prebuffer=20

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
# See the README/Manual for more details.

mpu401=none
mididevice=none
midiconfig=

[sblaster]
# sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12.
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none.
# oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
# Possible values: default, compat, fast.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=default
oplrate=11025

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 5, 6, 7.
# ultradir: Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=false
gusrate=44100
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=false
pcrate=22050
tandy=off
tandyrate=22050
disney=false

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=none
timed=true
autofire=false
swap34=false
buttonwrap=false

[serial]
# serial1: set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq (optional).
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms: Enable XMS support.
# ems: Enable EMS support.
# umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=auto

[ipx]
# ipx: Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.
# You can put your MOUNT lines here.
loadhigh xms umb 999999999999999999999999999999999
mount c c:\indycar
loadhigh=C:\DOS\Himem.sys
c:\

loadhigh=C:\DOS\EMM386.exe MAX=9999999999"

[CowtownBob]

well, about time you said something! you only sat in that dark corner over there for 2 years....

#4 ICR2 starts you off with a pretty baseline setup. it can take a while to work up a good setup. there used to be some online - might even be some in the archives section. this recent thread discusses other info you'll need once you have a setup you can live with, to find some parity with the AI. and answers question #2, as well

#7 make sure you start the program with the -h flag: (ie. indycar.exe -h) that way, it uses the advanced SVGA graphics then available on the new top-line 486 machines - 640x480, 256 colors.

beyond that, it's just a matter of the car and track artists, combined with the more realistic cars and tracks now available. better shapes and larger texture maps. and those of us who do that stuff thank you for your testimonial

#8 nope, no spotters. that's what mirrors are for in real life, they've been used in open-wheel recently - on ovals. at the time of the game they weren't used at all. road courses would take a whole spotting staff for each car, and there was enough chassis/engine/tire variation that tight packs didn't develop on ovals.

#9 pages and pages of it - all at your fingerclicks. dig around, see what you come up with. be forewarned - you're gonna be hitting some dead forum links. long story - it's out there if you want to read about it. dead off-site links, too.... and ask. somebody's got it.

[powersteamracing]

awesome, that helps a lot. But this turbo thing, when i press the number keys, it just turns off textures. what is the key command for boost?

---

NEW CARSETS
For adding new carsets you have to add a new folder into your ICR2/CARS directory named the same way as the carset files name.
For example CARS96.DAT into ICR2/CARS/CARS96 or REYNRDXX into ICR2/CARS/REYNRDXX .
And you'll need to have the .DAT file and the DRIVERS2.txt into this directory.
When starting the game it should give you the option "car sets" under "driver info".
There you can choose between the carsets.

When I go to the driver info section I only have 3 options: Player, Opponents, and done.

---

nevermind about the carsets. It's working now.

[Pavel 69]

Hi and welcome,

#2. Liner steering is for wheels. N3 has the same option.

#3. Yes, Indycars have turbo boost. Most of setups already have it set to maximum 9.

#5. All carsets need to be in CARS folder. 'Select Carset' option will appear in game drive option menu when you have more than on carsets.

#6. It's maybe problem with your Logitech. I use Logitech G25 wheel and it work very well here.

#7. There much more detailed carshapes for icr2 than default one. Also there are many track addons with better graphics. You may check 'Tracks on forum' thread at the top of the forum.

#8. We have all tracks for IRL 1996 - 2005 seasons, later seasons don't have few tracks. For CART/Indycar there are many tracks but still no full season. 1993-1995 years are near complete (we still don't have right Vancouver).

About carsets. There are Indycar/IRL carsets for all years from mid 80's til 2011. Check this page (you need to be registred) http://worldindycar.webs.com/

[RacerBG]

Well for some reason ICR2 cannot got to "full screen" in larger displays (bigger than 1024x768). I mean that in left and right there are blank black spaces.

[Pavel 69]

I have 16:9 monitor, resolution is 1600x900. I have WinXP and run ICR2 using VDMSound on full screen. Only there are black bars on left and right sides of picture because ICR2 use 3:4

[jack deth]

The joystick jitter seems to be a problem with DOSBox joystick input. I have done some testing but cannot get it to go away.

I have tested the VDMSound and my joystick (Xbox 360 controller) works perfectly. However, in DOSBox, the center point jitters around even after calibration.