Galf

Queste lamentele le leggo sempre e solo sui forum italiani :lol: Cosa l'hai bindata, sul tasto di fuoco? ;) l'album è eccezionale e me lo sto ascoltando ogni giorno, avere la musica ingame per qualche volo lungo non è male :P

Read previous page, I provided a fix. I still have not tried multiplayer with it because of real life issues, but it should work. You can also bind all controls while flying with the aircraft and then quit, it will remember the binds.

I just posted on their facebook because we should really see an official response on this, many people don't get it's a dcs bug and just report it on other modules (like I did)...

Thanks for the tip, that's a good one. But remember FXAA blurs textures!

32gb ram is a first in the gaming world just so y'know... if you guys can't get it working on 16 for mp then you're going to have pitchforks nearby soon enough :/ edit: alright you know what, I'll try as soon as I can, if it seizes up on 16gb of ram it's really the first time ever for a game I think...

Just jump in to OB, everyone is playing there anyways, most big servers are on OB too!

edit: nvm my bad and don't want to start a crapshoot. This isn't bug reporting clearly.

Guys, read the linked thread above, I found a fix for it. I'll directly quote my posts to be clear, but the tl;dr is: view.lua file bugs out, replace open beta one with stable one or try a repair. So, you guys should go check out the DCS log file on "\Users\USERNAME\Saved Games\DCS.openbeta\Logs" and if it shows the same error (ALERT error bla bla bla view.lua) then the fix involves replacing that view.lua file. I had a stable install so I copied that. If you don't have that, maybe a repair. Otherwise I can host the file? But I don't know if it's something that will work for everyone.

Guys, it was known that this module would be heavier than the F-18 by a small margin. VR is really hardware intensive, use your brains... it's not heatblur's fault! The plane is really well optimized, but they can't do magic!

This is hell for people with no 3d tracking, I couldn't solve it without binding movement keys... please make a binding for it, or even better, just make it more lenient in its detection radius - I know it's a minimal issue, but it's actually a game breaking one for anyone looking to do a complete startup without trackir (I have just a Tobii 4c, no spatial movement)

https://www.mediafire.com/file/py2ho57550eqp76/View.lua This should work. Emphasys in "should", it could be a file with local settings I have no control over, so try at your own risk - backup your older file in any case, and try a repair first maybe. FOR PEOPLE SCROLLING QUICKLY: TRY A REPAIR* OR IF YOU HAVE A STABLE VERSION COPY THE VIEW.LUA FILE YOU HAVE IN YOUR dcs world/scripts/input FOLDER OVER TO THE OPEN BETA! If you don't have a stable install or if the repair doesn't work, try the mediafire link over here, it has my stable view.lua file, it should work, but I don't know if it will carry over my personal game settings or stuff like that. Also remember that the game bugs over only when setting up axes. If you want to set up a plane and wait for an official fix, get into a mission with it, set all the controls (even if they're not showing you're actually binding them) then quit to desktop and it should keep the controls and work just fine. *how to repair: https://www.digitalcombatsimulator.com/en/support/faq/709/

The patch re-introduces the bug, I had to copy the file again...

Glad to know this works for everyone! :) It was such a weird bug I thought it might have different causes :)

Completamente analog senza limitatori, ma con assistenza al volo per renderlo "docile". Su youtube trovi svariati video di prove areodinamiche ed il modello Heatblur è davvero fantastico: segue ogni tuo ordine e ti informa prima di arrivare al limite, ma richiede tanto timone per usarlo al meglio, cosa che non avviene con gli aerei FBW dove il timone viene aggiunto automaticamente. Insomma... molto divertente!

ecco, grazie per il post tecnico... come dicevo, alla fine in ogni intervista il risultato finale è sempre "conta il pilota". Diciamo in termini DCS alla fine della fiera avranno comunque il vantaggio F-15 ed F-14 semplicemente perchè l'F-16, come l'F-18, se vola senza serbatoi esterni dopo 5 secondi di AB deve tornare alla base :D

