Jump to content

Drakeo

Resident
  • Posts

    308
  • Joined

  • Last visited

Posts posted by Drakeo

  1. On 12/27/2021 at 2:44 PM, Mircea Lobo said:

    Wanted to confirm Nick0678's suggestion works like a charm: I haven't tested with someone else yet but in-world voice appears to be working perfectly, at least as far as the viewer and its mic volume bar are telling me! I really wonder why Linux viewers don't come packaged with the win64 libraries by default, and that script instead of the broken SLVoice binary... till that's settled I'm keeping the patch in a separate directory so I can apply it with each viewer update.

    Last thing I should have to ask is if we may have a link to where those SLVoice binaries are periodically posted. So if I need to update them I won't have to ask for help again. I'm assuming they're updated periodically, if viewers won't ship them like they should I'll probably need to recreate this patch from the latest versions.

    If you do not understand pthread and fast math was part of the compiler moved into GLIBC no longer part of the compiler in clang or GCC. What are you missing.  What don't you get

  2. There is no reason why they say you need to recompile boost if 9.4.0 gcc or higher.

    #  if (CMAKE_CXX_COMPILER_VERSION VERSION_GREATER_EQUAL 10.0.0 )
    #    message( FATAL_ERROR "GCC greater 9.4.0 is not supported. Recompile boost for support of GCC 10.0.0 and up." )
    #  endif()
     

    gcc (GCC) 11.2.0

    GLIBC 2.33

    clang version 13.0.0

    builds fine.

    hey what do I know.

    FS 6.5.2 dev builds  is it stable that's Up to NickyD

    there biggest problems are building the libraries

    with default GLIBC settings. we need for the older GLIBC 2.23 to 2.28 "-g -fPIC -lm  -pthread -fno-finite-math-only"

    this turns off the default fast math that causes issues with newer GLBC linux systems.

    I hope this helps  the FS team. I am sure Henry knows it already?

     

  3. Please make sure if using 64 bit  that you are using the debug FS wine set to true.

    unless NickyD updated to 64 bit voice. I haven't looked. they always stuffed the 32bit SLvoice.exe wine in it.

    so this means you must install wine 64 bit and 32 bit.

    So b4 you say they do not work in Linux viewers you may need to look around been maintaining Linux build since 2011 my voice works on 64 bit Linux.

    All distros that have wine 64 bit installed.  For firestorm you need 32 and 64 bit. 

    I created this 3p package build a long time ago. for 64 bit wine voice kokua borrowed it and made it work for them.

    I use it when building FS  for my repo.

    I have no need for 32bit libraries so back in 2015 started using the wine64 bit build.

    you can find my builds of the FS and SL and Little-penguin viewers on my bit bucket. they are up to date with  SL except for FS I only build it when they release.

    I do build it with some of my libraries and custom builds for modern cpus such as avx avx2 and avx-512  openjpeg 2.5.0 devel that I maintain fork of on the  github

    Since my GF  has MS and hard to move hands voice is a big issue for me.

    I came to SL to work on the media and a 64 bit viewer. care less if any one uses them. But people do and they are stable.

    I recommended a collaboration of prebuilts for Linux on a thread that was closed then deleted. 

    Do to what ever the dictators thinks was the reason. so I started it the prebuilts and the variables to build them to get along with newer glibc clang gcc etc

    https://bitbucket.org/Drakeo/

     

    I see FS has stuffed the SLvoice64 bit into the viewer/bin/ so that means they  added an if statement I used a long time ago just took it out.

    new path and a new XML setting for voice how confusing. no one is using 32bit linux.

    Firestorm 6.5.2 (65510) Dec 27 2021 11:28:52 (64bit / AVX2) (Firestorm-Drakeo) with OpenSimulator support
    Release Notes

    You are at 184.8, 236.0, 89.6 in Missauke located at simhost-047862f33c79ca145.agni
    SLURL: http://maps.secondlife.com/secondlife/Missauke/185/236/90
    (global coordinates 262,841.0, 254,444.0, 89.6)
    Second Life Server 2021-12-10.566713
    Release Notes

    CPU: AMD Ryzen 7 3700X 8-Core Processor (2200 MHz)
    Memory: 32052 MB
    Concurrency: 16
    OS Version: Linux 5.15.11 #1 SMP PREEMPT Wed Dec 22 12:04:03 CST 2021 x86_64
    Graphics Card Vendor: NVIDIA Corporation
    Graphics Card: NVIDIA GeForce GTX 1080/PCIe/SSE2
    Graphics Card Memory: 8192 MB

    OpenGL Version: 4.6.0 NVIDIA 495.44

    RestrainedLove API: (disabled)
    libcurl Version: libcurl/7.54.1 OpenSSL/1.1.1l zlib/1.2.8 nghttp2/1.25.0
    J2C Decoder Version: OpenJPEG: 2.3.1, Runtime: 2.3.1
    Audio Driver Version: FMOD Studio 2.02.02
    Dullahan: 1.12.2.202109282040
      CEF: 91.1.23+g04c8d56+chromium-91.0.4472.164
      Chromium: 91.0.4472.164
    LibVLC Version: 2.2.3
    Voice Server Version: Vivox 4.10.0000.32327

    Settings mode: Firestorm
    Viewer Skin: Firestorm (Grey)
    Window size: 1920x1007 px
    Font Used: Deja Vu (96 dpi)
    Font Size Adjustment: 0 pt
    UI Scaling: 1
    Draw distance: 128 m
    Bandwidth: 500 kbit/s
    LOD factor: 2
    Render quality: High-Ultra (6/7)
    Advanced Lighting Model: Yes
    Texture memory: Dynamic (512 MB min / 10% Cache / 10% VRAM)
    Disk cache: Max size 9984.0 MB (7.8% used)
    Built with Clang version Clang 13.0.0
    Packets Lost: 15/1,518 (1.0%)
    December 27 2021 10:24:10 SLT

  4. On 7/26/2020 at 6:03 AM, rasterscan said:

    two words, one file.   slplugin.exe

    I swopped out firestorms for cool viewers and i can watch tv again. I do NOT advise others to do the same. Altho the TV works again I too still get dulahan error pop ups.  The last time this happened it took a viewer upgrade to fix. Personally I blame html5 and its innocuous but lethal https system. But hey. Brave experimenters may care to harvest various versions of slplugin and swop 'em out and see what happens but, like I say, dont do it kids. Stay safe. Stay careful. The only way is up.

    Unfortunately, you did not name your operating system . CoolVL  has a long way to go understanding basic Linux and the /proc. Love his arrogant work. I see he has become more gentle. With the LL dev;s he is a brilliant man but for Linux pretty much lost in a spoon-fed operating system. Winks.

    I tested all the install from SL to FS to all of my own.  The media worked in all. It seems as Oz Linden said to me when I was working on qtwebit. This is operator error your not smart enough to use your system with this application .  He was right. And  you are in that boat.

  5. On 3/11/2019 at 9:58 AM, Whirly Fizzle said:

    Dullahan is a headless browser SDK that uses the Chromium Embedded Framework.
    https://bitbucket.org/lindenlab/dullahan/src
    It's named after the headless rider: https://en.wikipedia.org/wiki/Dullahan

    You should be able to play Flash media in the viewer as long as you have the correct flash plugin installed for your operating system: https://wiki.phoenixviewer.com/downloads#additional_downloads_to_enhance_user_experience
    Flash media is technically not supported though, if it works, it works, if it doesn't then it probably won't get fixed.

    Certain media types cannot be played with Dullahan because of licensing issues: https://www.firestormviewer.org/why-is-my-tv-not-working/

    The LL viewer also uses Dullahan. So does Sansar.
    Source code: https://bitbucket.org/lindenlab/dullahan/src

    if you find media that will not play with Dullahan that you think should play, then you should file a JIRA issue.
    It's probably not worth bothering to file a LL JIRA for broken flash media (it needs to die in hell anyway) or media problems on Linux.
    If you have media problems on Firestorm in Linux, you can file a Firestorm JIRA issue.

    Oh bet you never took the time to download the 35 gigs and build it. If I am wrong sorry I have been keeping that huge blob now since 2013.  It is embedded chromium  and the top-notch guy  Callum Linden  did great things with it.  Fact  not many want to mess with it in Mac and windows. I have! I stick to   Linux.  Mac and windows. Thank god the best dev Callum Linden does it.

    It is the base of the viewer media. It is wonderful. Much better than the old qtwebkit stuff. Callum you are the best.,

  6. On 11/8/2021 at 1:47 PM, wesleytron said:

    I'm all set to buy a new desktop PC, but hesitating on decisions around the graphics card and CPU. Advice on whether I'm just wasting money on specifications (or the wrong specifications) would be appreciated.

    I was about to forge ahead with:

    • Intel Core i5 Six  i5-11600KF (3.9 GHz, 12 MB Cache)
    • 12GB NVIDIA GEFORCE RTX 3060 
    • 16gb RAM (2x8gb)

    No real rhyme or reason to my choices, other than "Ooh I think 12gb sounds good for graphics! It's a higher number". I'm sure it's good, but is it also pointless?

    I guess the question is - is that overkill for running SL? Should I go with the GTX series instead? How important is GPU memory - is higher Gb on the GPU beneficial?

    Would more multi-cores and/or a higher CPU GHz be better place to put my money? An i7 maybe?

    Notes about me: I'm NOT (currently) a gamer, and for work I MAINLY use my computer for graphic design and publishing. Hobby wise I also use it for some music production just using a DAW and virtual instruments. There is however a possibility I may be doing some video editing. A multi-monitor set-up might be something I'll want for the future.

    Any advice would be welcome.

     I have a firestorm build that will use your avx-512  that your CPU uses. Look me up.  Can build most viewers plus my own with the avx-512 calls.

  7. On 11/8/2021 at 1:47 PM, wesleytron said:

    I'm all set to buy a new desktop PC, but hesitating on decisions around the graphics card and CPU. Advice on whether I'm just wasting money on specifications (or the wrong specifications) would be appreciated.

    I was about to forge ahead with:

    • Intel Core i5 Six  i5-11600KF (3.9 GHz, 12 MB Cache)
    • 12GB NVIDIA GEFORCE RTX 3060 
    • 16gb RAM (2x8gb)

    No real rhyme or reason to my choices, other than "Ooh I think 12gb sounds good for graphics! It's a higher number". I'm sure it's good, but is it also pointless?

    I guess the question is - is that overkill for running SL? Should I go with the GTX series instead? How important is GPU memory - is higher Gb on the GPU beneficial?

    Would more multi-cores and/or a higher CPU GHz be better place to put my money? An i7 maybe?

    Notes about me: I'm NOT (currently) a gamer, and for work I MAINLY use my computer for graphic design and publishing. Hobby wise I also use it for some music production just using a DAW and virtual instruments. There is however a possibility I may be doing some video editing. A multi-monitor set-up might be something I'll want for the future.

    Any advice would be welcome.

    Stay away from any ?60 GPUs. For gaming . In SL it will run fine. The rtx60 NVIDIA GPUs are  good for texture memory.. I love the rtx 3060.  But  the  rtx80 GPUs have much faster bus speeds. Your I5 is a nice CPU.  You will never use more than 1024  texture memory. Not your system.  It is the   application.  But wait, there is a fork of the viewer for mesh optimized. This has nothing to do with mesh in world. Seems  newer GPUs  have this  like your rtx 3060. I have been keeping up with this in  the bitbucket building it.  I have a fork of it been testing it.  Mesh optimized is on GPU it is how we send triangles to the GPU so if we do some work before it gets to the new mesh optimized GPU it makes them supper fast takes the  work off the CPU and utilizes the mesh optimized buffer. . https://bitbucket.org/lindenlab/viewer/src/DRTVWR-542-meshopt/

    Here is the guy that stared it. https://github.com/zeux/meshoptimizer

     

  8. ryzen 7 3700x does  very good blows away all my intel machines. Even with a  gtx 1080. People forget  SL really has no use for high texture memory. 512 1024 a second is plenty.  This isn't a game that preloads into texture buffer for a set return. It is always changing,  higher buffer not always good.  So 2048 can really hurt you.  I hope in  the future  the team tackle this problem till then.  It is up to the CPU And system memory  to clear the bus.

  9. That is you GPU setting  that is environmental setting  just like Franks Elite the dude set it to his GPU and uses older firestorm that is way broke  Franks Elite is all blue yours is orange. environment settings. See operator error just like Oz Linden told me not smart enough to use the viewer, I was hurt.

  10. On 12/7/2021 at 10:13 AM, Sean Heavy said:

    When I login to SL from my Mac I remain an orange blob and my environment has only the terrain downloaded. I see almost nothing around me. There are also errors with my outfit like missing shapes and other missing things. I have gone to different regions all with similar results.

    I have logged in with the latest SL viewer, the latest Firestorm viewer, and SingularityAlpha; all result in the same issues.

    If I login with my Linux desktop computer (on much older hardware), on the same local area network and connected to the same wide area network, everything loads fine, even pretty quick. 

    Is anyone else experiencing this?
    Can you suggest what to look at in my system that might be causing this?
    I am reasonably good with IT but this is stumping me.

    Below are my specs on my Mac:

    MacOS Monterey
    iMac (Retina 5K, 27-inch, 2019)
    Processor: 3 GHz 6-Core Intel Core i5
    Memory: 16 GB 2667 MHz DDR4
    Graphics: Radeon Pro 570X 4 GB

    System Version:    macOS 12.0.1 (21A559)
    Kernel Version:    Darwin 21.1.0
    Boot Volume:    Macintosh HD
    Boot Mode:    Normal
    Secure Virtual Memory:    Enabled
    System Integrity Protection:    Enabled
     

    I compiled  the latest in Monterey. It builds it runs perfect.  The SL code is perfect. It runs on  my oldest to the newest. It is most likely  Operator error . Oz Linden explained this to me a long time ago.  Just not smart enough to use it. I was hurt.

  11. Looking at SL mac downloads . Seems No reason for the dev team to do anything.  There are 10 times more Linux downloads  for  Firestorm and Kokua then any of the SL mac downloads  SL should drop mac it is a loser with M1 Mac users should just leave  like  SL asked all the linux users.  So please close this  thread. Because  macosx and the M1 cpu’s really do not play well.  So why. Even have this thread about macosx.

  12. By the way I am creating a new build tool that  could help many people you can find it here.  every prebuilt may need a different  variable for per GLBC  GCC you want to contribute that would be nice.

    https://bitbucket.org/Drakeo/prebuilt-lib/src/master/

    May be time for third party devs to get together on this  it will save a so much time.

    Feel free to fork and  send pull request.  After I get Linux done will work on the Mac stuff then Windows stuff.

    Be nice if we had a central place to go to it would be nice. .  fork it  create a branch edit your logs.

     

  13. 21 hours ago, mygoditsfullofstars said:

    FYI -- I have a programming background in x86 assembler and C and other languages up my sleeve.

    Number 9 was the last UNIX I dealt with. hey but  Maw Bell was my account.  Instead of being rude we could be talking about  trying to get time on the main frame then

    1978 babe all we had was cards and TAR so be nice. Put the links to your work here so we all can be come part of it FS does.

  14. 21 hours ago, mygoditsfullofstars said:

    @Drakeo Bare metal means to run it natively

    Wow your smart any other slang you want to teach me.  should I  solder another  evergreen 486 into my board or use  a boot strap I am a huge fan so  . Not here to be rude and you are rude and the fact is I am  a huge FS fan. Going to fork it just like Emerald call it  call it Phoenix . Fact is I am a huge fan. so get off me.

    I probably will fork it because LL will not add de render to  objects and allow harassment.

    Next time you think some one owns something on the GPL you should learn what a boot strap is bare metal man.

    Last people rude enough to fork it I had to fix there  builds for them in Inworldz they had no clue. Plock what ever  lol stripped mono from it  omg.

    No one cared when the Aurora project happen.  just fork that to.  stop being mean mygoditsfullofstars

    Love coming in here.

    Quote

    FYI -- I have a programming background in x86 assembler and C and other languages up my sleeve.

     look put you work on the bucket give me the link or  be nice.  I been herding this blob for over a decade.  Use my tools or   put your link to your work here.  GPL right.

    • Haha 2
  15. On 9/25/2021 at 4:55 AM, mygoditsfullofstars said:

    The log spam errors are EGL related

    You have no clue why it is there or you would never post it.  LLError has nothing to do with LL_WARNS it is a tool the spam is good  and is needed.

    It goes to /dev/null so wtf. in linux. Windows people. 

    Fact is spam is not spam it is the feed back from the the code.  Create the log see where the spam you wanted to make  the log.

    Everything you see in  console is what was written the code for you to see.  I am just  having fun. Fact is you have no clue how  "printf" works.

    Hey thanks for the cool pics.

    • Haha 1
    • Confused 1
    • Sad 1
  16. On 9/25/2021 at 1:02 AM, mygoditsfullofstars said:

    @Drakeo

    I am running the viewer on bare metal with the proprietary NVIDIA drivers. Stop making stupid assumptions. Go and look up who I am on the FS website (I'm not some clown who is just experimenting in a VM). I know better than to try and run it in a VM FFS. There is something inherently broken in this release of CEF and GPU acceleration on Linux. I am not the only one who saw the same GPU log error spam. Are you going to accuse the others of trying to run it on a VM too?

    Oh and before you even consider saying my hardware is old. Don't go there. Intel i9, RTX-3070 GPU.

     

     

     

    run it from here. https://vcs.firestormviewer.org/phoenix-firestorm/commits

    Then post a jira OK build it then post it.  WTF is bare metal ?

  17. Hey NickyD what ever your doing something right  look at the donations  love your work on the lab. I rarely take any one serious in here your  just a cool peep up north unless you moved again.

    This issues is the Linux viewer  i love poking at FS pie menu it is my fun thing to do.

    SDL DirectFB is the huge bridge to cross I can careless about  dullahan  actually.

    SDL2 will build with DirectFB  here the issue. 2014  was the last updates ?

    We will have to start linking to the  xorg. ? Xwayland ??? Wayaland .

    I see that Linden labs in the DRTVWR-543-maint is slowly removing the code.

    This will come back to haunt them when  everyone is building on Arms CPU's. 

    I started a build system for the DRTVWR-543 that should build in all Linux systems that are older . This will be moved up as the systems move forward.

    And again thank the world Class viewer team Firestorm for all the help they have given to Linden labs.

    With out the libraries  for Linux we will be left behind.  If I was you NickyD!  And may be to late your Mole hill has become Mountain.

    See you all next week

     

  18. On 9/19/2021 at 7:01 AM, mygoditsfullofstars said:

    Its disabled because its broken in the current CEF release for some reason.

    Screenshot_20210916_122717.thumb.png.4b3ec4968072bf48fb92680bafd0b762.png

    @DrakeoFeel free to compile and debug CEF and let me know what the issue is. This was making my logs about 2GB in size in no time.

     

    Son you  have an issue your working in VM stop being a foolish one. Install it on the hard ware only do not test in virtual machine. If you do not know why. Then please stay away if your a dev.

    As you know I post my CEF3 builds and the scripts to build them ok.

    I am sure in 2015 I enlightened your team lead what to look for.  And the same in 2017 and in 2013 when I was starting on CEF b4 CEF 3

    and The FS team was brilliant in helping with the scripts and pushing  the need Lib's . for old  xorg stuff.

    fact is . For me to compile it in Linux.  So all can use it took many days weeks and years to customize a Linux system in the old GLIBC and old GCC 5.5.0 

    So it can use vulkan and xwayland etc. I built a tool nothing more nothing less.  and Virtualbox will break some libraries do to the cpu ID issue.

    VM machine will break pthread .

     Same reason why Chrome can run on  old Redhat and run on new Redhat. Tools.  Same reason why Mozilla Firefox runs on a 7 year old systems

    nothing hidden here https://bitbucket.org/Drakeo/build-cef/downloads/

    built in GCC 5.50 here is the script I use.

    https://bitbucket.org/Drakeo/slackware64-14-2-cef/src/master/

    future script build for the next 3  to 5 years.

    https://bitbucket.org/Drakeo/slackware64-15-0-cef/src/master/

     

     

     

    • Confused 1
  19. On 9/21/2021 at 9:49 PM, mygoditsfullofstars said:

    Yep, another team member ended up with a 99GB CEF log and it filled their partition...

    look tell you how lost people are.  Not going to talk windows  platform  only a spoon fed humane in the ISA world would get lost doing that.

    Stupidity happens. I build the FS code all three platforms  one a week. OK. S0 I am unable to reproduce using my build. 

    If it was  you and I  would see it in the commits .

    Only ignorance of the program would lead to this.

    Only a smart percentage pushes stable even when your working on the masters edge.

    As far as your 99 gig.  LOL  you need to look at the simple log and see that you have an issue. not the software

     LL tested that dullahan over and over . I submitted my builds so they could see it on the bitbucket. UNABLE TO REPRODUCE

    This discussion is about  GPU  and dullahan. KISS works.

    FS team will fix it. because they  got on the new simplified wagon. Up to FS to push 519.

    OK. get to work FS.  Mine works it uses LL code.

    Where do you see me disabling  this in The LL  Linux viewer I maintain.

    Not good or bad for you.  I want GPU acceleration  when rendering  the platform. Remember we all do not using  a pie menu.

    Or legacy sever for profiles that should be taken down do to the SL experience is changed in a huge way. This is SL not FS.

    You want to be part of the community NickyD then get your profiles in order.

    Other wise we see ruth looking profiles from 2009  in https://my.secondlife.com/

    That's where the platform went with hundreds of fine things. Your   legacy path  just ruins marketing and the experience of the client.

    Yes you can see your old ugly profile in web option. That is a joke and ruins the SL experience for  me and many others.

    Ok See you all next week. right click your back  click a circle click again click again.  tsk.

    World class.

    Some time you have to find 2021 not 2009.

     

    • Confused 1
  20. Is what it is.  not good not bad. just broken dullahan  hey SL no longer supports Linux I see that is catching on. post a log wow.

    Time to say The program is broken because you are unable to watch twitch ?

    I am sure NickyD understands this tsk

    In 3 years they will be porting everything to ARM's cpu Linux. psst only a fool would count out  Google.

    to bad for Mac users the platform gives  has issues with  mac's latest rules.

    You can see it in the commits.  I build my own  version. now go  gather your debug on CEF.

  21. Think about striping your cef3-bin  binaries before packing them or stripping them when building Dullahan. I mean your not building a debug build of CEF3 not really going to help you when using debug option when starting FS.

    283 mb  as a tarball and 1.2 gigs extracted. wow. 

  22. I noticed this commit today.

    Linux; Disable GPU once more, as once again having it on causes issues on some systems.

    https://vcs.firestormviewer.org/phoenix-firestorm/changeset/cef73bce8f2469ee7ec9fc95970831be0e1a0ccc

    
     	mPickedFiles.clear();
     	mCurVolume = 0.0;
    +#ifdef LL_LINUX
    +	mDisableGPU = true;
    +#endif
    +	
     	mCEFLib = new dullahan();
     	setVolume();

    Right now this saddens me. I am unable to reproduce these problems. I rather like having the use of my GPU for rendering media on webpages.

    This isn't a put down  but a regression do to hardware and compliance.  Is this a gamer program or not. Do you think Chrome or Chromium turn this off by default.

    So right now the FS team is building for older I mean way older CPU's That isn't as big of a deal.  If the Firestorm users like me at times  is being held back because people want to run hardware that isn't  up to the programs standards.  NickyD  why not have two builds.  At some point like me people will need to upgrade the hardware.

    But if your running a intel graphics like an i7 APU and  the Linux users are penalized  why not give the people the choice. Not that hard to rebuild the media plugin.

    Just a thought.

    I use the internal browser for all links.

     

     

    • Like 1
×
×
  • Create New...