![]() |
|
|||||||
| IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
|||
|
|||
|
I cannot turn spit on the ground. No seperate brakes, doesent turn with rudder and throttle?
|
|
#2
|
|||
|
|||
|
I have the same problem with differential braking but thought it might be something I was doing wrong despite having the proper axes mapped in controls.
|
|
#3
|
|||
|
|||
|
being able to turn on ground like in IL2 1946, so easy at works lets have that back
after i fire and stop i still have firing sound for a second or two. aftyer landing engine sounds like its still running (hurricane) |
|
#4
|
|||
|
|||
|
The spit braking on ground means you need to map a key or joystick button to Brakes On Full (I think default is 'B') to steer you then press and hold that button then use the rudder to differential brake left or right. It is a bit awkward but actually models the real aircraft well in that respect.
|
|
#5
|
|||
|
|||
|
The biggest issue for me at the moment is with the Spitfire IIa. With realism to full (accept two handed operation) the disparity between control positions and the aircraft response is almost a show stopper. I just had a test flight around for 40 minutes to nail down how to reproduce but turned out it happens in most flight conditions.
I believe this is all related to the same cause. The aircraft instruments and performance loses synch with control inputs from the user. This is not due to low FPS, I was just flying around at between 50-74 FPS. The faults can be measured as followed: Aircraft is in sustained straight and level flight, Artificial Horizon shows bank angle in either direction of 30 degrees+, Turn coordinator shows no turn. Throttle when at around 60% for a sustained period then starts to stop responding to throttle control changes. The icon overlay can show the change but with no response from the aircraft from either gradual or sudden increase/decrease. You have to push it all the way forward or all the way back to seemingly update the aircraft. Rudder trim is similar to throttle.. small inputs have no effect. Have to introduce massive input to get it to register with the aircraft causing over-correction. Intermittent failure to register commands for things like Magnetos or Fuel cock. One moment the key-press works next it doesn't. This is a bit of a show stopper really and CEM is largely unusable for sustained periods of time as a result of the failure of the aircraft to recognize changes to control inputs or key presses. |
|
#6
|
|||
|
|||
|
|
|
#7
|
|||
|
|||
|
Issues I've encountered with FMB or objects with FMB, and MP - FMB used for creating MP mission.
1. German industrial building's "hook" error, can't use. 2. Flak attacks seagull's... LOL. 3. Some objects (i'll create a list) are not useable and renders' the FMB unusable (CTRL-z to undo sovles it for now). 4. Spawning planes inside hangers with door's that don't open....... 5. Some spawning planes spin slowly, brake has no effect. Not sure what the issue is, but it also prevents using the rudder to taxi about. EDIT: it's the wind parameters doing this. Although the ground is skiddish at gradients. 6. Briefing other than the mission description is not viewable at any time. 7. Airfield object - creating runway fine.. the airdrome points are another matter. I assume these allow to create spawn points, and taxi waypoints, but you can't spline? so that 0-1-2-3 is sequential so it doesn't work... how to? 8. Road tool.. bugged. Create a point in Engalnd, a second, and they converge over France :s Last edited by doghous3; 04-13-2011 at 03:13 PM. |
|
#8
|
|||
|
|||
|
Ok I tried many things,
Low or high buildings details no effect. Antialiasing high x8 or off no effect. If you play in 1600*1080 on my system the fps start show is scramble and unreadable. With my system 1920x1200 or less make no change to micro stutter. Is this due to my system or other people do have the same results? It is a great game/simulation event with the little problems. |
|
#9
|
|||
|
|||
|
Graphical and FM bug on the Br.20. Level flight with shot off wing and with prop and pistons of missing engine visible.
|
|
#10
|
|||
|
|||
|
I have just upgraded my system from Windowa XP to Window 7 and increased my RAM from 3Gb to 8GB - so have been 'off the air' for a few days?
Today, I finally got back into the COD after a (1 day download from Steam? and 5 days getting the Windows set-up working?) - its a bit slower down in OZ??) and finally started flying the Hurricane. On the new system, I still had to 'dumb down' everything (graphics)? to get the whole thing working at a a reasonable FPS? I am having problems getting 'ATI Catylist' to work in 'Windows 7' ( I would like any thoughts on this?) so I don't think my video graphics are working at their best? I have attached a 'jpeg' showing some of my graphic problems , now that I have upgraded? My graphics were better on my old XP system? Ilya you have to quickly go to '4 Cores' to get everything working properly in this flight sim - sadly members will have to upgrade! System specs. Operating system: Windows 7 Professional 64-bit Motherboard: Gigabyte P35-DS4 Processor: Intel (R) Core (Tm) 2 Extreme CPU Q6850 @ 3.00ghz Memory: 8192MB RAM Pagefile: 1893MB used, 14485MB available Direct X version: Direct X 11 Display: Benq 1920x1200 (32bit) (59hz) Video card: ATI Radeon HD 4870x2 Driver version: 8.831.2.0 Memory: 1768MB See attached jpeg? DFLion |
![]() |
| Thread Tools | |
| Display Modes | |
|
|