Ehm, è un F-16 AI, non c'è l'F-16 nel gioco. Se vuoi fare delle ipotesi, guardati i files tacview fra giocatori. edit: poi calcola che l'F-14B era pari all'F-15 dei tempi, che a sua volta era superiore all'F-16 ma non in maniera epocale, infatti da qualsiasi intervista sentirai sempre che era il pilota a fare la differenza. Nel caso di DCS, l'F-16 è un vecchio aereo AI-only che vola come un UFO ed ha un'intelligenza artificiale che... beh è quella di DCS. ;)

Beh... gli aerei FC3 ti sembrano simulati o solo abbozzati? ;) se li paragoni agli altri aerei non c'è storia!

Hanno fatto vari test con l'AIM-54 comunque. Non so se sarà la versione che avremo in release, ma il "problema" del missile è che brucia per il doppio del tempo rispetto agli altri missili aria-aria nel gioco, quindi se lanciato da media distanza (es. 20 miglia) diventa difficile evitarlo perchè ti piomba addosso a velocità altissime ed hai poco tempo di reazione. Se lanciato a distanze maggiori invece evitarlo è semplicissimo.

So, I had the same problem and I fixed it by pasting the View.lua file from DCS Stable to DCS OB. Here is a cut from my post where I worked it out, on the A-4 thread because I thought it was an A-4 bug before realizing it happened with all modules: So, you guys should go check out the DCS log file on "\Users\USERNAME\Saved Games\DCS.openbeta\Logs" and if it shows the same error (ALERT error bla bla bla view.lua) then the fix involves replacing that view.lua file. I had a stable install so I copied that. If you don't have that, maybe a repair. Otherwise I can host the file? But I don't know if it's something that will work for everyone.

