z929669

Not sure specifically what you mean. Nexus uses IPB as we do, and "My Content" is available from the forums under your user profile menu just as it is here. I also still see the mod tracker is active. I guess I am not familiar with the functionality of which you speak.

The desktop interface in Win 7 is probably still the most prominently used desktop OS. Win 10 cannot be the default, since it has not yet been released to the general market. Win 8.1 is MS's 'default', but I doubt it is more prevalent in the market, particularly in business. What MS wants, MS doesn't necessarily determine and definitely not for me. Easy for you to say if you are indeed new to computer use. Try using a desktop platform and workflow for twenty years and have all of your methods squished by an interface-layout overhaul that masks all of the most important administrative doorways into your OS. It is all still there, but accessing it is more cumbersome for those of us that have developed very efficient workflows within a traditional desktop env (Linux, mac, and Windows all have had a similar desktop interface for the past 20+ years). Change is good, but only when it is better. Metro is a marketing/branding change and is largely useless to many/most PC users, albeit convenient for MS. Actually, it is a pure branding move as well as an attempt to make their mobile OS/apps more relevant. It has the secondary, serendipitous effect of creating consistency across platforms. I would say that a huge chunk (?most?) of traditional windows users hate the new move. Even Googling Metro "love' brings up this Reddit.

Wiki is definitely more flexible, since anyone can edit, and crafty people can subvert certain standards. What we can do is protect pages and discourage certain behaviors, but there is always a degree of flexibility that cannot be constrained. We are just making it very easy to maintain these deviations by having the CSS extension and creating certain templates.

Try to grasp the idea of a 'flexible' standard. This confers a degree of freedom with constraint. See your own examples on the Nexus ... they all have same layout and fonts and styles. Only color theme and backgroud images differ, and those differences are the 'allowable' differences dictated by the flexible standard. (and as you say, this is not a problem, because Nexus main site is not a wiki, and ONLY the design team can edit and thereby dictate color themes and background images). The entire Nexus site conforms to a common look/feel standard. The Nexus main site has the one you refer to, the Nexus wiki has another, and the Nexus forums yet another. None of them change based on supported game (aside from color and background image). All elements have identical spatial parameters, widgets, buttons, etc. All behavior is consistent. That is what we want for this site. It requires definition of the flexible standard (which we have yet to finalize).

On user pages, that is fine, but not on pages supported by the site (e.g., user-created guides that we support in the forums). We need to define a flexible standard for those. Customizing any of the elements above subverts the site look/feel. The only exception would be Neo's guide. That one is grandfathered in, as Neo has been with us from the beginning, as has his guide, essentially. All other user guides are relatively recent. We'll be open to input regarding the flexible standards though. We just need to set a baseline for consistency and discourage gross deviation from that.

I can see that ... I did not examine this one closely ... what about adding code to remove underlines from links within these cols as we do in the INI Settings entry pages?

How is Launch significantly different from Windows Search?? Also, you need to remember the names of all of your programs/docs (or close to it), for these to be useful. I prefer a list (organized to my liking) as a reminder of all the crap I have installed on my OS. Why must our desktop OS behave and be formatted like a phone OS? That's why I will never use post Windows 7 on my conventional PCs. They are not dinky touch-screens!

He has made Header template for that, which essentially masks some built-in wiki editing functionality set under user preferences. These recent templates need to be locked down and restricted to test pages for now until s4n and I can implement a dev wiki for demonstrating these kinds of new ideas without making them accessible to public editors until we are sure we want to implement.

We encourage all community members to become active on the wiki, and we are seeing some great new wiki use and development from several users and staff lately ... example (and see adjacent recent topics). The proposed 'Fc' template changes by Proton are 'good', and I would like to implement some standard color/markup uses for the site. site CSS is probably the best way, but templates like this example is another viable option, IMO. Whatever is most easily maintained is my pick. Any new templates should be coded to include an "Experimental" warning at the top of the page. It might also be a good idea to include such an indicator in the transclusion itself or even restrict the use of such templates to wiki admins.

Testing/experimental template.

Again, this should be considered 'experimental' and not in use outside of mock-up/testing areas.

Possibly useful, but only if we want to dictate a standard for custom user guides ... which is not a bad idea. Need to verify all these new templates with s4n and devise a plan going forward so that we don't get too much use of new templates that will likely make it much more difficult to bring the wiki to a global standard.

Tech will need to confirm this I think, as I am not set up with the latest config to verify.

No, I ran outside of MO as well. You can allocate resource archives via File > Resource Files, and the textures are loaded from the archives. EDIT: the resource files only allow BSA archives, so that seals the deal for me :P (below is the window that opens up when you select File > Resource Files under NifSkope 1.1.3) ... then again, I may be bat**** crazy ... perhaps you can verify my insanity?

The right column was effectively floating right (lots of space between colons and property values). I was too lazy to fix the more sophisticated method you were using, so I just increased the width of the primary div element using the original, more basic CSS parameters.

Actually, that is not my experience (see prev post). I can't get loose to work with 1.1.3, but BSAs do work fine. The Alpha resolves (see other prev post) OP updated with more links

... speaking of nude bodies and STEP's position, if nipples and pubic detail is omitted, then it is really a "not nude" nude and gives the same effect alt3rn1ty (and the rest of us) want without the potentially offensive issues. It's like a skin-colored spandex singlesuit and serves all needs.

That information is also available in the main guide and it may be more up to date there, but I didn't verify that they are different.

OK, change or leave as you see fit then. It works either way

I get about 40 FPS on average outdoors (see my system specs in my sig)

Nope, i took a guess and chose Intel, so you will need to edit with form to change ... the combobox was blank in the form before I chose "Intel" EDIT: Changed Also, I reverted DY's changes and widened the div so that it accommodates slightly longer values (but really, "FirePro M6100 FireGL V" is a bit extreme and could be abbreviated or shortened to "FirePro M6100")

You didn't choose a CPU manufacturer, so that threw off the lineup ... whatever DY did messed up the formatting of the right column though, so need to fix that ...

HDMI and DVI should show no difference at all, since they both carry the same digital signal (but agree that there will probably be loss in analog to digital adapter). The issue stated in the OP is almost certainly the monitor/TV (pixels per inch diffs), but it could be diffs with the GPU as well.

This is probably related to posts created under MyBB, so any posts created before early 2013 likely don't have the attributes needed for use with the fully-functional full editor under IPB. I can't get that functionality either.

PM me your Nexus ID, and I will add you. ... so, is the Nexus wiki description 100% identical to our Nexus description page (BB code and all else)? If not, then they need to be synced up.