Jump to content

Hippo

Members
  • Posts

    960
  • Joined

  • Last visited

Everything posted by Hippo

  1. OK. But IIRC, when a new module is released, a new version tends to be released to support it. Still, I hope you're right.
  2. Thank you for making the effort to post. I'd be really interested to know WHY the option to disable deferred shading was removed, and why it was removed now? Is it because new models are no longer being developed to work with the old method? I.e. is it because the F-18 and PG will not work with the old method? I really would have liked to have kept the option to not use DS, even as a legacy unsupported option, and would have lived with glitches. Is there absolutely no option to leave it in for a while longer? After waiting all this time for the F-18, it grates somewhat that when it arrives I have to run it with much decreased performance.
  3. Framerates were over 100% higher (not using DS) than they are now, with all other settings staying the same. I can understand why some might complain. There is no option for MSAA 8x.
  4. Hippo

    Labels in VR

    Thank you for posting that. I've tried labels before (new installation recently), and will give your settings a go. I just wish DCS had a more intelligent way of dealing with this, e.g. Make targets appear as conspicuous dots depending on target distance AND SIZE, to relate to when an average person would first be able to see them in reality. Show target name when relative target size means an average person would be able to identify them (including if target is magnified via a targeting pod, i.e. display label in the MFD). All as options, of course.
  5. Too much tension around here of late. Thought I'd try to lighten the mood. Sorry if I went too far for some.
  6. ...my updater just updated... but then nothing. ;)
  7. :D Bah humbug! (Should I mention the F.A. Cup?)
  8. OK, descending to 6400 (on 29.92) worked and triggered the "well done". I then had to climb back up to 7000 before the trigger to request the level turn would work. I then managed to screw up the low speed level turn :) so can't comment on the rest of mission, but I'll give it another try tomorrow. Thanks for replying. ***** EDIT Managed to complete the mission. Descending to 6400 and then climbing back up to 7000. After that following the altitudes as requested by the instructor everything works out fine.
  9. The point I was making was with regard to the manner in which this has been handled by ED. I believe that it is customary, when replying to a post, to debate the point being raised. Hence my curt reply to that other poster. The points you make are all entirely reasonable, but have been discussed endlessly already. The MSAA thing is very subjective, of course. To me, no MSAA in VR results in unacceptable image quality. I have come down to 1.0 PD, and 2xMSAA, and am living with that; but it grates when I had found settings that I was very happy with, with deferred shading off, and much higher fps.
  10. Are you saying that we should set 29.92 at all times for the campaign? I know I've probably missed it somewhere; but does this need to be more explicitly explained to users? It's the first time I've come across this after attempting this campaign several times. TBH I've never changed the altimeter setting when flying this campaign. In my (RW private flying VFR) experience I would set QNH on departure, and QFE on approach (UK VFR). Most other places, I believe, stay with QNH on approach also. I have never gone above transition when VFR where I fly. I'm inferring from your explanation that military pilots don't use QNH at all. This seems to me unlikely, but I'd be very interested to know how they actually do handle it. Sorry to keep cropping up like a bad penny, btw. What happens is I start the campaign, get distracted by real life or come up against issues like this. Put it aside for weeks, then start again from the beginning. Through several attempts I think the furthest I've ever got to is mission 6 or 7. Not complaining, I think your campaigns are brilliant, my own motivation and attention-span - not so much.
  11. +1. Kept flying past WP3. Thought it might be because I had missed the waypoint, and so I tried to turn around -> mission failure as too much deviation from 040.
  12. That's very helpful, thank you. Problem solved.
  13. Coulda, shoulda, maybe. I have the greatest admiration for ED, and all they've done over the years, and there is a sense in all of these posts that they are beyond criticism and can do no wrong. Well, sorry, but forcing deferred shading, which cuts frame rates in half, on users, as a simple one line bug fix in a readme, with no explanation, no warning, is to treat their users with complete disdain. It's just not an acceptable way to behave. I think that we should complain loudly, and that it's right and fair to do so.
  14. Ah, ahora entiendo. El problema es que la instalacion de DCS la prefiero en ingles. No se como va lo de misiones de entrenamiento, pero seria posible descargarlas en castellano y abrirlas / volarlas en el editor? O incluirlas en la version DCS en ingles como VO? Gracias por contestar, me imagino que ya teneis bastante con que ocuparos. Y disculpa pf ortografia, tildes, etc - UK keyboard only.
  15. Options, please options. I believe that locking the cursor to head motion is (or has the potential to be) a real issue in VR that has been overlooked by developers. I haven't had too many issues with DCS, but as example I offer the (Majestic) Q400 in P3D. In this aircraft, the knobs on the MCP (at the top of the instrument panel) affect the MFD displays. So, e.g., to set the altitude / heading / etc you have to put the cursor on the knob and turn the knob while looking down at the changing value in the MFD. If the cursor moves when you move your head this is extremely inconvenient, if not impossible. Of course, IRL, the pilot puts his hand on the knob, looks at the display and turns the knob. There has to be some way of replicating this. I would suggest that the cursor stays put unless the mouse is moved again (to some adjustable threshold), at which time it would reappear (centred?) on-screen.
  16. I would like to have the option that the cursor does NOT move when I move my head, i.e. mouse only. Is it possible to do this currently? Reason: on occasion you need to click a switch and look at a result somewhere else in the cockpit. This is very difficult to do if the cursor moves as you move your head. It would be the equivalent of keeping a finger on a switch while looking around.
  17. Yes, please give us TABS. Real pain to have to go through multiple pages and back again when switching between checklist / charts / manual / etc. Would need keybind prev / next tab.
  18. Thanks for replying, but I must be missing something. I don't know where to set the localisation to ES and can only find four missions under \DCS World OpenBeta\Mods\aircraft\C-101\Missions\EN\Training (no ES folder). Just to be clear, what I mean is whether there are versions of these missions with the instructor speaking in Spanish?
  19. Hi. Sorry if I'm being a bit dense, but I can't proceed past step 36 (intercom panel). I don't have the option to press "Space", and I'm not sure if I'm supposed to do something. Are there versions of these missions in Spanish? Thanks for any help. **** EDIT **** I haven't tried yet, but I think it's probably because I haven't pulled the various knobs. I was only rotating them - I'll give it another go tomorrow. **** EDIT **** Yes, it was me. Apologies. After pushing and pulling in several knobs I managed to progress. Apologies for wasting anyone's time. I'll leave this here in case it helps anyone else. These training missions really are excellent as are the cockpit graphics, your artist(s) have done a fantastic job. Really looking forward to the advanced flight model.
  20. Agree entirely. To add to the frustration, I pre-ordered the F-18 assuming I had found settings which would work for me. This is no longer the case, and the sense of disappointment is enormous. I'm thinking of asking for a refund.
×
×
  • Create New...