Jump to content

Jaus

Members
  • Posts

    319
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Jaus

  1. It looks like skins from FC can be ported to ROF just by copying the skin into the appropriate folder. I did this with my Alb skin and it worked without modification. There were two drawbacks however: The colors as rendered by ROF were much brighter than they appear in FC. I had to reduce the overall luminosity of the .dds considerably to get the colors I had seen in FC. Also, ROF may not be able to handle the effects of the alpha channel from FC. On my skin, areas of high reflectivity appear as holes in the skin. It is noticeable up close, but to me it didn't appear significant in the air. This would probably be fixable with a little work on the .dds in Photoshop.
  2. What is the url/pwd to the unofficial Rise of Flight Teamspeak?
  3. I'll be there. WIll fly whatever is needed.
  4. Jaus

    ROF v. FC

    Yes, individual curves was nice for taming squirrely planes. I used to use offset control curves as a kind of trim against planes with consistent deviation.
  5. With the talk about the Gotha scenario, I went back and made sure that my ROF installation still works and flew a few missions. Is it my imagination or is the AI in ROF way better than the AI in FC? Sure seemed that way last night (not that they killed me, they just took more work ) I know the sounds and visuals are much better in FC, but I sure do miss those old planes.
  6. Correct me if I'm wrong, but it looks like the 200hp Halb is the same skin template as the 160, but with late war crosses. If the Halb-au is painted with the black and yellow tail of Jasta 10, should a white border be used to outline the rudder cross so it doesn't blend in with the black?
  7. Are Halb's to be painted with the same Jasta marking (e.g. tail, rudder colors) as the scouts?
  8. I just made a correction to the Albatros skin. Re-uploading now.
  9. I've corrected the names and improved the Pfalz crosses in the submission thread. The Albatros in the zip is probably the same as the one you have. I didn't think you had retained that one as it was submitted during hardlook.
  10. Here are four Central skins for me (actually one skin applied to 4 aircraft) Corrected Dr1 jaus_skins3.zip v_!_JG1_FokkerDr1_Jaus.dds
  11. Re-uploaded. Best?
  12. New skin uploaded. Better?
  13. I'd like to submit this skin. Let me know if I skipped a step in the submission protocol. Update: Heinrich had a couple of suggestions I'd like to incorporate. I'll re-attach when the changes are made. Let's try again..... ! JG1 AlbatrosD5 Jaus Jasta 10_.zip
  14. Success! Even though I removed the modern nvidia plugin from PS, PS still seems to be able to use it. The 8.55 version did install but when you save a file you have to select a different file type (D3D,DDS) to use the older converter. When you select the D3D,DDS file type you get the older converter dialog, and the settings Luftritter posted worked. Thanks for the help!
  15. I googled the 8.55 version of nvidia and downloaded an exe that was clearly labelled 8.55, but it ended up re-installing the 2020.1.1 version. From what I've read it sounds like PS CC doesn't work with the older version of the plugin, and the newer version doesn't work for IL2. I'll try the Dxtbmp.
  16. My settings panel is a little different. The BC3 option does have a tooltip that mentions DXT4/5 so I think that is correct. Generate mipmaps is selected. I don't see a parallel to the '2D texture' pulldown in your image. I do have an 'image type' setting with the options : Color Map| Greyscale | Normal Map-tangent space| Normal Map-object space Maybe I need the 'old' nvidia tools that were mentioned in the post Vonrd linked.
  17. Hmmmm. I did notice that the templates Larner has posted do have unusual (Cyrillic?) lettering for the alpha channel. I tried renaming it but that didn't work. I'll have to give the external converters a try. Does Dxtbmp work directly with .psd file?
  18. I have put it in the locations you quote, and FC does see the file. I am not familiar with dds format and have been taking the dds defaults when saving through the plugin. I just realized I am creating an empty dds file. The problem must be in the conversion settings where I have no idea what to use.
  19. I can't seem to figure out how to correctly save a template to .dds. I have the Nvidia PS plugin, and I save the flattened image to a .dds. FC can see the file, but when I select it there is no change from the default skin. What am I missing?
  20. I wasn't very descriptive of my photo editing 'monitor'. It is actually a pair of monitors, one for the photo and one for the data about the photo ( I sell photography and metadata/cataloging is a big part of that). To get a larger TV with that monitor pair would mean having to constantly swap the TV and the monitor combo as the TV is not acceptable for the photo or its metadata. The 32" Dell would not have specs ideal for gaming (it is spec'ed for imaging, resolution, color gamut) but it would be able to provide a larger screen for FC and could be a one-monitor solution. Everything is on a budget, but the options I'm looking at are manageable. The VR option is very enticing for the immersive experience, but there are limitations I am worried about (rearward visibility, perspiration, lens fogging, headset fatigue, limited use, etc.) Actually, the more I look at what I just wrote the more I realize that my situation is unique enough that it is going to be hard for others to offer applicable suggestions. That said, I am interested in hearing other similar experiences (if there are any )
  21. I have been re-thinking my upgrade plans. The problem: Spotting in FC on my old 22" monitor is virtually impossible unless the aircraft is close. I also do wildlife photography and have frequent need to edit photos The resources: My current monitor is fine for photo editing, but too small for FC. I have a gtx 970 video card, fine for photo editing, not for sim-ing. Possible solutions: As discussed in a previous thread, I could get a large TV , but that would have to be swapped in and out with my photo and data editing monitors. (not desireable) I could get a rather pricey 32" Dell ultrasharp monitor that would be fine for photos, and should certainly improve my spotting in FC but by how much is unknown. I could spend a couple hundred more and get an HP Reverb headset with a refurb GTX1080. I've read great things about the experience, not sure how much it might affect spotting. I'm interested to hear any thoughts/experiences along these lines especially from anyone who has traveled a similar path. Thanks.
  22. I've done some rearranging to make more space and am now experimenting with different monitor arrangements. How does FC handle a change in monitor orientation from 16:9 to 21:9? Greater field of view? Stretching image in one dimension to fit?
  23. What is it about the larger screen that makes spotting easier? Is it just the single pixel aircraft are larger? A 43" tv sounds like fun, but won't fit in my space. What is the contrast ratio of the 43" tv?
  24. I'm thinking about upgrading my monitor or gpu. Currently I have a 10yr old 22" monitor and a GTX 970 gpu. For the purpose of spotting aircraft at a distance in FC, what do you think is the most important to upgrade?
  25. S ! <shows spiffy new uniform> How do I look?!! Thanks for the warm welcome!
×
×
  • Create New...