Jump to content

nessuno0505

Members
  • Posts

    2119
  • Joined

  • Last visited

Everything posted by nessuno0505

  1. Io l'ho presa a 1500. Mai avrei comperato una ti in tempi "normali": con un MSRP a 1200 ha un rapporto prezzo-prestazioni nettamente inferiore ad una 3080 con MSRP a 720. Ma siccome le 3080 lisce non riesco a trovarle a meno di 1200, spendere 1500 per una 3080ti è stato più "onesto" che prendere una 3080 a 1200. Considera che ho recuperato qualcosa vendendo la mia 2070 a 420 (pagata 500 a suo tempo). Comunque mi avete convinto: devo solo vendere il mio Rift s. Lo darei a 200 €, che dite, vi sembra onesto? E' tenuto benissimo e ho ancora tutte le scatole e i manuali originali. Anzi, se interessa a qualcuno...
  2. Sono interessato anch'io al confronto, visto che ho fatto la follia (ebbene sì, ho preso una 3080ti) e ora sto meditando sul cambio del visore. Io sapevo che i problemi di tracciamento erano coi controllers (che in DCS non userei), non col visore in sè! Sai se nei nuovi reverb g2 in vendita oggi ci sia già la nuova versione del cavo, o va comunque comperata in un secondo momento? Ha senso prendere un reverb g2? Cioè, con tutti quei pixel ci sarà da calare il dettaglio grafico anche con una 3080ti! Invece tenendo il mio Rift s dovrei avere un frame rate eccezionale anche con grafica alta! (non ho ancora provato perchè sto aggiornando tutto il PC e sono in fase di montaggio) Insomma ne vale la pena? Grazie.
  3. This is the usual reaction when you try a DCS full module for the first time. You pay 35 dollars with sales and shortly after that you realize you can "play" what you have bought for years and years as your main "PC game" without getting tired and learning something new every day. DCS appears to be very expensive if you look at it superficially (60 dollars for "a DLC"? It's crazy!) but in the end it's the cheapest "PC game" one can get. The manual itself worths the money. Welcome to the disease and be aware that you will never recover!
  4. Io vado per i 44 e anch'io uso il PC quasi solo per simulare (non solo dcs: anche il-2 e microsoft flight sim); è vero i tempi di sviluppo sono lunghi, d'altra parte più che l'età è il tempo che manca: trovo difficile apprendere tutti questi moduli complessi ed essere efficace contemporaneamente con tutti. Pertanto preferisco dedicarmi a due o tre moduli al massimo; è anche il motivo per cui ancora non ho ad esempio l'f-18 o l'f-16. È vero che i moduli si stanno accumulando ed appare sempre più difficile che ED riesca a seguirli tutti in tempi rapidi; è anche vero però che gli elicotteri sono in capo agli ex-belsimtek e che per il mosquito c'è il gruppo dedicato alla wwii. Io credo che l'obiettivo ideale della ED sarebbe dedicarsi al simulatore base e lasciare i moduli alle terze parti; evidentemente al momento questo non basta e hanno bisogno di spingere su moduli fatti in casa. Vedremo cosa accadrà quando tutta la roba grossa che c'è in ballo arriverà verso la fine; sono senz'altro un bel po' di anni di lavoro da mettere in conto per cui il lavoro non mancherà. Credo che l'eventuale comparsa di un competitor nel mercato dei simulatori militari potrebbe smuovere un po' le acque, ma non si vede nulla all'orizzonte. D'altra parte, per uno sviluppatore appassionato è più facile costruire un modulo appoggiandosi su qualcosa che già c'è (dcs) piuttosto che fare tutto da zero.
  5. Exactly. We are aware that a new and improved FLIR is a huge task, but please give us a temporary workaround in order to have the FLIR work again, as before the new clouds. Or state clearly that the only workaround possible for now is to disable clouds. That would mean no clouds in any modern A-G mission, a very disappointing issue but if this is the only solution possible, please let us know.
  6. If this is an issue shared by several modules maybe it should be reported in DCS general bugs.
  7. Sì! Viva il climatizzatore simulato! Che dire... il mio portafogli è aperto, prendete quello che volete!
  8. This is the DCS paradox: if you want to simulate something accurately, if it's military related you can do it only if it's at least 15 years old, while for cities and landscapes you can be current. Thus, you fly 15-20 years old airplanes in a 2020 scenery. Why not to choose a 20 years old scenery? This should be asked to ED.
  9. If it was only air-to-air, still it would worth: this is the right approach! Now I might start complaining about the black shark 3 third pylon, but this would be off-topic...
  10. Maybe it's the wrong forum section, this should be posted in "military and aviation related content". Thus said, we already have M2000c and F-14A, early 4th gen; so a Mig-29A could really give us the first historically accurate content blue vs reds (I know we already have f-5 and mig-21, but this would be a bit different). I think the most modern thing we should expect to have in DCS in the next 10 years could not be later than an F117A, given but not granted ED can simulate low radar observability in some way.
  11. Something I've read on the internet: inconsistent frame time, stuttering, FPS drops, a faulty implementation of asw and blurry image with the Quest 2, versus a more solid and consistent experience with Nvidia, even the 20xx series. Search "6800xt VR performance" on Google. I have a rift s so asw is important to me, and I'm very happy with Oculus VR (that I find a lot better than steam VR) so a quest 2 could be a fine upgrade for my Rift s, if I decided to upgrade my VR hardware too. You have a Reverb g2 so maybe Windows mixed reality Is different, I do not know. But today you can try to buy and AMD card from their site at MSRP, while a Nvidia card Is sold double its price, and this makes a difference too.
  12. Very good news about the partnership for the eurofighter. But, does this new plan change in any way your work on the Intruder? Ok I've seen the other thread. No Intruder ATM but it was already planned.
  13. Just a small off-topic: I've seen your specs: how is DCS VR with an AMD system? I've read low frames and some bugs with AMD graphics in VR. I've got a 2070 on a 5 years old machine; I'd like to renew my system but - given the current price of Nvidia cards - I was considering an AMD system, maybe a 6800xt (there's a small batch every wednesday on AMD shop at MSRP) with a 5800x. Are AMD graphic cards really so badly optimized for VR?
  14. I don't care a new version. A fix of the long standing bugs and maybe a texture overhaul would be more than enough. I like the low tech 1970s style of the f-5, I have both the f-5 and the mig-21 and they are a different interesting way of flying DCS other than the mid2000 high tech birds.
  15. A lot of "reported" in the bugs subforum, but still no fixes in the last OB (except some sort of engine sound overhaul, not really needed nor asked). We seriously need a proper bug fix before any f-5e II upgrade.
  16. Last test: same mission, same settings, no crash, all went well (until my killing by AAA). Vaicompro works on LUA files, maybe if I mispell something it gives back an error, I think it's not an issue. Never thought a crash could be due to my printer/scanner, but it's the last error before the crash so maybe that's the problem. I'll try to fly switching off my printer. Very weird solution, but if it works...
  17. dcs.log Log attached. What's the problem?
  18. DCS Tacan has bugs. Sometime you lost the signal without a reason. Turn It Off then on and the signal Is back again. Long standing bug, I must deduce never corrected (as always).
  19. Solved with a deadzone of 5. Maybe is my warthog getting older? I'll try the same deadzone in pitch too, let's see if it's also easy to trim in pitch.
  20. Exactly. But then "smaller" but very annoying bugs related to single modules pass on stable and stay there for a lot of time once passed, and neither you can hope for a hotfix. L-39 instruments texture missing, and f-86 not clickable buttons are just two examples. Maybe you can play f-86 (very difficult if you fly VR and do not use a keyboard); with the l-39 missing textures we had to rely on a community fix, otherwise unplayable module. Changing a text file was all the work needed, but It passed on stable anyway, and luckily a common user found a fix, otherwise you could not fly the l-39. This Is not acceptable, they HAVE to do something also for "smaller" but very annoying module related bugs. Otherwise IMHO it's better to risk a major bug fixed after a week in OB, rather than hundreds of "smaller" bugs staying for months on stable.
  21. The stable release Is totally unuseful: when they are ready for something new, they pass the OB to stable. Now Marianas have to pass on stable since they are ready for the next new thing (the mosquito maybe?). They look at whole simulator blocking bugs, but noone cares about single modules bugs, this Is even stated in the explanation of what OB Is All about. I have uninstalled the stable branch and fly only OB. If there's a whole blocking bug I move to fly in msfs and wait for the next OB update. I can't use hundreds of GBs of my SSD to keep two versions both filled with bugs, the only difference being the so called stable have bugs that do not get fixed for a longer period of time.
  22. The radios are on when the button is pulled, while they are off when it's pushed. Shouldn't it be the other way around? Pushed = in = radio on; pulled = out = radio off? Or is it correct as it is?
  23. I've checked, no double axis binding. Maybe it's all ok and it's just my wrong impression. I can't do logs. If someone explains me how to, I'll put mine here to check if there's something wrong. If it's not a bug (and it's not), it's one of the two: something wrong in my settings or everything is fine and it's just me. Thanks
×
×
  • Create New...