{"id":19891,"date":"2013-07-19T08:55:25","date_gmt":"2013-07-19T07:55:25","guid":{"rendered":"http:\/\/www.hsw.hu\/?p=19891"},"modified":"2013-07-19T08:55:25","modified_gmt":"2013-07-19T07:55:25","slug":"iracing-frissitesek-2013-2-szezon","status":"publish","type":"post","link":"https:\/\/www.hsw.hu\/?p=19891","title":{"rendered":"iRacing friss\u00edt\u00e9sek 2013. 2.szezon"},"content":{"rendered":"

\"lotus-49-on-track1\"<\/a>Az iRacing g\u00e1rd\u00e1ja az eddig megszokottakhoz hasonl\u00f3an ez\u00fattal is a szezon v\u00e9g\u00e9re id\u0151z\u00edtette a program nagyobb \u00e1talak\u00edt\u00e1s\u00e1t. Term\u00e9szetesen ez\u00fattal is sz\u00e1mtalan \u00fajdons\u00e1g \u00e9s jav\u00edt\u00e1s v\u00e1rja a j\u00e1t\u00e9kosokat kedvenc programjukba.
\nA csapat most kiadta az \u00fajdons\u00e1gok r\u00e9szletes list\u00e1j\u00e1t, amit term\u00e9szetesen a HSW-n is elolvashattok angol nyelven.<\/p>\n

Website:<\/strong><\/span><\/p>\n

Leagues Page\u00a0<\/strong><\/p>\n

Members\u00a0<\/strong><\/p>\n

– League admins can assign members a nick name
\n– League admins can assign members a car number<\/p>\n

League Info\u00a0<\/strong><\/p>\n

– League admins can tag their leagues with keywords and other pre-set filter options under the\u00a0Set League Filters button. This information allows members to find leagues through filtering
\nand is a complement to finding leagues via name search.
\n– Admins can create a comma-separated list of keywords from a drop-down or enter new keywords\u00a0which will be saved for use on other leagues. The Save button needs to be clicked for keywords
\nto take effect.
\n– Keywords can be removed from the list, thereby, disassociating the league from those\u00a0keywords.
\n– Checked pre-set options are saved or removed immediately as the admin clicks on the\u00a0checkboxes. This allows members who are filtering for leagues to see leagues in real-time as
\nadmins make their changes.<\/p>\n

League Directory\u00a0<\/strong><\/p>\n

– Next Page and Previous Page buttons are working.
\n– A new Filters button was added. This brings up a form allowing members to search for leagues\u00a0via pre-set filter options and keywords. This compliments the league name search option.
\n– Members can create a comma-separated list of keywords from a drop-down and\/or select from\u00a0pre-set filter options. If filtering with keywords only, the member must click on the Done
\nbutton to set the filter.
\n– Clicking on the pre-set filter options immediately filters the list of leagues as options\u00a0are selected\/unselected. The list of keywords are automatically used in combination with the
\npre-set filter options.<\/p>\n

The filtering is persisted until the member clicks the Reset Filters button or clears cookies\u00a0from the browser. This allows the member to view details of\/join the filtered leagues without
\nlosing the filtered list, even through multiple sessions.<\/p>\n

Preferred Car Number\u00a0<\/strong><\/p>\n

– Has been changed to allow for three digits<\/p>\n

File a Protest\u00a0<\/strong><\/p>\n

Filing protests can now be accomplished by clicking „File Protest” in the header of the member\u00a0site. Fill out the appropriate information, and submit. In some cases, you WILL have a time
\nlimit to get these protests into the system.<\/p>\n

You will be emailed a notice of receipt of the submission. These protests will be sent to the\u00a0iRacing.com Appeals Board, and the appropriate measures will be taken to resolve them. This
\nnew system will help us utilize a more orderly way of resolving problems and issues, as well\u00a0as keep you informed of the situation as it progresses.<\/p>\n

Downloading Software\u00a0<\/strong><\/p>\n

The page that allows you to download the iRacing software just got smarter. It will now offer\u00a0an appropriate download option for the operating system you visit it with, as well as offer a
\nchoice of alternate download options, if that’s needed. The page has also been updated to be\u00a0friendlier and easier to use. Check it out at
\nhttp:\/\/members.iracing.com\/download\/member\/noservice.jsp<\/a><\/p>\n

– At this time there is only the PC version of software available. The Mac version will be\u00a0released in the next few weeks.<\/p>\n

Awards\u00a0<\/strong><\/p>\n

– Consistent Finish awards were added. These awards are given for finishing 2, 5, or 10 races\u00a0at your own iRating or higher. There are awards for both road and oval, for a total of 6 new
\nawards. These awards are not retroactive.<\/p>\n

Race Guide\u00a0<\/strong><\/p>\n

– Improved the performance of the Race Guide\u00a0Full Grid Control for League Racing
\n– When configuring league races you now have the option to configure the grid in advance\u00a0rather than relying on a qualifier. To do so you should select the new league session type
\n\u201cOpen practice + race\u201d. The session is configured exactly the same as other sessions except\u00a0you will now see a link to \u201cClick here to configure your field and grid\u201d. This session type
\nis the only one that allows you to configure the grid because all of the other configurations\u00a0either don\u2019t have a race component or have a qualifier component that will determine the grid.
\n– When you select \u201cOpen practice + race\u201d you will see a \u201cClick here to configure your field\u00a0and grid\u201d link. When you click on the link you will see the \u201cLeague Session Grid Builder\u201d
\nuser interface.
\n– Similar to tournament session grids, configuring a league session grid is a 3 step process:<\/p>\n

Load drivers into the race field. You can load all league drivers, all league drivers who\u00a0participated in a prior race in the same season, or individual league drivers selected from a
\nlist.<\/p>\n

Move drivers from the race field onto the grid. You can drag and drop drivers or use one of\u00a0the grid algorithms to set the grid automatically. When loading drivers from a prior race the
\nsystem will use that race\u2019s finishing positions to determine a position for this race.
\nAdditional drivers will be slotted behind drivers who participated.<\/p>\n

Click Done to save the grid.<\/p>\n

As with tournament sessions you have the option to drag and drop racers on the grid. This\u00a0gives you total flexibility to set the grid exactly as you want it. For example, let\u2019s say
\nyou are using a sequential gridding algorithm to pull racers from your most recent league\u00a0race. Let\u2019s also say that one of the drivers did something and the league administrator has
\nissued a penalty that the driver should start at the back of the field. After applying the\u00a0sequential algorithm you can drag the driver from the top spot to the back of the field.<\/p>\n

It is possible to create the session without setting the grid. This should allow people to\u00a0configure their entire season in advance and configure the grid prior to each race. If you
\ndon\u2019t set a grid the session will allow any league drivers to enter and the grid will be set\u00a0by iRating<\/p>\n

The grid is presented as a two-column list that supports dragging and dropping drivers to\u00a0change their position in the grid. In oval-racing terms the left column is the inside lane
\nand the right column is the outside lane. Each grid position is presented as a rectangle with\u00a0the driver\u2019s name. The current row and grid position of the driver is shown in a box to the
\nleft of drivers in the left column and to the right of drivers in the right column.<\/p>\n

A current limitation of the system is that there is no way to delete the grid. At the moment\u00a0the only way to delete a grid after you have saved it is to cancel your session and recreate
\nit.<\/p>\n

Simulation:\u00a0<\/strong><\/p>\n

Teams\u00a0<\/strong><\/p>\n

A prior build added the ability for your teammates to become your „crew chief” (though only\u00a0one at any given time). Doing so allowed them to make „black box” changes to request
\nadjustments at the next pit stop.<\/p>\n

This build introduces the ability for your teammates to help out with setting up your car in\u00a0the garage. Apply whatever term fits your mental model for this; possibly „head mechanic”,
\nthough internally we call this person the „garage editor”. As with the crew chief, any of \u00a0your teammates can take-on and give-up the garage editor role at will, but only one person may
\nclaim that role at any given time.<\/p>\n

You can envision visiting the garage screen as picking up a clipboard that has the team’s\u00a0setup sheet on it. In order to make any changes, you need to request that you become the
\nteam’s „garage editor”, and that the team’s car be physically put into the garage, where the\u00a0mechanics can flail away at it with tools, and the effects of any updates can be measured.
\nYou do this by clicking the green „edit” icon near the upper-right corner of the garage\u00a0screen. If you are the only person on your team that is connected to the session, the „edit”
\nbutton is automatically clicked for you. If the icon is gray, then the car is forbidden from\u00a0being placed into the garage (generally after a race session starts).<\/p>\n

While the car is in the garage, the [Drive] button on the session screen will be disabled, and\u00a0will be shown as [Garage], instead. The helmet and name of the person that is adjusting the
\ncar is displayed on the garage screen to all the team’s members. All of the teammates can see\u00a0the changes the garage editor is making to the car’s setup each time the setup finishes „tech
\ninspection”. Many changes tech quickly and are automatically sent, but some require the\u00a0[Apply] button to be clicked, or for the [Apply] to be automatically executed.<\/p>\n

All changes to the team’s car setup are tentative, and will only be committed when the garage\u00a0editor clicks the garage screen’s [Done] button. Clicking on this button relinquishes the
\ngarage editor role, and physically releases the team’s car from the garage with the latest\u00a0changes applied to it. The garage editor can discard any changes they’ve made and revert to
\nthe team’s car as it entered the garage by clicking [Cancel], the „edit” icon, or [X] to close\u00a0the garage screen, and then confirming that the changes are to be thrown away. Discarding the
\nchanges from having clicked the „edit” icon or the [X] will also give up the garage editor\u00a0role.<\/p>\n

The garage editor has access to all of the car setups that iRacing includes, any setups they\u00a0have stored locally, and any setups that have been „shared” by other users in the session.
\nThey do not have access to setups stored on the disks of other team members. If a particular\u00a0member of your team has a setup you wish to use, let them become the garage editor so that
\nthey can load it, and then hit [Done] to apply it to the team’s car. Any other team member\u00a0can then make additional changes to that setup.<\/p>\n

No one on the team will be allowed into the garage screen until the team has a car setup.
\nWhen the team’s driver first connects to the session, their last-used setup is loaded and\u00a0applied as the team’s car setup (unless this is a fixed-setup race, in which case the
\nappropriate fixed setup is used, instead).<\/p>\n

To prevent the loss of any changes you might be making to the car’s setup near the end of a\u00a0session, you can continue to edit your team’s setup across session transitions (for example
\nfrom practice to qualify, or qualify to race). Except in fixed-setup sessions, where your\u00a0garage editor status is revoked, and the „preferred” or „mandated” setup for the session is
\nforced onto the car.<\/p>\n

The garage editor can exit the garage with a setup that fails tech inspection, but the driver\u00a0will not be allowed into the car until the setup is modified so that it passes tech.<\/p>\n

Collidable Cones\u00a0<\/strong><\/p>\n

– All cones at all tracks are now collidable.<\/p>\n

Reflap Car\u00a0<\/strong><\/p>\n

– The Splits\/Delta system has been expanded to be able to show a transparent car representing\u00a0your currently selected reference lap. We call this a Reflap Car.
\n– By default the Tab key cycles through the modes, including Off. The key can be remapped in\u00a0the Options screen. First time into the sim we default the Reflap car to being on. There are 6
\nreference lap modes:<\/p>\n

Off<\/p>\n

All-time Best Lap – Your fastest lap ever recorded<\/p>\n

All-time Optimal Sector – your fastest sectors even if they were not part of the same lap<\/p>\n

Session Best Lap – best lap this session<\/p>\n

Session Optimal Sector<\/p>\n

Session Last Lap – the last lap you drove<\/p>\n

– The Splits\/Deltas function in all modes, but the Reflap car is only viewable in Testing or\u00a0Time-trial events.
\n– The UI will hide itself as you enter the grid to start a race, but tapping the Tab key will\u00a0make the UI visible again.
\n– The transparency of the Reflap car is adjustable via an app.ini setting:<\/p>\n

[Graphics]\u00a0<\/strong><\/p>\n

reflapCarTransp=0.350000 ; Set level of transparency for reference lap car.<\/p>\n

– There is a hotkey to toggle the display of the ReflapCar, the default keypress is ctrl-c.
\n– There is a Reflap car button in the delta time window, that if clicked toggles the Reflap\u00a0car.<\/p>\n

Weather\u00a0<\/strong><\/p>\n

– You can now control some weather parameters for Hosted sessions and off-line Testing. There\u00a0is no rain.
\n– Temperature, from 65\u00b0F to 90\u00b0F
\n– Humidity, from 0% to 100%.
\n– Humidity is combined with fog – continuing up past 100%RH, you can select a fog level from\u00a01% (light fog) to 100% (heavy fog). Note that the maximum fogginess level is far beyond what
\nany race organizer would consider to be „safe” conditions under which to race – especially at\u00a0a fast race track. You should experiment with your desired fog level in testing sessions
\nbefore creating a hosted session using such conditions. 25% is probably a good real-world\u00a0safe level of fog in which to race.
\n– Wind speed, from 0MPH to 30MPH
\n– Wind direction, specified as „from which direction is the wind blowing?”, with 8 selections
\non the compass.
\n– Cloud cover. „Clear,” „Partly Cloudy,” „Mostly Cloudy” and „Overcast.”
\n– You can choose to specify the temperature in either \u00b0F or \u00b0C. You can choose to specify the\u00a0wind speed in either MPH or KPH. Regardless of how the session’s host specified them, the sim
\nwill display the values in the units you’ve chosen in-sim.
\n– You can also choose „Realistic” weather. The sim will randomly choose weather conditions\u00a0that, on average, meet the conditions that we specify on a track-by-track basis. The values
\nthat are randomly chosen will have the same limits as listed above. Weather conditions can\u00a0vary slightly during the session (the temperature can change, and the wind can be variable).
\nNote that wind gusts can go over the 30MPH max. At a night event, the realistic setting will\u00a0bias towards lower temperatures and higher humidity than a daytime event.
\n– All official iRacing sessions continue to use the usual iRacing Default weather conditions.\u00a0But, we have changed the iRacing Default weather to now be „Partly Cloudy”, where in the past
\nit used to be „Clear” even if you saw a cloudy sky. This change will result in the track\u00a0temperature being a couple of degrees cooler, which will produce a subtle difference in lap
\ntimes and tire feel.
\n– Cars will drive differently as the weather changes. You may find that you need to alter your\u00a0setup to get the most out of the car under different weather conditions.
\n– Whenever you join any session, the sky (which defines things like the sun position, lighting\u00a0conditions, reflections, and shadow angles) will be chosen at random to match the selected
\ncloud cover setting.
\n– Cars turn on their headlights on foggy days.<\/p>\n

Tech Tracks\u00a0<\/strong><\/p>\n

– Tech Tracks are essentially tracks that, for one reason or another, are unfinished iRacing\u00a0tracks but are to the point of being driveable.
\n– For a track to be considered a Tech Track, the track is not on our current production list\u00a0to complete. We may someday complete a given Tech Track, OR NOT. We are making Tech Tracks
\navailable because of the many requests we get from real world drivers and members.\u00a0– Tech tracks will not ever be put on a schedule for official series. However they can be<\/p>\n

used for testing or private sessions. They will include race control and grid boxes and can\u00a0be used for private or league racing.<\/p>\n

– The standard license fee of a Tech Track will be US$5.
\n– A Tech Track is what it is, and we will not be actively updating the track in any way unless\u00a0we decide to fully finish it. If we do finish it, we will take the tech track away and issue
\niRacing credit for the purchase price to any member who purchased it. Again, do NOT buy a\u00a0tech track with the assumption it will someday be finished.
\n– Tech tracks will not be part of any volume discount purchase program like the 100% club.
\n– Settings are available in renderer.ini to override the dimensions and density of the laser
\nscan dots. We recommend using the default values, but if you experience poor performance when\u00a0rendering laser scans it may help to reduce the point sizes or density. PointSizeMM specifies
\nthe physical width of each dot in world space (in millimeters) \u2013 dots far away will render\u00a0smaller than points near the camera. PointSizeMax specifies the upper limit of how big of a
\ndot will be rendered on screen (in pixels), and PointSizeMin specifies the size of the\u00a0smallest dot to be rendered on screen (in pixels). The MaxLaserScanVidMem setting specifies
\nhow much video (GPU) memory may be used (at most) to contain the laser scan, lowering this\u00a0value will reduce the density of dots.<\/p>\n

[Laser Scan]\u00a0<\/strong><\/p>\n

MaxLaserScanVidMem=128 ; Max scan density to load into vidmem (32
\nto 128 MB)
\nPointSizeMM=90 ; desired physical point size width (mm): 1
\nto 120
\nPointSizeMin=2 ; min point size in screen pixels (1 to 15)
\nPointSizeMax=8 ; max point size in screen pixels (1 to 20)<\/p>\n

Pit Macros\u00a0<\/strong><\/p>\n

– Add new pit service text chat macros. Parameters include:<\/p>\n

#help – print help message<\/p>\n

#clear – unselect all request for service<\/p>\n

#ws – use up one tear off to clean the windshield<\/p>\n

#fuel – Add fuel. Optionally specify an ammount to add, defaulting to your displayed units if\u00a0not specified. (#fuel 5, 5g[allon], 5l[iter], 5k[ilo], etc)<\/p>\n

#lf – replace left front tire. Optionally specify the pressure, defaulting to your displayed\u00a0units if not specified. (#lf 30, 30p[si], 30k[pa])<\/p>\n

#rf, rr, lr – same as lf but for the other three tires.<\/p>\n

– Add in 5 new text chat macros, and populate them with reasonable defaults for pit service.
\nThe new macros default to keys shift-1 to shift-5.<\/p>\n

– Renamed chat macro 0 to 10, this will break any custom macro already defined for that slot.<\/p>\n

– Added an option to turn off the automatic request for full pit service every time you exit\u00a0pit road. The default is to leave this behavior active, just like it was previously. The
\nsetting can be found in app.ini [Pit Service] autoResetPitBox=1, setting it to 0 turns off the\u00a0auto check behavior.<\/p>\n

Oculus Rift\u00a0<\/strong><\/p>\n

– Added preliminary support for the Oculus Rift VR Headset Development Kit.<\/p>\n

Follow the instructions of the dev kit to install it as either an extended desktop monitor\u00a0(recommended) or as a duplicated monitor (may allow you to see on a monitor what is visible
\ninside the Rift). The resolution for the dev kit monitor should be 1280×800.<\/p>\n

When launching the simulator, it will attempt to detect the Rift. If it is detected, a dialog\u00a0box will prompt you if you want to use the Rift. If the simulator does not properly detect the
\nRift, try configuring it differently on the PC.<\/p>\n

Centering the Rift: When the simulator first launches, the 2D loading screen image will\u00a0appear (as usual), about a meter way from the view point. While on the loading screen, hold
\nyour head straight and level, and press any key to re-center the head tracking. Any time after loading completes, such as on the replay screen or while driving, you may use the
\nassignable hot key (options screen, default is \u2018;\u2019) to re-center the head mounted display\u00a0(HMD). You may want to assign this command to a button on your wheel, to make it as easy as
\npossible to re-center if necessary.<\/p>\n

VSYNC is optional when the Rift is enabled, specified via the graphics options screen. VSYNC\u00a0is recommended to prevent tearing, but many report less latency and better tracking with it
\ndisabled.<\/p>\n

Multisampling is supported with the Rift. The number of samples per pixel is specified in the\u00a0graphics options screen (AA #samples) and is applied to the Rift\u2019s display if supported on
\nyour GPU.<\/p>\n

The user interface screens now pan (to a limited extent) with head tracking. This allows\u00a0navigation of the garage and options screen within the Rift. It also allows the black boxes
\nand other driving UI to be viewed while driving. This is a work in progress.<\/p>\n

In general, achieving higher frame rates is very important when using the Rift. Reduce\u00a0graphics quality as necessary to achieve low latency head tracking.<\/p>\n

There are several new options located renderer.ini related to the Rift as follows.<\/p>\n

[Oculus Rift]
\nCorrectYaw=1 ; Enable magnetic yaw correction
\nCorrectPitch=1 ; Enable gravity based pitch correction<\/p>\n

UsePrediction=1 ; Enable motion prediction
\nPredictionTimeMS=20 ; How many milliseconds to use during prediction
\nForceVSYNC=0 ; Force on VSYNC for Rift even if disabled in the graphics
\noptions settings
\nPanUserInterfaceToEdge=0 ; Allows user interface to pan further with head tracking<\/p>\n

ForceVSYNC causes VSYNC to be enabled whenever the Rift is in use. When set, it overides the\u00a0setting from the options screen only for the Rift. We don\u2019t currently set this option by
\ndefault because it increases controller lag and head tracking latency on some PC’s.<\/p>\n

The CorrectYaw and CorrectPitch settings, when enabled, use the Rift\u2019s magnetometers (for\u00a0yaw\/magnetic fields) and accelerometers (for pitch\/gravity) to help correct any drift
\naccumulated during driving. When Yaw correction is enabled, whenever you recenter the Rift
\n(using the hotkey) a magnetic calibration will automatically begin \u2013 the calibration will\u00a0automatically complete after the headset is rotated over a large enough range (it helps to
\nlook around after initiating the calibration).<\/p>\n

Garage\u00a0<\/strong><\/p>\n

– The sim now monitors the performance of its „real time” thread. The „garagePhysicsSpeedup”\u00a0entry from app.ini has been removed, and the sim will now dynamically adjust how aggressively\u00a0it runs the physics while in the Garage. If you have a slow computer, and you used to have\u00a0the garagePhysicsSpeedup tweak set to 1, it could have caused the sim to drop out of real
\ntime, causing clock smashes, lots of skew, and probably any replay recorded while you’re in\u00a0the garage to be bad. Now, if you have a fast computer, the physics will settle more quickly
\nin the garage. If you have a slower computer, it will take longer, but the sim won’t drop out\u00a0of real time while you’re in the garage.<\/p>\n

Replay\u00a0<\/strong><\/p>\n

– Added a volume level adjustment for overall replay volume vs driving volume (eg: Hall of\u00a0Fame can turn down the volume level coming from non-driving pods). App.ini only so far, no UI.<\/p>\n

[Audio]\u00a0<\/strong><\/p>\n

loudnessReplay=0.0 ; Volume adjustment for overall replay volume versus driving volume in dB<\/p>\n

Controls\u00a0<\/strong><\/p>\n

– Default Fanatec display to on, now that it has been stable for a while.
\n– Request all forces to start every tick to resolve certain FFB issues.<\/p>\n

Telemetry\u00a0<\/strong><\/p>\n

– Dump the garage tire measurements to telemetry so members no longer need to enter garage to\u00a0log data. We only update the data every time the garage takes a measurement.
\n– Fix a small bug that caused a telemetry variable to not be unregistered properly when the\u00a0car was reinstanced.<\/p>\n

iRacing API\u00a0<\/strong><\/p>\n

– Added support for chat and pit script control to remote api
\n– Add support for remote pit control to session display (so the crew chief can use automated\u00a0tools).
\n– Include the additional weather related info in the irsdk output.<\/p>\n

Voicechat\u00a0<\/strong><\/p>\n

– Fix potential sim crash when keying up voice chat.
\n– Add a mic VU meter to the voice chat UI cluster.
\n– If you attempt to transmit and someone else is speaking on your transmitter’s frequency, a\u00a0„no microphone” icon will be displayed to you, indicating to you that you are not being heard.
\nWhen the server takes the frequency away from the other person and gives it to you, this\u00a0indicator will be removed, so that you know others are now hearing you.<\/p>\n

Graphics\u00a0<\/strong><\/p>\n

– Allow the FPS display (system meters) to work on the session screen during replays.<\/p>\n

Bump Drafting\u00a0<\/strong><\/p>\n

– Reduced bump friction to help reduce hooking bumpers while drafting.<\/p>\n

UI\u00a0<\/strong><\/p>\n

– Add new app.ini setting which, when enabled, stops the UI from reappearing when the iRacing\u00a0window gains focus or is clicked on.<\/p>\n

[Graphics]
\nKeepUIHiddenOnFocus=0<\/p>\n

Options Screen\u00a0<\/strong><\/p>\n

– Re-arranged many of the tabs. Most key definitions have been moved into a single tab with a\u00a0scroll bar.
\n– All hotkeys can now be reassigned, including the replay controls.
\n– Fixed a bug in the code that generates the „Your control is assigned to this device” string\u00a0for „two sided” controls, like Look Left\/LookRight, when the control is assigned to a single
\ntwo-sided axis. It likely would have said something like „Dev 0 Axis 3 <<” instead of „Dev 0\u00a0Axis 3 <>”.<\/p>\n

Helmets\u00a0<\/strong><\/p>\n

– Stamp iRacing logos over the top of helmet license stripe.<\/p>\n

Tire Model\u00a0<\/strong><\/p>\n

– Fixed a bug that would allow the tire carcass to move too rapidly as it passes through zero\u00a0deflection. This helps the tires to feel less twitchy.
\n– Fixed a bug in the temperature calculation that helps the over-the-limit feel.<\/p>\n

Cars\u00a0<\/strong><\/p>\n

– Added Lindblad chassis sponsorship.<\/p>\n

ABS\u00a0<\/strong><\/p>\n

– Updated the ABS algorithm on all our ABS cars for less jarring force feedback.<\/p>\n

Chevrolet Corvette C6R<\/strong><\/p>\n

– Damaged cars no longer have the dash and interior door panels disappear.<\/p>\n

Chevrolet Impala Class B\u00a0<\/strong><\/p>\n

– The track bar split rule instituted at the beginning of the season has been withdrawn.<\/p>\n

Chevrolet SS-Gen6\u00a0<\/strong><\/p>\n

– The track bar split rule instituted at the beginning of the season has been withdrawn.
\n– Fuel load is now adjustable in the garage for practice only.<\/p>\n

Ford Falcon V8 Supercar\u00a0<\/strong><\/p>\n

– Fixed an aerodynamic drag bug that could occur if ride heights got into places that were
\noutside of the aerodynamic map’s limits.<\/p>\n

Ford Fusion-Gen6\u00a0<\/strong><\/p>\n

– The track bar split rule instituted at the beginning of the season has been withdrawn.
\n– Fuel load is now adjustable in the garage for practice only.<\/p>\n

Kia Optima\u00a0<\/strong><\/p>\n

– Fixed a problem where the telemetry reported incorrect fuel levels.<\/p>\n

Lotus 49\u00a0<\/strong><\/p>\n

– The Lotus 49 is now available, and is using the Version 5 Tire Model.<\/p>\n

Radical SR8\u00a0<\/strong><\/p>\n

– Added a kph label on the digital dash.
\n– Updated external engine sounds.<\/p>\n

Silver Crown\u00a0<\/strong><\/p>\n

– Updated external engine sounds.<\/p>\n

Sprint Car\u00a0<\/strong><\/p>\n

– Updated external engine sounds.<\/p>\n

Skip Barber Formula 2000\u00a0<\/strong><\/p>\n

– The Skip Barber car is now using the Version 5 Tire Model.<\/p>\n

Street Stock\u00a0<\/strong><\/p>\n

– The Street Stock is now using the Version 5 Tire Model.<\/p>\n

Tracks\u00a0<\/strong><\/p>\n

Circuit Gilles Villeneuve \u00a0– Now available.
\nLong Beach Street Circuit \u00a0– Now available as a Tech Track.
\nSouth Boston Speedway\u00a0– Racing at night is now available.
\nLanier National Speedway\u00a0– Racing at night is now available.
\nIrwindale Speedway\u00a0– Added a Figure 8 configuration<\/p>\n","protected":false},"excerpt":{"rendered":"

Az iRacing g\u00e1rd\u00e1ja az eddig megszokottakhoz hasonl\u00f3an ez\u00fattal is a szezon v\u00e9g\u00e9re id\u0151z\u00edtette a program…<\/p>\n","protected":false},"author":1,"featured_media":19892,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[49,43,152,147,50,46,296,295,542],"class_list":["post-19891","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pc-hirek","tag-game","tag-iracing","tag-jatek","tag-patch","tag-pc","tag-racing","tag-simulator","tag-szimulator","tag-update"],"featured_image_urls":{"full":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",1000,625,false],"thumbnail":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1-100x70.jpg",100,70,true],"medium":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1-300x187.jpg",300,187,true],"medium_large":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",640,400,false],"large":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",640,400,false],"1536x1536":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",1000,625,false],"2048x2048":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",1000,625,false],"covernews-featured":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",1000,625,false],"covernews-medium":["https:\/\/www.hsw.hu\/wp-content\/uploads\/2013\/07\/lotus-49-on-track1.jpg",540,338,false]},"author_info":{"display_name":"Toya","author_link":"https:\/\/www.hsw.hu\/?author=1"},"category_info":"PC<\/a>","tag_info":"PC","comment_count":"0","_links":{"self":[{"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/posts\/19891","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=19891"}],"version-history":[{"count":2,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/posts\/19891\/revisions"}],"predecessor-version":[{"id":19894,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/posts\/19891\/revisions\/19894"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=\/wp\/v2\/media\/19892"}],"wp:attachment":[{"href":"https:\/\/www.hsw.hu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=19891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=19891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hsw.hu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=19891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}