Patch 1.03 - Feedbacks

[Electro]

je sais que le radar était éteint, ce qui a changé c'est que l'appui sur le lock suffisait à te faire passer en sous-mode "bore", radar allumé, alors que depuis le patch 1.03, l'appui sur le bouton de lock ne fait rien.

[squezzer]

Pas besoin de programmer une touche supplementaire, il suffit de programmer la sequence "D" puis "CTRL R" sur une seule touche du X45.

[Daffy]

Merci à LP pour ce patch 1.3

J'ai moins de soucis de FPS au niveau des Bases aériennes les jours de grands départs. Maintenant, il me reste encore quelques bizarreries graphiques





Rien de bien méchant

[EricTerminator]

Quel pied, moi qui rêvait d'utiliser à nouveau l'AIM-7 et ses 40kg d'explosif !

Par contre, le F/A-22 Raptor a toujours le problème de l'absence de skin depuis la 1ère version de F4 AF, ainsi que la moitié des avions du jeu...

[GunMan]

Hey les gars ! La tête du pilote bouge en même temps que l'axe de lacet !!

[Jallie]

Hey les gars ! La tête du pilote bouge en même temps que l'axe de lacet !!

--> c'était déjà d'avant ! ! !

le dicton..mieux vaut tard que jamais...ç'est ça qui est bon parfois...

de découvrir qu'il y a encore des truc qu'on ne faisait pas (encore )
..ou qu'on n'avait pas fait gaffe + tôt !!!

[Electro]

je viens de découvrir que, avec le TIR et en pit 3d, désormais, vous pouvez voir vos 6heures... ce qui est hyper utile, tout de même !

[Jallie]

oui...idem...

en mode forcé vers l'arrière...c'est yes maintenant.

parce qu'en mode normal...ça bloque toujours sur le même montants du ACE-II.

mais c'est déjà cela de +

[Blackflys]

Gros probleme de configuration des emports sur BLOCK 50, impossible de mettre un AGM-88C en position 7 et 3, uniquement en 6 et 4 ce qui veut dire que pour les reservoirs sup il faut oublier si AGM-88 en place
Completement irrealiste

[Jallie]

sur quel modèle de F-16 ??

[Blackflys]

F-16 BLOCK 50 comme il etait stipulé sur mon message

[eutoposWildcat]

Block 50 CCIP et Block 52 CCIP, même, pour être plus précis. A priori, chez moi, aucun problème par contre avec les Block 50 et 52 "d'origine".

[MayDay-MayDay]

Comment vous faites le mode forcé pour TIR ? Merci.

[Blackflys]

Oui en effet, config irrealiste uniquement avec les BLOCK 50 et 52 CCIP

[Blackflys]

Les Flight Model ont ete revu a la baisse, mais il y a quand meme des limites, on est passé des F-16 survitaminés à des F-16 sans patate comme le MLU.
Je veux bien que sa motorisation date un peu mais il ne faut tout de meme pas exagerer. , chargé à bloque, il faut limite voler en Full PC pour ne pas decrocher....

[GunMan]

J'ai un gros probleme par contre avec les GBU, problème inexistant sous la 1.02.

J'essaie d'abbatre à la GBU-24 un Shelter ou la tour de controle, donc je passe master arm / on, laser arm / on, je configure tout, largage des bombes une à une, Hardpoints 1 et 2 On, TGP on, tout le bordel...

Pour finir je suis sur mon shelter en expend sans lock complet, le curseur est pile au centre du shelter. La GBU est larguée, et tombe facile 5 mètres à coté du shelter, c'est à dire très très loin de là ou je l'avais demandé...

Si je refais la meme experience avec deux GBU-24 en largage par paires, tout marche très bien.

J'ai déjà testé de larguer volontairement la bombe à côté du shelter de façon à ce que le "décalage" fasse que ça tombe dessus... Mais ça marche pas.

En lock complet, ça tombe encore plus loin. (en plus je ne largue jamais mes GBU avec full lock).

