jetkid

+1 I also noticed the lack of lights. Is the fix planned for the next OB patch by any chance? Thx a lot!

hi, it seems not so hypothetical:

Sure @TOViper, thx a lot! Maybe you can evaluate to add this image to help "visualize"

I think this can help to understand - maybe Description of diagrams Upper part is a very precise representation of the CI in B-Scope scanning mode. Below the CI an hypothetical profile of the terrain (also very accurate haha). Then in the central part our beloved Viggen, which by setting the radar at 15 km gradually approaches the B-scope scanning area. Consider the Viggen always at high altitude in order to not have hidden ground amongst the reliefs. Case 1: moving towards waypoint b1 In this case, given that only what is included in the 10km of the B-Scope area is represented on the CI, we need to subtract what remains behind the aircraft as it approaches the upper limit of the B-Scope area, keeping this upper bound fixed in the CI. Thus in the CI we see the image disappear from the bottom upwards (in the schema below from left to right). Case 2: waypoint b1 passed but the pilot reselects it In this case, I have done several tests and it seems to me that the following happens. Given that -also here- only what is included in the 10km of the B-Scope area is represented on the CI, as the aircraft approaches we need to subtract what goes further between the upper limit of the B-Scope area and the radar scanning range limit adopted by the aircraft at that moment (in my example 15km). So as the Viggen approaches the upper bound of the B-Scope scan area, in the CI we see the image disappear from top to bottom (in the schema below from right to left). It's very complex to explain for me, this is my try. Is it correct @MYSE1234? Thank you!

