Jump to content

Laer

Members
  • Posts

    58
  • Joined

  • Last visited

  1. Ah, I see where I was mistaken. I was about to say that it was not in the list, so I couldn't delete it... but I was only looking at the popup window that shows the current preview module available. I just realized a moment ago, after closing that, that there was an additional screen in one of the other tabs, where the LOADED terrains are listed, and sure enough, it was there, and the option to delete it was present. All is well.... Thanks, The Nephilim
  2. Hi. I was previewing the Nevada map during the module preview promotion, and logged into my DCS World tonight to disable the Nevada map before the end of day deadline hit (...or, to have a quick flight if there was still time). I wasn't sure (due to the time zones), what local time the expiry would actually occur over here. As it turns out, the Nevada time expired already, so the sim popped up messages saying it was disabled, etc. So, I'm assuming that I don't need to disable anything or do any other actions in order, but I just wanted to be sure that I'm okay to just manually delete the Nevada folder from the Mods/Terrains folder... or if it has to be done from within the sim somehow. I just don't want to mess anything up, and also want to be sure I'm in compliance and all that. So, can I just manually delete the folder, or is there some other (proper) way to do it?
  3. Yup, on mine, Caucasus is 16gigs, and PG is 32gigs. (Why do we have a difference on the Caucasus map?) Weird... and now that I checked, the Buy page for PG also states the same specs as Nevada... 60gigs minimum, 160gigs recommended, plus an 'additional 35gigs'... Ya, maybe they are including the base program, and only the 'additional' is the maps requirement... although they are saying 35gigs for PG, when both of us have it as (say) 33gigs. Well, if that's the case, maybe I CAN fit Nevada on there, since it would fit in the remaining 50gigs of drive space I have. Certainly seems more likely the map is around 35, than 160+35! Okay, well, as odd as that is, that's good. I can try Nevada tomorrow. I'll be getting a larger drive sometime (since DCS is surely to increase in size when the new free map arrives), plus I'm sure XPlane11 (which is also on that drive) will be expanding over time. Just needed a quick solution for tomorrow's Nevada preview. Seems like I should be okay. Thanks guys...
  4. Hi, Rudel chw... Ya, a larger SSD is the obvious proper solution, but not something that I can do today (Nevada preview is tomorrow). Not even sure the computer store is open, let alone if it's a good idea to go there. Eventually, though, I will upgrade it, as I said. Too bad I can't just temporarily move the Persian Gulf map... but, you're probably right about it trying to load it. At this point, I'm not even sure the 50gig + the 32(?)gig I'd get from the move would be enough for Nevada, which claims it needs 160gigs... plus 36gigs(?!) more on top of that. Ugh... Ya, I more or less get the link thing... just wasn't previously familiar with it, so I wasn't sure if it created any files as a result, and if you then delete that file to delete the link. The reason I ask about the deletion, is because the article only referenced deleting Symbolic links, not hard links, which I'd be using. As well, I found other articles/threads about difficulty deleting links, although it may just be in reference to links to items that are being used when you are trying to delete them. There were other references to third party apps required to delete them, etc.... and since I'm not well-versed in this sort of thing, I was concerned I'd mess something up with the system or the DCS install, which I couldn't reset/fix. Okay, well, I guess I'll just pass on previewing Nevada... If it truly needs 160gigs (plus possibly 36gigs on top of that), then I'll probably not be buying it anyway. Why is it so huge compared to Persian Gulf and the Caucasus map??
  5. Thanks for the info, Rudel chw. I have to admit, that's a bit new and intimidating, but certainly looks like a solution. What would happen, though, if I just (for the sake of a temp solution to allow me to preview Nevada for a day) manually move the Persian Gulf folder in the DCSWorld/Mods/Terrains folder to a temp (inaccessible) drive, and install Nevada there (with the newly aquired drive space resulting from the move) for now? (Then, deleting Nevada, and moving Persian Gulf back to it's original spot) ALSO: I've read up on Symbolic/Hard links, and I think I pretty much get it. But, what I don't understand, is whether that command line action creates any kind of visible file in any of the directories, or some indication of its existance. As well, how do you then delete that hard link? Remember, I am just wanting to use this to preview (for a day) the Nevada map, which I don't have room for on my DCS drive.
  6. Thanks for the reply. Open question to Fri13 or any other users: So, are we talking just a regular (manually made) shortcut sitting in the Terrains folder of the DCSWorld/Mods folder? If so, how would you specify the install location of the newly purchased/previewing terrain? Isn't it just a checkbox in the Available Modules section of the Module Manager, which then automatically just installs it with the base install of DCS? Again, I want to preview Nevada tomorrow, but only have 50gigs on my DCS SSD, so I'm looking for some sort of (temp) solution to do that. I'll get a larger SSD later.
  7. Hi. Is there a way to install or move terrain modules to another drive, while still keeping DCS on the original drive? My SSD only has 50gigs left, and if I demo/buy another terrain module, it (assumedly) won't fit. So, I'm wondering if I could (for now) install modules on some other drive, and point to that extra drive in DCS somehow. Eventually, I'll probably be getting a larger SSD, and installing all of DCS there, but for now, I can't. In a pinch, would I be able to just temporarily manually move my existing Persian Gulf install folder to another drive, install the preview Nevada map,try it, then delete Nevada and move the Persian Gulf map back to its original location. Obviously, PG would not be useable moved to its new (temp) location, but would it work again once I move the folder back to the DCS drive after deleting Nevada? I'd like to test Nevada out, but only have 50gigs left on the SSD where DCS is installed. ALSO, I'm confused about the Nevada map requirements. It seems to say that it requires 120gigs of drive space for the map (although can, at minimum, operate using 60gigs), but then there's a note saying it needs an extra 36gig of space). So, what's up with all that? What is the minimm abount of space I need on a drive (with DCS World installed on it) to also add the Nevada map?), just to test it out during this preview week? Win7 Premium
  8. Hi. I was always curious about this... When creating a quick mission, I'm puzzled why not all the airfields are available as start points (icons on the map to select your quick mission starting field). As well, why are some that ARE present even there, when every time I try and use them, I'm told there is no airfield there (and so no misson is generated)? Are those intended only for 'starting airborne' type starts? Why even have those start points if they can't be used? And, why not have all the airfields available as start points? I initially thought it was because they were enemy fields (relative to your plane's country/team), but changing to an opposing country/side didn't change the available start points. Are they non-military? What's the reason? I just realized (after having the map for so long) that there were quite a number of other airfields I wasn't even aware of!
  9. So, just curious about something... I know the Hornet uses inertial systems as it's primary/standard navigation system, but was surprised to see that it can't utilize NDB stations. (Yes, I know it can get NBD functionality from VOR and TACAN beacons, but I'm talking about using NDB stations). Normally, I'd understand that the inertial/TACAN systems are far superior to the NDB beacons, but in areas like the Persian Gulf map, I was (also) surprised to see that many of the airfields (ex. on the coastline, for example) do not have TACAN nor VOR. So, even though the map is litered with NDB stations in useful areas, you can't use them... and there seemingly isn't any VOR or TACAN beacons to take their place. Granted, again, the Hornet focuses on inertial nav systems... but I'm curious what happens if/when that system is damaged. Without that, it seems like there's no way to navigate to the coastal airfields, for example. It's odd that you can't utilize NDB beacons for such a situation. I'm by no means knowledgable on this (real world or sim)... but I was just curious about it. BTW, I'm talking in the SIM world... not real world, where I'm sure there are other factors/rules happening.
  10. UPDATE: I just tried it again with Sim/Real Comms selected, but seem to get the same randomness. I'm fairly sure I'm just not understanding something. I'm doing these tests in Quick Mission (Advanced mode). I noticed, for example, that even though I dialed the ATC frequency of an airfield (not the one I took off from), only the one I took off from would be non-grey in the ATC airfield list... and that was only after I called the first (home base) one once (as previous to that, when I tried contacting them the first time, they too were greyed out, even though I had their frequency set). Although it doesn't explain all the issues stated here, I am starting to get the feeling that (at least in Quick Mission mode) you can only radio the field you take off from??? Maybe?.... I don't know. I'm really puzzled by the seemingly random behaviours I'm seeing when trying to dial in either ATC or Nav beacon frequencies, and what determines what is greyed or white in the ATC list (...I would have thought it was the currently dialed in Comm1/2 frequencies, but that doesn't seem to be the case, from what I can see). I thought, too that maybe I was leaving something out in the 'from cold and dark' startup... but even if I start the mission on the runway (already fired up), I get the same behaviors. Again, if I figure anything out, I'll post here, in case anyone else is curious and following along.
  11. Hi. Sorry to ask this seemingly simple (and easily looked for in the manual and/or videos), but I actually did search those, and was confused by what seemed to be contradictions between them. I'm just wanting to get the official word on the PROPER controls you use to control WHICH aspects of a landing approach on-speed AOA. There's two things you seemingly need to control... keeping the velocity vector on the landing target of the runway... and keeping the E bracket lined up to the velocity vector. Yet, it seems some sources say to use throttle to control one, and elevator trim to control the other... while others seem to say the opposite... and some just seem to say use throttle and trim to control both, not specifying if each uses one or both. And, there seems to be some inconsistancy about whether to keep the stick vertically centered (and do any pitch adjustment via the elevator trim), or to use the stick. Sometimes I get it all to work well (using throttle to adjust the vertical placement of the velocity vector on the runway, while keeping the E bracket and velocity vector aligned using trim)... while other times, it's a complete disaster (...not sure what determines that). So, I'm a bit confused, and I want to make sure I'm not doing this incorrectly from the start. Could someone please verify the proper controls used to: 1) Keep the velocity vector on the proper (vertical) section of the runway? 2) Keep the E bracket aligned to the velocity vector? And... 3) Should the stick be kept (vertically) neutral, or can/should you use it to maintain (vertical) alignment of the velocity vector and the runway target area? 4) If using the stick is 'allowed', does it also have affect on the AOA (and therefore the alignment of the E bracket and velocity vector)? Sorry again, but I'm going in circles on this one, and I just want to get this nailed down for good.
  12. @giordino: Odd... that sounds like one of the issues I was having. I had ATC on Comm1, and a nav beacon on Comm2... yet even with Comm1 on full volume, the voice was VERY faint. When I put Comm2 up to full volume (it was as about 10%, since it was a nav, and had annnoying squelch noise), the voice suddenly was proper volume... So, even though ATC was on Comm1, the Comm2 volume knob seemed to control the volume. Not sure what was going on there... The Squelch Filter seems to still be a bit bugged... or at least inconsistant... although maybe I'm just doing something wrong sometimes.
  13. Thanks for the explanation, RobinHood. Much appreciated. I'll try that out next session. I think I did have it working on my first try, but I wanted to be sure I wasn't missing something, and also just wanted to hear the official procedure.
  14. Thanks for the responses, guys. I'm in Sim mode, but ya, my comms are currently on simplified. Although I've had DCS for a very long time, I only occassionally played it, and that would just be me flying around, and not really doing much with the avionics, etc. Recently, I've been trying to learn everything properly (the Hornet is actually suprisingly easier to learn, especially compared to my A-10!). Radios were (up to now) something I thought would be too complicated to do on Sim/Realistic mode... but now, it seems that (despite being on Simplified) I think I'm pretty much doing it the 'real/complex' way anyway. I have to see how the non-simple comms mode differs, and will probably switch to it if what I'm currently doing is pretty much 'real mode'. Yes, I just recently got VoiceAttack (very impressed with it). Partially for the cool feeling of interaction... partially to address not having to memorize some of the more obscure keyboard shortcuts or awkward keyboard keyboard presses... and partially because I pretty much ran out of buttons/axis on my X52 Pro. So, on al counts, VA really addressed those. There's a few things I have to try... One vid said that pressing the Enter button (UFC) has to be more than just a click for it to properly lock in. I also was confused by how the airport frequency info (F10 map, when clicking on an airport) had 4 different numbers. Now, I realize that those are supposedly different frequency bands (ex VHF, UHF, etc)... but, I'm not familiar enough with the ranges to distinguish which band each one is in (...or even knowing if they are ALL useable... certainly don't seem to be). I've been reading the Chuck's Hornet guide (...His guides are always excellent), as well as watching various tutorial videos, including the official ones. Just been a bit puzzling/somewhat frustrating, as what they do doesn't seem to work in my sim, for some reason. I'm going to play around some more... I've already set the Comms to 'real' for the next time I have a session, as I was wondering if that might be interferring (as you pointed out). It may be one or a combination of factors, although I'm not really sure what, as everything seems to check out (ex. line of sight isn't blocked, etc). What might also be a factor, is I have been manually starting up the jet in my recent sessions... and I know that, although it's does start up the engine properly, my steps DO lack some of the lesser proceedures... so, maybe some comms related step is missing in my startup... maybe some switch is (by 'cold and dark' status default) in the wrong position. Got to tinker some more. If I DO figure something out, I'll post it here, in case others are curious.
  15. I'm not an expert or hard-core player, but I figured I'd post what I 'know' in hopes it might help. Apparently, at least in perhaps earlier versions of the Hornet (might have been fixed since) there was a glitch with the Squelch system. From what I remember of a tutorial video, switching the ADF button to 1 or 2 would disable the Squelch Filter (colon beside the SQLCH text on the right of the UFC panel disappears, indicating it's off). If I remember right, the fix was to turn the ATC switch to OFF, turn on Squelch Filtering (click the button to the left of the SQLCH text field), and then put the ATC back on(?)... Not sure, but there WAS some glitch with it. That all said, if you are using Comm2 for navigation and Comm1 for communication, you could always lower the volume of Comm2 (Volume knob on the right of the panel) if the Squelch filter doesn't work (...it SEEMS to work for me, if only sometimes). Just be sure not to turn it down to zero, as the system needs it audible (if only just) in order to function. Again, I'm not an authority on this, and this might all be wrong, but hopefully that might help steer you to a solution.
×
×
  • Create New...