Deux solutions :
1/ Je ne sais pas larguer une GBU (ce qui me parait quand meme très peu probable)
2/ AF Bugge

[Ghostrider]

Je veux bien que sa motorisation date un peu mais il ne faut tout de meme pas exagerer. , chargé à bloque, il faut limite voler en Full PC pour ne pas decrocher....

Rentre les AF

Sans rire j ai senti la reduction de poussée mais faut pas non plus exagérer .....

Mais c est vrai qu il reste encore pas mal de trucs a corriger ... LP annonce une series de patch et pas un ou deux

[C3PO]

Bonjour --- I'd love to help but my French isn't anything to speak about. I managed to understand about the COMS 1 and COMS 2 -- they are not implemented ... but TeamSpeak 2 works a treat

[Morpheus FFW08]

Just one remark about the thrust of F16:
it seems to be weak because in low altitude it is impossible to get more than 400 kt IAS without AB, with a "normal load" (2 tanks, 6 mk 82, 2+2 a/a missiles).
in "real" operations, the push is at least at 540 kt, and of course we can get this speed without AB... RPM should be betwen 95 and 100% and remaining at 540 kt should not be a problem.
it must be the same for medium and high altitude, because it is hard to keep a reasonable speed above FL200. once again, pushing at FL 300/M0.90 should be possible with such a load.

Pour les français:
la poussée du F16 semble faible,parce qu'en conf de guerre (2 bidons, 6 Mk82 et 2*2 missiles A/A) il est impossiblme d'obtenir des vitesses correctes.
en BA, difficile d'avoir plus de 400 kt de Vi sans la PC, alors qu'on devroit pouvoir se ballader à 540 kt sans trop de soucis, et sans PC of course.
en HA, difficile de grimper au dessus du FL 200, alors qu'on devrait pouvoir se trimbaler au FL300 et M0.90.

Alors, ce F16, un peu mou du moteur?

[T-REX FFW04]

Since patch 2 (1.0.3) I can't host a campaign on-line game anymore...

We are 8 players, one hosting teamspeak and another one (me) hosting the game.

Everything works almost fine for about half an hour after take-off, and then my graphics display starts to go wrong: it freezes twice or more and then goes into a blank screen.