Hi all. Above a simple path to test B-Scope. Here we have Gulf Map, but same behavior applies on all maps. Distance amongst waypoints approx 30km. My problem is about terrain mapping on CI, not on targets. In the saved track you can see B-Scope sometimes not "drawing" the ground inside CI, while PPI does always. Furthermore you can see the "centered" behavior near waypoints (in ME I've setup B types, but the same applies on all the types), in which radar snowplot "goes up" into CI thus "erasing" the parts below. Weird thing: switching from AG to AA radar modes (IR missile on weapons selector), B-scope draws the terrain correctly. Coming back to AG mode even adjusting elevation, no diplayed terrain on CI. 99% of time with CI maximum contrast applied. Track in attach @MYSE1234 It's a bit long track but i think interesting because you can find several strange things on B-Scope mode. Imho. Thank you very much! ASJ37_bscope_test.trk

Hi @MYSE1234 Still not clear to me, sorry Scenario I tried: 3 different "B" waypoints Distance between waypoints: 50 km b-scope mode starts reflecting ground terrain / objects and displaying data on CI only when near the waypoint (now i know it's -6 km to +4 km range) but when i'm for example between A and B or B and C, let's say in the middle (25km away from both previous and next waypoint), b-scope shows nothing, while standard mode works normally displaying data on CI So, is this correct behavior? Thx again!

Hi @Machalot It's about B-Scope not working properly. The radar displays ground reflections only in a +-10km range centered onto the waypoint (B or M or U). Exactly as declared by @MYSE1234 It's unclear to me whether HB -mentioning here @Zabuzard- is fixing the bug. Thx

No information about this problem?

Hi! It's unclear to me whether HB is fixing the bug. At the moment the behavior is exactly as declared by @MYSE1234 and as described into @TOViper document. I doubt this was the behavior of the real life counterpart. Some information @Zabuzard?

Hi @Dallas88B I tried several workarounds... but unfortunately nothing worked. I had to merge diff files manually. Not using any 3rd party SW, just my CH Control Manager

mee too!

it happens randomly also after deleting metashaders... and not only for ground instant mission see here...

I thought it was resolved by manually deleting fxo and metashaders2 contents (under Saved Games folder). After three of four times the game loaded correctly, agin the problem was back. Something is going wrong here... I noticed several ERROR_ONCE DX11BACKEND issues, but among all the modules (airplanes / helicopters) in fact only MirageF1 has this type of problem. ERROR_ONCE DX11BACKEND: texture 'miragef1-common_5_G_S' not found. Asked from '' ERROR_ONCE DX11BACKEND: texture 'miragef1-common_5_B_S_ALA14' not found. Asked from '' ERROR_ONCE DX11BACKEND: texture 'miragef1-common_5_L_S_1' not found. Asked from '' ERROR_ONCE DX11BACKEND: texture 'miragef1-common_4_spec' not found. Asked from '' ERROR_ONCE DX11BACKEND: texture 'miragef1-common_5_nm' not found. Asked from '' and so on... Logs attached. Thx! dcs.log

Hi every skin is without textures on wings. The only working one is the ALA 14 NATO Skin 1 (CE) 1990 I have no mods, used updater for cleaning and repairing Can someone help me? Thx!

i'm using them on win 11 without problems.

Arrivata la comunicazione ufficiale da ED via newsletter poco fa. Complimenti davvero e ora il Lomcovák non ce lo toglie nessuno :)

Hi everyone! I have installed DCS from scratch due to new OS (win 11). I have saved all joystick and keyboard bindings from the previous one. Important note: no hardware changes in the meantime. So I reloaded the joystick profiles - no problem. Then I passed to the various keyboard.diff.lua, but nothing was loaded, everything was always in the default configuration. Then I found, when exporting the keyboard assignments in HTML format, that the hash values associated with the individual commands have changed. Example (Viggen plane) - extract from the keyboard.diff.lua saved by me (from the previous DCS installation): ["d3003pnilunilcd23vd1vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "1", ["reformers"] = { [1] = "LShift", }, }, }, ["name"] = "A1 Mode", }, thus the "old" hash for "A1 Mode" command was: d3003pnilunilcd23vd1vpnilvunil now in the new DCS installation the same command results like this the hash value is a new one: d3002pnilunilcd23vd0vpnilvunil Therefore to have the assignment read correctly by the new DCS, I had to replace the old hash with the new one for "A1 mode" command, inside my keyboard.diff.lua backup file. Same thing for many of the commands in the keyboard.diff.lua files saved by me from the previous installation. Is there a less complex way to retrieve keyboard assignments? I have done a lot of customizations and having to do this hash remapping work is impossible... as well as thinking about reassigning all the commands from scratch... Thanks in advance to anyone who can help me!

thank you!

same problem here! +1

Il G2 al momento non si trova, a meno di non voler pagare un prezzo improponibile (su amazon supera i 700E per la versione SENZA controller). Oltre al fatto che i controller hanno un tracking a dir poco imbarazzante e che su diversi pc la connessione USB è buggata a tal punto da rendere il visore inutilizzabile. Ero intenzionato a prenderlo tempo fa, ma dopo la serie infinita di lamentele da parte della stragrande maggioranza di clienti e dell'aumento di prezzo selvaggio ed ingiustificato, con 350 euro ho acquistato l'oculus 2, che funziona bene e può essere utilizzato anche come visore stand alone per tutta la famiglia. Non ha una risoluzione paragonabile al G2, ma per qualità/prezzo ad oggi è il best buy a mio avviso. Ciao.

I started flying with this module and I noticed a problem on the external model ... I am attaching a screenshot that explains itself well ...

Grazie ora ho rimosso VSynch. Anche FullScreen a sentire quello che consigliano in giro (pare che si guadagni qualche frame). @Super64des sopra i 250 gli sviluppatori sconsigliano. in effetti io sinceramente oltre questo valore non ho notato differenze di fps e/o qualità, ma magari io che sono occhialuto perdo un po' di dettaglio a prescindere e quindi non mi rendo perfettamente conto...

1024 fisso ora provo 512 every frame!

Ciao. In effetti da ODT io disabilito AWS perchè mi crea un sacco di artefatti assurdi. Il fenomeno si verifica in ogni caso sia con AWS acceso che spento... Very strange... In ogni caso succedono cose veramente assurde con il VR. Un altro esempio è che spariscono le vibrazioni più intense nei cockpit... per fare una verifica veloce puoi prendere il 25T e andare in picchiata... anche superando i 650km/h va giù liscio come l'olio, manco un accenno a mezza vibrazione. Togli l'opzione VR e tutto torna come prima... ovvero sembra di stare su un Landini 30 (mitico trattorino d'epoca)... Bhà... può essere che hanno tolto questo tipo di effetti con i visori per evitare di far vomitare le persone...

Ciao. Sotto le config. Due note, in MP porto a 72hz nella app oculus ed il super-sample in ODT a 1.2, in SP ad 80Hz e 1.3 rispettivamente. In ogni caso ogni su dcs non c'è speranza di vedere girare le cose decentemente anche avendo a disposizione una centrale atomica, e non parlo solo per il VR... Con la mia config se sparo tutto a palla in 2D comunque non vado oltre i 35/40 FPS...