|
|
#71
08-05-2012, 12:58 PM
|
|||
|
|||
Quote:
|
|
#72
08-05-2012, 12:58 PM
|
|||
|
|||
|
Quote:
|
|
#73
08-05-2012, 01:02 PM
|
|||
|
|||
|
Quote:
So the He 111P needs to be checked again regarding the gyrocompass. The little plane inside the gyrocompass should indicate the actual heading with its nose! Right now it is sometimes the planes back or just a completely wrong heading (depending on the actual heading) Took me some time on ATAG to find the right direction because the indicator keep switching around while I just wanted to fly to the coast from Tangmere, it was sooo confusing  After making it to the coast I could clearly see that the comp. is wrong atm.
|
|
#74
08-05-2012, 02:31 PM
|
|||
|
|||
|
Quote:
Edit: Forget it, i just saw you guys are talking about multiplayer. It's a user-made script to clean shot-down aircraft from the server. Quote:
However, the plane in the compass should not indicate actual heading all the time. Coming from IL2:1946 a lot of people are confused with this, because most of the instruments were simplified. In CoD they are more detailed and many get confused. The German repeater compass displays your heading at the top of the compass (the 12:00 position). As you turn around, the outside ring rotates and you read your heading off the top position. The little plane icon in there is a heading selector, not your heading indicator. It's easier with an example. Let's say you are flying due north, heading 0. At the top of the compass you would see 0 degrees. The plane icon is irrelevant to this.Now, let's say you want to turn to your next waypoint which is due east, heading 90. If you map keys to the functions "course setter increase/decrease" you can rotate that plane icon. You press the course setter increase key and the on-screen text will indicate the course setter's degrees as you increase the desired heading to the right, you repeat this until it reads 90 degrees. However, the little plane icon moves to the left. Why? Because the plane icon shows you how much you need to turn and in which direction, in order to achieve the heading you selected. 
|
|
#75
08-05-2012, 04:07 PM
|
|||
|
|||
|
Massive memory leaks are still in the game code!
There are several major bugs that have been around since the release of the game, and this is still one of them.
Originally, this would most quickly occur when you flew near a formation of 3+ 2 engine German (player) bombers. Don't ask me why it didn't affect the Blenhiem, but it just didn't. It only affected the Ju88, Bf110, and He111 (I didn't have the opportunity to fly the BR20 in formation enough to know if it affected it or not). This would also occur in dogfights with 4-5 player flown single-seat planes, but it didn't always happen. At any rate, the game would slowly drop FPS until the game slowed to a .000001 fps and then the game would crash and we would get a launcher.exe error in windows. About 3 or 4 patches ago, this was changed. Now we do not get the launcher.exe error, but if you try to fly a large bomber group, someone wil have an FPS drop below 1 fps and stays there. About 2 patches ago we tried this with a group of ~7 He111's and we lost about 3-4 players because of launcher crashes or FPS drops. Also, we still found this in dogfights with 4-5 planes. Anyhow, the video below shows the same FPS drop I would normally get when flying in a tight bomber formation. There may have been a Ju88 in view distance, but I did not see it. I do know that there was a dogfight roughly 5-6km away from me when I filmed this video. I only notice this type of bug in multiplayer, I have never been able to re-create it in singleplayer. I've also never noticed it when diving on AI controlled planes in multiplayer. I've attacked a formation of over 12 He111 AI planes with a steady ~40fps. VIDEO: -Another major bug that has been around since release is 'ghosts.' We believe it has something to do with de-spawning AI flights. When the game was first released, 'ghosts' were actually pilots/crew members sitting in mid -air where an AI flight had passed by. Now, there are no longer people sitting in mid air, but we still render the distance render dot of an object. When you approach this (what used to be an AI flight) there is nothing there. It is just a distance dot. When you get close, it disappears, but after you pass by and look back, the dot is there again at a distance. To my knowledge, this only occurs in multiplayer. -The last one is just a graphical problem. Running at a high resolution is a hindrance in the game because when you see a contact at a distance and zoom in, it appears smaller (because you are rendering 1 pixel). However, if you are rendering at a low resolution, you can easily see contacts at a distance. The worst is that bombers, boats, and balloons seem to explode from a small do to a 3d object. Also, clouds seem to magically appear at a distance of ~5000m away. Rendering needs some work. And something especially needs to be done for ground object rendering. It is impossible for player bombers to see and line up on a target for a level bomb because they do not render ground objects until they are within 5000m. So for a bomber trying to hit a factory complex at 5000m, you are literally over the target by the time you can render it. Because of the scale of the game, I would suggest allowing the mission builder to designate objects that will forcibly render at a distance.
__________________
|
|
#77
08-05-2012, 05:01 PM
|
|||
|
|||
 I keep get this and I am not running out of resources. 16 Gb ram and 3 Gb vram. Monitoring shows I have plenty of resources left over. Never happened until this patch. Yes, I know how to change the desktop composition, but this is an error specific to CoD application. Should not happen. Last edited by icarus; 08-05-2012 at 05:03 PM. |
|
#78
08-05-2012, 05:33 PM
|
|||
|
|||
|
Quote:
Actually this is the last big issue with performance! But it is a game breaker! |
|
#79
08-05-2012, 05:40 PM
|
|||
|
|||
|
Quote:
|
|
#80
08-05-2012, 06:54 PM
|
||||
|
||||
 Quote:
__________________
Core i7 3930k @ stock, asus rampage IV Extreme, 16 GB ram GSkill 2133 MHz, SSD vertex 3 max iops 120 GB, Noctua NH-D14, 1 x GTX 580 Point of view (overclocked) 3 GB, HAF 942, G 940, silent pro gold 1000 w, track IR 5, SAMSUNG SyncMaster 245 B. |
 |
|
|
Linear Mode