The strange thing is that the other players are still bound to each other,despite my blank screen (crash to desktop w/ the windows error report send/don't) as if the server was still working fine... but, from minutes to minutes some are kicked out, some are freezed, others lose they flight controller, and finally only two of us reached the landing area without getting in any trouble. For those two fellows everything was fine except the runway wasn't there :(

This kind of thing never happened to me before, that's why I am wondering why it does happen now, because I didn't change anything to my settings nor hardware.

My CPU is a P4 3.2GHz w/ 1GB RAM, my graphic card is an ATI Radeon 9800XT w/ 256MB RAM, and the bandwith of my internet connexion is quite large (at least 512k/s up and 10M/s down)...

Is the campaign mode to heavy to be played on-line w/ 8 human pilots ?

We'll try next week to test the same mission with another hoster than me... maybe it's my computer's fault, but who knows...

[C3PO]

['-REX"]Since patch 2 (1.0.3) I can't host a campaign on-line game anymore...

We are 8 players, one hosting teamspeak and another one (me) hosting the game.

Everything works almost fine for about half an hour after take-off, and then my graphics display starts to go wrong: it freezes twice or more and then goes into a blank screen.

The strange thing is that the other players are still bound to each other,despite my blank screen (crash to desktop w/ the windows error report send/don't) as if the server was still working fine... but, from minutes to minutes some are kicked out, some are freezed, others lose they flight controller, and finally only two of us reached the landing area without getting in any trouble. For those two fellows everything was fine except the runway wasn't there :(

This kind of thing never happened to me before, that's why I am wondering why it does happen now, because I didn't change anything to my settings nor hardware.

My CPU is a P4 3.2GHz w/ 1GB RAM, my graphic card is an ATI Radeon 9800XT w/ 256MB RAM, and the bandwith of my internet connexion is quite large (at least 512k/s up and 10M/s down)...

Is the campaign mode to heavy to be played on-line w/ 8 human pilots ?

We'll try next week to test the same mission with another hoster than me... maybe it's my computer's fault, but who knows...

I think your machine might be overheating. Make sure the heatsink and fan on the CPU is free of dust and debris: this solved an issue for someone else who suffered similar problems.

Also make sure that your connection speed is entered again into the speed setting fields: updating resets them to 33kbps up and down. Let me know how you get on!

[T-REX FFW04]

I think your machine might be overheating. Make sure the heatsink and fan on the CPU is free of dust and debris: this solved an issue for someone else who suffered similar problems.

Also make sure that your connection speed is entered again into the speed setting fields: updating resets them to 33kbps up and down. Let me know how you get on!

I have no problem with overheating, fans are clean and so on. I guess the problem is somewhere else. It may be something independent from AF, because, as far as i know, other people don't have such problems.

I installed the latest graphic card drivers, and I didn't experience the graphics crashes anymore. This problem seems to be fixed.

On another hand, I have several questions about the connection settings:

1- For instance, my upload speed is around 800kb/s and for download it is around 12000kb/s
So I told AF to use up=768 kb/s and down=8 thousands-something (I don't remember the exact value).
But, when I play online I also use TeamSpeak. When TeamSpeak is in use, the upload speed drops to ~500kb/s. Should I then told AF that my upload connection speed is 512kb/s or do I let it set to 768kb/s ?
In other words, if the 800kb/s speed is not always there but sometimes droping a 'little', what appends with AF servers packets ? are they lost or recovered ? Does it lead to lags or more serious problems ?
I doubt this point has anything to do with patch 1.0.3, it may be due to something else, but I didn't clearly understand this point.

2- Connection speed fluctuations leads to the problem of 'micro-disconnections'. It might append that an internet connection breaks for some very short time (maybe less than one second). Are AF server and clients able to reconnect w/o damage or is it a critical situation ?

This kind of problem is often discussed when talking about client/server exchanges, these are protocol, buffer, swap, and timeout handlings. How is it done by AF's sever ? How far is it user settings dependent ? If you know.

I don't know either if you heard about our datalink problems. Our last on-line game (8 players) was a nightmare because of D/L. For instance '2' can see '4', '4' can see '2', but '3' was alone ( in spite of a D/L set to 'on' ) or totally out of range (alt=Angel700!! for instance). The same thing happened to the other flight... Some of us can see each other, but some have no consistent D/L...
It was like some of us plaid in another game. We can't see them in spite of 8 players confirmed on the kneeboard.
Is it the first time you here about this ? Do you think it could be linked to the above client/server problem ? how ?

This it a lot, I know, and I beg your pardon for annoing you which those things, which seem to have more to do with our computer settings than with F4AF. But if you could light our way you are welcome

Thanks again

[hatch]

I just would like to point out that night missions are quite difficult to fly under F4AF.
The airbases are very dark, the landing light is not visible from the cockpit and the runaway/taxi lights are hardly visibles.With the NVGs, only the taxiway and runaways and some structures are visibles, but not the terrain (it is black).
In the air, when using the HUD FLIR vision, the terrain is not clearly visible, only some lines and "volumes", makes it very difficult to judge where we are in terms of altitude.Besides, it is very difficult to setup the FLIR parameters (FOV and tilting) to get the correct view. When manoeuvering the A/C, the objects in the HUD FLIR FOV seem to move in a bad sense, I don't know how to explain that, but it's hard to keep a good visual reference.

Anyway, these things have been there since a long time ago, but maybe LP could take the opportunity to enhance it...

C3PO if you hear me...

[moi1000]

Un bug tout con : je faisais un petit vol sur MLU. En vue exterieur, il était danois. Depuis le cockpit il était tchèque

[wacco]

hi all
I have a problem with the TACAN of Capo dichino (in Balkans) .
In f4af doc the chanel is 125Y, on the kneemap it's 125X, but none of both is correct.
thx