I'll try to produce some clean logs and try again because this is super weird: it never happened to me, then yesterday I installed the A-4 just to try it out and I got this issue. Then I added two other mods (because my cousin wants to play with them, sigh) and I noticed ALL the mods go crazy on me when I try to bind certain axes, it seems to go crazy on all axes except the flight ones. So THIS IS NOT SPECIFIC TO THE A-4! It's something really weird on my end! Today I start up the game, it sees the zoom axis binding no problem (edit: I didn't bind it, it just kept a previous binding attempt, it seems.), so I think it's solved. I get into a quick test mission, seems all fine, then I again try to bind lighting axes and it goes stupid on me again. What I mean by "go stupid": it won't see any command input or axis movement in the command binding section, and if I'm already in a mission it's fine, while the moment I enter a loading screen (es. back from mission to map editor) it hangs - no hard crashes, it just hangs without ever leaving the loading screen. Here's the end of my last log where I tried to unplug my gamepad to see if it had any effect on resetting the issue (it didn't.) I have plugged in: my X-55 stick and X-55 throttle, an xbox gamepad, and a Tobii 4C eye tracker. Playing on latest open beta. 2019-03-12 10:40:14.794 INFO WORLDGENERAL: loaded from mission Scripts/World/birds.lua 2019-03-12 10:40:14.797 INFO DCS: dbox not found , skip 2019-03-12 10:40:14.930 INFO Lua: Lua CPU usage: metric: average mission execution: 25.5148 % 2019-03-12 10:40:14.934 INFO TACVIEW.DLL: Recording flight data in [C:\Users\galff\Documents\Tacview\Tacview-20190312-114015-DCS-a4test.zip.acmi] 2019-03-12 10:40:14.949 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 0 157 squares 2019-03-12 10:40:14.957 INFO EDTERRAINGRAPHICS41: surface5 gc() LOD 1 159 squares 2019-03-12 10:40:14.957 INFO EDTERRAINGRAPHICS41: surface5 gc() 22.174900 ms 2019-03-12 10:40:15.282 ERROR_ONCE DX11BACKEND: texture 'uvmapsfueltank_dft150_dft300_spec' not found. Asked from 'NGMODEL' 2019-03-12 10:40:33.446 INFO Lua: Lua CPU usage: metric: average mission execution: 3.1987 % 2019-03-12 10:40:58.958 ALERT LUACOMMON: Error: GUI Error: [string "./Scripts/Input\View.lua"]:1197: attempt to call method 'setValueRange' (a nil value) GUI debug.traceback: stack traceback: [C]: in function 'setValueRange' [string "./Scripts/Input\View.lua"]:1197: in function 'onProcessInput_' [string "./Scripts/Input\View.lua"]:1224: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> 2019-03-12 10:41:18.326 INFO Lua: Lua CPU usage: metric: average mission execution: 2.7870 % 2019-03-12 10:46:16.063 INFO Lua: Lua CPU usage: metric: average mission execution: 3.0434 % 2019-03-12 10:47:02.960 INFO INPUT: Device [Controller (Xbox One For Windows) {B46E90E0-0C51-11e9-8001-444553540000}] created deviceId = -1 2019-03-12 10:47:02.960 INFO INPUT: Joystick created[Controller (Xbox One For Windows) {B46E90E0-0C51-11e9-8001-444553540000}], ForceFeedBack: no 2019-03-12 10:48:59.571 INFO Lua: Lua CPU usage: metric: average mission execution: 3.1805 % 2019-03-12 10:49:01.624 INFO TACVIEW.DLL: End of flight data recording 2019-03-12 10:49:02.078 INFO Config: netview stopped 2019-03-12 10:49:02.136 INFO TERRAIN: lSystem::CleanScenes() 2019-03-12 10:49:02.225 INFO EDCORE: (dDispatcher)enterToState_:3 2019-03-12 10:50:00.727 INFO EDCORE: (dDispatcher)enterToState_:5 2019-03-12 10:50:00.727 INFO DCS: application shutdown edit: tried again, this time with a proper DCS plane, and it happened again! So there's something wrong with my install, something that went wrong recently... the only recurring factor is this: 2019-03-12 11:11:12.640 ALERT LUACOMMON: Error: GUI Error: [string "./Scripts/Input\View.lua"]:1197: attempt to call method 'setValueRange' (a nil value) GUI debug.traceback: stack traceback: [C]: in function 'setValueRange' [string "./Scripts/Input\View.lua"]:1197: in function 'onProcessInput_' [string "./Scripts/Input\View.lua"]:1224: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> This line does not appear if I don't try to bind an axis Edit 2: alright it happens even if I delete the A-4 and all mods... so I can confirm that it has nothing to do with the A-4, it might have happened some time ago and I didn't notice because I don't often bind non-flight axes. Now I'm lost on how to fix this, but this isn't the proper thread anymore I think... duh. Edit 3: FIXED IT! I have no idea if it's DCS fault or something happened on my side, but I managed to just copy the view.lua file from Stable to Open Beta and it fixed it. The OB View.lua bugged itself. Now the A-4 works flawlessly! (Turns out there's a thread for this bug: https://forums.eagle.ru/showthread.php?t=233656 )

If I try binding the "Zoom View" axis, the module bugs up and crashes at the first loading screen! :S Can anyone reproduce this? I'm binding it to an X-55 throttle Z-axis, I'll try some other things now. edit: had the same issue trying to bind the lighting axis. Flight axes give no problems.

Ricordiamoci pure che i missili in DCS sono la cosa meno simulativa di tutte... hanno troppa resistenza all'aria stando a molteplici riscontri e - la cosa più importante - in multiplayer non hanno possibilità di detonare in prossimità del bersaglio a causa del netcode, vengono calcolati solo i missili che colpiscono direttamente il bersaglio.

Nsomma, penso sia più giusto così. Dopo 4 anni e rotti di lavoro durissimo per portare un modulo di questo livello su DCS, lo regali a chi gioca dietro? In Rise of Flight non c'è RIO, c'è gente dietro che controlla delle mitragliatrici, qui invece la posizione del RIO è complessa tanto quanto quella del pilota ed ha richiesto la stessa quantità di lavoro, è giusto pagare per questo livello di simulazione. Detto questo, studierò duramente per essere un buon RIO e spero di trovare tanti piloti con cui giocare in mp :pilotfly: ...fra un annetto, quando mi sentirò abbastanza sicuro :lol: se c'è qualche altro pilota con scarsa esperienza come me che vuole un RIO orientato al "just for fun" può scrivermi un messaggio privato, ma ci metterò davvero almeno un mese ad orientarmi abbastanza per il mp!

Guys, this is how people improve. Do not be afraid to lay out constructive criticism, no matter how important if you feel something isn't right you should always says so. In the long run it makes people's work easier - once you work on something for long enough you start having troubles seeing the bigger picture, eyes from outside help out a lot. Criticism is good. Andrew's post is a perfect example.